This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author eric.araujo
Recipients akitada, anthonybaxter, eric.araujo, tarek
Date 2010-08-26.00:49:51
SpamBayes Score 5.22954e-07
Marked as misclassified No
Message-id <1282783793.66.0.150950019347.issue1109659@psf.upfronthosting.co.za>
In-reply-to
Content
Being able to write a global option after a command name seems a nice feature to me, and the implementation should be straightforward: The base Command class already adds some options like help to each subclass, it’s just a matter of adding verbose, quiet and dry-run and adapting distribution.

no-user-cfg would have to be special-cased: Giving this option to one command  would just pass it to the Distribution instance. Supporting per-command no-user-cfg would be overly complicated and not really useful.
History
Date User Action Args
2010-08-26 00:49:53eric.araujosetrecipients: + eric.araujo, anthonybaxter, tarek, akitada
2010-08-26 00:49:53eric.araujosetmessageid: <1282783793.66.0.150950019347.issue1109659@psf.upfronthosting.co.za>
2010-08-26 00:49:52eric.araujolinkissue1109659 messages
2010-08-26 00:49:51eric.araujocreate