We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi, this is not really an issue but a feature request.
It would be really nice if after parsing the configuration, one could dump it back out, possibly after altering the data structure as needed.
Thanks for this nice project!
The text was updated successfully, but these errors were encountered:
yeah, it is called a outputter (not a generator, as I had incorrectly stated firstly).
I have been looking at various add-on to the pyparsing module for generating from its graph tree.
Even am looking at alternative parser that may have a builtin generator.
At the moment, one could add members to pyparsing to support this.
pyparsing
Still tabulating cost effectiveness of development time here, but this is one feature that is rather high on my list.
Sorry, something went wrong.
I'm conferring with the @ptmcg (author of pyparsing) about the re-outputting of the config file.
One thing we have to remember, any comment lines will be lost.
There are two general classes of parsers, and only one of them can save comments as well as inline comments of Python/C/C++ varieties.:
antler
No branches or pull requests
Hi, this is not really an issue but a feature request.
It would be really nice if after parsing the configuration, one could dump it back out, possibly after altering the data structure as needed.
Thanks for this nice project!
The text was updated successfully, but these errors were encountered: