classification
Title: python -m no longer executes packages directly
Type: Stage:
Components: None Versions: Python 2.6
process
Status: closed Resolution: invalid
Dependencies: Superseder:
Assigned To: Nosy List: Martijn, benjamin.peterson (2)
Priority: Keywords

Created on 2009-10-27 12:48 by Martijn, last changed 2009-10-27 14:25 by benjamin.peterson.

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
2009-10-27 14:25:51benjamin.petersonsetstatus: open -> closed

nosy: + benjamin.peterson
messages: + msg94561

resolution: invalid
2009-10-27 12:48:16Martijncreate