[issue14857] Direct access to lexically scoped __class__ is broken in 3.3

2012-05-27 Thread Roundup Robot
Roundup Robot added the comment: New changeset bcb3b81853cc by Nick Coghlan in branch 'default': Tweak importlib._bootstrap to avoid zero-argument super so I can work on issue #14857 without breaking imports http://hg.python.org/cpython/rev/bcb3b81853cc New changeset 96ab78ef82a7 by Nick Coghl

[issue14857] Direct access to lexically scoped __class__ is broken in 3.3

2012-05-20 Thread Meador Inge
Meador Inge added the comment: Ouch. The '__class__' behavior is documented here too: http://docs.python.org/py3k/library/functions.html?highlight=__class__#super. Unfortunately I don't see any other documentation on the lexically scoped form of __class__. As implied, cases like the follow

[issue14857] Direct access to lexically scoped __class__ is broken in 3.3

2012-05-20 Thread Arfrever Frehtes Taifersar Arahesis
Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue14857] Direct access to lexically scoped __class__ is broken in 3.3

2012-05-20 Thread Daniel Urban
Changes by Daniel Urban : -- nosy: +durban ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.o

[issue14857] Direct access to lexically scoped __class__ is broken in 3.3

2012-05-19 Thread Nick Coghlan
New submission from Nick Coghlan : Currently, __class__ references from methods in 3.3 aren't being mapped correctly to the class currently being defined. This goes against the documented behaviour of PEP 3135, which states explicitly that the new zero-argument form is equivalent to super(__cl