Benjamin Peterson [EMAIL PROTECTED] added the comment:
I'm not sure how we could implement a warning on import of exceptions
aside from implementing it in the compiler. I suppose 2to3 could just
remove the import...
--
nosy: +benjamin.peterson
___
Brett Cannon [EMAIL PROTECTED] added the comment:
On Sun, Aug 24, 2008 at 2:51 PM, Benjamin Peterson
[EMAIL PROTECTED] wrote:
Benjamin Peterson [EMAIL PROTECTED] added the comment:
I'm not sure how we could implement a warning on import of exceptions
aside from implementing it in the
Changes by Brett Cannon [EMAIL PROTECTED]:
--
priority: critical - release blocker
___
Python tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2350
___
___
New submission from Brett Cannon [EMAIL PROTECTED]:
Importing 'exceptions' should raise at least a Py3K warning, if not a
full DeprecationWarning.
--
keywords: 26backport
messages: 63718
nosy: brett.cannon
priority: immediate
severity: normal
status: open
title: Warn against importing
Changes by Brett Cannon [EMAIL PROTECTED]:
--
priority: immediate - urgent
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2350
__
___
Python-bugs-list mailing list
Douglas Mayle [EMAIL PROTECTED] added the comment:
I ran python through a debugger and found that the exceptions module is
imported automatically at load time. Because of this, when import
exceptions is parsed, the module is already loaded, and PyImport_Import
is not called. In order to
