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 _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
