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 Martijn
Recipients Martijn
Date 2009-10-27.12:48:15
SpamBayes Score 0.00018057719
Marked as misclassified No
Message-id <1256647697.94.0.0863288338635.issue7220@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2009-10-27 12:48:18Martijnsetrecipients: + Martijn
2009-10-27 12:48:17Martijnsetmessageid: <1256647697.94.0.0863288338635.issue7220@psf.upfronthosting.co.za>
2009-10-27 12:48:16Martijnlinkissue7220 messages
2009-10-27 12:48:15Martijncreate