[issue17473] -m is not universally applicable

2013-09-26 Thread Nick Coghlan
Nick Coghlan added the comment: runpy needs to be refactored at least a bit before this will be practical. Issue 9325 is an existing issue for the same idea that discusses some of the problems to be resolved (it's a good idea, just a fair bit of work). -- resolution: -> duplicate stat

[issue17473] -m is not universally applicable

2013-09-26 Thread Antoine Pitrou
Changes by Antoine Pitrou : -- nosy: +ncoghlan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.pyt

[issue17473] -m is not universally applicable

2013-09-26 Thread Claudiu.Popa
Changes by Claudiu.Popa : -- nosy: +Claudiu.Popa ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue17473] -m is not universally applicable

2013-09-26 Thread Berker Peksag
Changes by Berker Peksag : -- nosy: +berker.peksag ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue17473] -m is not universally applicable

2013-03-22 Thread Tshepang Lekhonkhobe
Changes by Tshepang Lekhonkhobe : -- nosy: +tshepang ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue17473] -m is not universally applicable

2013-03-18 Thread R. David Murray
R. David Murray added the comment: I think this is a reasonble idea, however there is no intrinsic relationship between these modules, so adding -m to each one should be a separate issue. We can use this issue as a master and make the other issues dependencies of this one. As a new feature a

[issue17473] -m is not universally applicable

2013-03-18 Thread Devin Jeanpierre
New submission from Devin Jeanpierre: Many executables in python are meant to be run on python scripts, but can't run python scripts that are part of a package. For example, one can do `python -m pdb foo.py`, but not `python -m pdb package.foo`. This makes it more difficult to interact with ex