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 mrh1997
Recipients mrh1997, paul.moore, steve.dower, tim.golden, zach.ware
Date 2017-11-08.16:55:53
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1510160153.48.0.213398074469.issue31879@psf.upfronthosting.co.za>
In-reply-to
Content
Of course I do not know the initial ideas/philosophy of the launcher.

But the current implementation supports these custom commands (for whatever reason). Thus I'd say they should work "properly". My view of "properly" is that the implementation matches the documentation which is currently definitely not the case.

Of course one could add an extra passus to the docs like: "custom command names must not start with 'python'". But why include a special case (and make it less intuitive) without need?

By the way: We have a use case for this custom commands and I could image others had, too. Or how came that they were included?
History
Date User Action Args
2017-11-08 16:55:53mrh1997setrecipients: + mrh1997, paul.moore, tim.golden, zach.ware, steve.dower
2017-11-08 16:55:53mrh1997setmessageid: <1510160153.48.0.213398074469.issue31879@psf.upfronthosting.co.za>
2017-11-08 16:55:53mrh1997linkissue31879 messages
2017-11-08 16:55:53mrh1997create