-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
YAML configuration/project file instead of XML #24
Milestone
Comments
rakhimov
changed the title
Non-XML configuration/project file
YAML configuration/project file instead of XML
Jan 14, 2017
rakhimov
added a commit
that referenced
this issue
Jan 14, 2017
This is the start of the transition to YAML format instead of XML. PyYAML and PyKwalify are added as dependencies for YAML processing. Issue #24
rakhimov
added a commit
that referenced
this issue
Jan 14, 2017
- The minimum Python 3 version is bumped to 3.4 Issue #24
rakhimov
added a commit
that referenced
this issue
Jan 14, 2017
Explicit is better than implicit! This should be handled outside of package constructor. The implicit single source packages are not supported by YAML config (#24), so the code is unused. Some ugly code due to this initial mal-design is removed. This feature could be reintroduced in future in a better form.
rakhimov
added a commit
that referenced
this issue
Jan 14, 2017
A single list entry can appear as a non-list object if not followed by '-'. This is, however, valid with PyKwalify and convenient to write. Issue #24
rakhimov
added a commit
that referenced
this issue
Jan 14, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
yaml as a potential alternative.
The text was updated successfully, but these errors were encountered: