On Tue, Jul 13, 2010 at 8:06 AM, Michael Foord <fuzzy...@voidspace.org.uk> wrote: > An explicit error being raised instead would be just as good.
Ah, refusing the temptation to guess. So the idea would be, when attempting to import __main__ under it's original name: 3.2 issue a DeprecationWarning 3.3 raise ImportError It still strikes me as wrong for the base import implementation, but PEP 302 may provide a mechanism for an interpreter shell to add its own "newbie protection" hooks (and that would have the virtue of being available much earlier and with a much lower chance of breaking anything). Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ 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
