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 vinay.sajip
Recipients alexis, brian.curtin, eric.araujo, lygstate, paul.moore, tarek, tim.golden, vinay.sajip
Date 2012-02-18.11:39:44
SpamBayes Score 1.0067864e-09
Marked as misclassified No
Message-id <>
Also, we normally set ".py", and ".pyw" into the PATHEXT environment variable, so that a script "" can be invoked from the command-line as just "pysetup" without the suffix. This gives the same experience as using a "pysetup.bat".

I would say that pysetup seems a little more polished (and shorter) than the -m form, especially for users new to packaging. After that, I agree with Paul's ordering of .exe, with the setup script having to be named if we use the "standard" mechanism, or else if we use a custom .exe, it can of course be called whatever we want.
Date User Action Args
2012-02-18 11:39:45vinay.sajipsetrecipients: + vinay.sajip, paul.moore, tim.golden, tarek, eric.araujo, brian.curtin, alexis, lygstate
2012-02-18 11:39:45vinay.sajipsetmessageid: <>
2012-02-18 11:39:44vinay.sajiplinkissue14027 messages
2012-02-18 11:39:44vinay.sajipcreate