[issue1170766] weakref.proxy incorrect behaviour

2011-01-04 Thread Armin Rigo
Armin Rigo added the comment: Not for me (the last example I posted, on 2.7 head). But I will not fight for this. -- ___ Python tracker ___ _

[issue1170766] weakref.proxy incorrect behaviour

2011-01-03 Thread Antoine Pitrou
Antoine Pitrou added the comment: Works in 2.7 and 3.2. -- nosy: +pitrou resolution: -> out of date status: open -> closed ___ Python tracker ___

[issue1170766] weakref.proxy incorrect behaviour

2010-08-21 Thread Mark Lawrence
Changes by Mark Lawrence : -- versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.4 ___ Python tracker ___ ___ Python-bugs-list

[issue1170766] weakref.proxy incorrect behaviour

2010-08-21 Thread Armin Rigo
Armin Rigo added the comment: All the missing type slots I reported can cause incorrect behavior very similar to the one reported originally. For example (in Python 2.7): class I(int): pass i = I(123) hex(i) => '0x7b' hex(weakref.proxy(i))=> TypeError I

[issue1170766] weakref.proxy incorrect behaviour

2010-08-21 Thread Mark Lawrence
Mark Lawrence added the comment: I'll close this in a couple of weeks unless anyone objects. -- nosy: +BreamoreBoy status: open -> pending ___ Python tracker ___ _

[issue1170766] weakref.proxy incorrect behaviour

2008-03-17 Thread Raymond Hettinger
Changes by Raymond Hettinger <[EMAIL PROTECTED]>: -- assignee: rhettinger -> _ Tracker <[EMAIL PROTECTED]> _ ___ Python-bugs-list ma

[issue1170766] weakref.proxy incorrect behaviour

2007-09-20 Thread Sean Reifschneider
Sean Reifschneider added the comment: Raymond: Is this still a problem, or should we close it because the reported issue is resolved and 2.4 is no longer maintained? -- assignee: -> rhettinger nosy: +jafo priority: high -> low resolution: -> accepted type: -> behavior ___