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

Is there a reason you choose an JSON configuration file vs INI (configparser) based file? #7

Open
bschollnick opened this issue Feb 7, 2016 · 0 comments

Comments

@bschollnick
Copy link

I've forked speed complainer, and I'm adding in the ability to customize the ping settings, etc. But I want to keep this backward compatible.

Is there a reason you went with a JSON config file, vs a straight ini based system. I have a home brew module, that makes using the ini system quite simple. It will take the ini file, and map it into a dictionary for easy loading and manipulation.

(I personally find the JSON configuration file very cluttered....)

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