[Python-Dev] PEP 328 and PEP 338, redux
Giovanni Bajo
rasky at develer.com
Tue Jun 27 18:32:22 CEST 2006
More information about the Python-Dev mailing list
Tue Jun 27 18:32:22 CEST 2006
- Previous message: [Python-Dev] PEP 328 and PEP 338, redux
- Next message: [Python-Dev] PEP 328 and PEP 338, redux
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Phillip J. Eby wrote: > Actually, maybe we *do* want to, for this usage. > > Note that until Python 2.5, it was not possible to do "python -m > nested.module", so this change merely prevents *existing* modules from > being run this way -- when they could not have been before! > > So, such modules would require a minor change to run under -m. Is > this > actually a problem, or is it a new feature? This is where I wonder why the "def __main__()" PEP was rejected in the first place. It would have solved this problem as well. -- Giovanni Bajo
- Previous message: [Python-Dev] PEP 328 and PEP 338, redux
- Next message: [Python-Dev] PEP 328 and PEP 338, redux
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list