|
|
|
|
|
by duerrp
3963 days ago
|
|
>> So...it's for configuration management? What do >> "experiments" have to do with this? Yes and no, pyexperiment handles configuration management for you (by using argparse and configobj etc.), but it's main point is that it saves you from having to set up these components. My main goal was to reduce the overhead of writing the same "framework" code every time, so pyexperiment sets you up with simple one-command solutions for many common tasks. >> What does this package do that isn't done by click,
>> docopt, or argparse? It will set you up with a framework where e.g., you don't have to write the same boilerplate code to get a multiprocessing cabable logger that logs to a file. You just call log.debug("bla") and that's it. |
|