Unification of settings' and headers' format by YAML. #3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…y opened w/o errors.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By this request you will unify the format of
settings.cfgand the headers. This is done by replacing ConfigParser and the former key:value parsing method by _YAML_. The latter, although more general and thus slower, will enable easier modifications and extensions in PyLL's future.It is as exact as the previously used formats.
Unluckily, it shares one of the former drawbacks, too: In case of an user forgetting to define headers and setting e.g., "Operation: XYZ" as first line, that one is wrongly regarded as header. A problem which cannot be solved in an other way than insisting on at least one header line, the title.
Settings.cfgis short and can easily be rewritten. Header's format already is a subset of YAML, therefore nothing needs to be changed.