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 Steve Barnes
Recipients Steve Barnes, paul.moore, steve.dower, tim.golden, zach.ware
Date 2017-05-16.05:38:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1494913092.31.0.156770771134.issue30362@psf.upfronthosting.co.za>
In-reply-to
Content
@steve.dower I did check and none of the currently supported pythons us -l or -L and have implemented it with -list and -long-list but I do appreciate your point that someone might come up with a use for all of these flags in a future version of python.

How about dropping the short flags, (-l & -L), and making the long flags more launcher specific, i.e. --launcher-list and --launcher-list-paths spring to mind.

I really do think that this change would be really useful, e.g. in the short form to generate a list of installed targets that might all need a specific library updated or to create one venv for each installed target, the long version has already helped me out spotting where a python that I was not expecting had been added to the registry.

I'll also take a look over on pep514tools to see if there is anything I can do to help there.
History
Date User Action Args
2017-05-16 05:38:12Steve Barnessetrecipients: + Steve Barnes, paul.moore, tim.golden, zach.ware, steve.dower
2017-05-16 05:38:12Steve Barnessetmessageid: <1494913092.31.0.156770771134.issue30362@psf.upfronthosting.co.za>
2017-05-16 05:38:12Steve Barneslinkissue30362 messages
2017-05-16 05:38:11Steve Barnescreate