[issue7220] python -m no longer executes packages directly

Benjamin Peterson added the comment: This was purposely removed in 2.6 and reworked in 2.7 and 3.1. -- nosy: +benjamin.peterson resolution: -> invalid status: open -> closed ___ Python tracker

[issue7220] python -m no longer executes packages directly

New submission from Martijn Ras : 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 . In Python 2.6 this results in the following error: /usr/bin/python: is a package and cannot be directly executed