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

[Feature Request] Better config file #57

Open
GoogleCodeExporter opened this issue Oct 10, 2015 · 1 comment
Open

[Feature Request] Better config file #57

GoogleCodeExporter opened this issue Oct 10, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

The current config file is hard to understand. strict=0, usb=False, it's 
inconsistent. I had to dig through the source to figure out why my brick wasn't 
being recognized and ended up reimplementing it with the json module instead.




Why do you think it's important?
It's frustrating when things don't work. Also, it'll get rid of your eval call, 
which really isn't Pythonic at all.

Any ideas on how to implement it?
I used the json module. Renaming the existing keys would be a good approach as 
well.

Please provide any additional information below.
I've attached my config file. I might attach the modified locator.py when I 
finish cleaning it up.

Original issue reported on code.google.com by i.nnikishi on 9 Jul 2013 at 4:59

Attachments:

@Bottersnike
Copy link

If you want, @Eelviny, I have some code that I always use the parse config files that look like the following:

stuf: True
morestuf: False
startDate: 15432252
someNumber: 213
someWords: hello

@schodet schodet self-assigned this Dec 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants