➜
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.
Created on 2009-10-27 12:48 by Martijn, last changed 2022-04-11 14:56 by admin. This issue is now closed.
| Messages (2) | |||
|---|---|---|---|
| msg94555 - (view) | Author: Martijn Ras (Martijn) | Date: 2009-10-27 12:48 | |
Heya Folks, I've just started moving some of my projects from Python 2.5 to Python 2.6. I used to start some of these packages using python -m <packagename>. In Python 2.6 this results in the following error: /usr/bin/python: <packagename> is a package and cannot be directly executed I got everything running again, by using the following command: python -m <packagename>.__init__ This strikes me as awkward, since every package should still have the __init__.py file. Can this be fixed so running python -m <packagename> will once more be equal to python -m <packagename>.__init__? Mazzel, Martijn. |
|||
| msg94561 - (view) | Author: Benjamin Peterson (benjamin.peterson) *  |
Date: 2009-10-27 14:25 | |
This was purposely removed in 2.6 and reworked in 2.7 and 3.1. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:56:54 | admin | set | github: 51469 |
| 2009-10-27 14:25:51 | benjamin.peterson | set | status: open -> closed nosy: + benjamin.peterson messages: + msg94561 resolution: not a bug |
| 2009-10-27 12:48:16 | Martijn | create | |