Message119543
I find that _AttributeHolder is a handy way for passing the command line options around the application. What is lacks though is a documented API for actually fetching the attributes in batches, like .items() or something similar that could be used for iterating over all command line arguments. That's why I thought '_get_kwargs' would be a good candidate particularly because it does exactly what I need in my code, returns a sorted list of key/value parameters.
But I'm not really saying that it must be '_get_kwargs', could as well be _AttributeHolder's __dict__ attribute as long as the docs say that it's a part of the public API so that I'm sure I'm not using something that may silently break between releases. |
|
Date |
User |
Action |
Args |
2010-10-25 09:30:15 | dsuch | set | recipients:
+ dsuch, bethard, docs@python |
2010-10-25 09:30:15 | dsuch | set | messageid: <1287999015.89.0.172516432177.issue10190@psf.upfronthosting.co.za> |
2010-10-25 09:30:14 | dsuch | link | issue10190 messages |
2010-10-25 09:30:12 | dsuch | create | |
|