On Tue, Jun 27, 2006, Phillip J. Eby wrote: > At 08:08 AM 6/27/2006 -0700, Guido van Rossum wrote: >> >>Bad idea IMO. The __name__ == "__main__" rule is so ingrained, you >>don't want to mess with it. > > 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?
Well, yes, considering that cd'ing to the module's dir and doing "python module.py" will now fail. -- Aahz ([EMAIL PROTECTED]) <*> http://www.pythoncraft.com/ "I saw `cout' being shifted "Hello world" times to the left and stopped right there." --Steve Gonedes _______________________________________________ Python-Dev mailing list [email protected] http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
