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 alexis, ceder, eric.araujo, fdrake, guyrozendorn, higery, mhammond, tarek, tim.golden, vinay.sajip
Date 2011-10-24.16:26:07
SpamBayes Score 5.694036e-06
Marked as misclassified No
Message-id <1319473568.47.0.365762176827.issue12394@psf.upfronthosting.co.za>
In-reply-to
Content
> FYI: In pythonv, the build_scripts functionality provides identical support for dotted
> callables to what Éric proposed, while preserving existing functionality for ordinary script
> files.

My current preference is to use only new-style generated scripts for the scripts field in the files section, and to let people use the data-files/resources system for old-style file scripts.

We’ll have to think about the shebang munging and decide if we keep it.  I think recommending that people use “/usr/bin/env python” (or python3) and not doing anything to the shebang may be the best thing.

> While working on this, I came up against a problem with build_scripts in virtual environments:
This is also a bug in current distutils and distutils2 scripts.  Scripts should always be regenerated, as they depend on the running Python, not on other files.
History
Date User Action Args
2011-10-24 16:26:08eric.araujosetrecipients: + eric.araujo, mhammond, fdrake, vinay.sajip, ceder, tim.golden, tarek, alexis, higery, guyrozendorn
2011-10-24 16:26:08eric.araujosetmessageid: <1319473568.47.0.365762176827.issue12394@psf.upfronthosting.co.za>
2011-10-24 16:26:07eric.araujolinkissue12394 messages
2011-10-24 16:26:07eric.araujocreate