Skip to content
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

Investigate moving from JSON/YAML parsing to ConfigObj #5

Open
winhamwr opened this issue May 2, 2013 · 0 comments
Open

Investigate moving from JSON/YAML parsing to ConfigObj #5

winhamwr opened this issue May 2, 2013 · 0 comments

Comments

@winhamwr
Copy link
Owner

winhamwr commented May 2, 2013

ConfigObj would allow us to mostly get out of the low-level validation-parsing game. It has built in validation and template expansion. It uses python templating instead of Jinja2, but it's not clear if that's much worse. It would also certainly be possible to add Jinja2 support.

Need to evaluate how well the current functionality would fit our needs and how much of a risk the current project status is. Looks like there are quite a few open issues and the project hasn't had any commits since 2011. I would much rather contribute to a shared library than re-implement some of the functionality inside Neckbeard though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant