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 | ncoghlan |
|---|---|
| Recipients | benjamin.peterson, ncoghlan |
| Date | 2008年05月04日.04:34:24 |
| SpamBayes Score | 5.4108652e-05 |
| Marked as misclassified | No |
| Message-id | <1209875667.56.0.764676566127.issue2751@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
The ability to execute packages was never intended, since doing so breaks imports in a variety of subtle ways. It was actually a bug in 2.5 that it was permitted at all, so 2.6 not only disabled it again, but also added a test to make sure it stays disabled (2.4 correctly rejected it with an ImportError, just as 2.6 does). Here's the relevant svn log entry: r56509 | nick.coghlan | 2007年07月23日 23:41:45 +1000 (2007年7月23日) | 5 lines Correctly cleanup sys.modules after executing runpy relative import tests Restore Python 2.4 ImportError when attempting to execute a package (as imports cannot be guaranteed to work properly if you try it) |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年05月04日 04:34:28 | ncoghlan | set | spambayes_score: 5.41087e-05 -> 5.4108652e-05 recipients: + ncoghlan, benjamin.peterson |
| 2008年05月04日 04:34:27 | ncoghlan | set | spambayes_score: 5.41087e-05 -> 5.41087e-05 messageid: <1209875667.56.0.764676566127.issue2751@psf.upfronthosting.co.za> |
| 2008年05月04日 04:34:26 | ncoghlan | link | issue2751 messages |
| 2008年05月04日 04:34:24 | ncoghlan | create | |