Benjamin Peterson [EMAIL PROTECTED] added the comment:
Collin, can you review the 2to3 patch?
--
assignee: - collinwinter
components: +2to3 (2.x to 3.0 conversion tool) -Interpreter Core
nosy: +benjamin.peterson, collinwinter
___
Python tracker
Georg Brandl [EMAIL PROTECTED] added the comment:
I'd say that since this is so easy for a fixer to spot and fix, no
convoluted effort to add a Py3k warning is necessary. (The same goes
for sys.exitfunc, #2356).
--
nosy: +georg.brandl
__
Tracker [EMAIL
Jack Diederich [EMAIL PROTECTED] added the comment:
+1, I'll burn my _apply_evil(ModuleObject *) function patch to
moduleobject.c which did a memcpy on a type object and several other
heresies.
On Tue, Mar 25, 2008 at 4:27 AM, Brett Cannon [EMAIL PROTECTED] wrote:
Brett Cannon [EMAIL
Jack Diederich [EMAIL PROTECTED] added the comment:
Fixer patch works for me (both must be applied).
A 3k warning for accessing is harder - it would have to copy the module
type or dict type and supply a custom to_getattro that watches for
accesses to exc_(type|values|traceback). I'll look
Jeff Balogh [EMAIL PROTECTED] added the comment:
Attaching a patch that provides fixers for sys.exc_
{type,value,traceback}
Added file: http://bugs.python.org/file9749/issue2357.diff
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2357
New submission from Brett Cannon [EMAIL PROTECTED]:
Using sys.exc_{type,values,traceback} should raise a Py3K warning.
--
components: Interpreter Core
keywords: 26backport
messages: 63732
nosy: brett.cannon
priority: immediate
severity: normal
status: open
title:
Brett Cannon [EMAIL PROTECTED] added the comment:
A fixer to use sys.exc_info is needed.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2357
__
___
Python-bugs-list mailing list
Changes by Brett Cannon [EMAIL PROTECTED]:
--
priority: immediate - urgent
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2357
__
___
Python-bugs-list mailing list
