[issue18690] memoryview not considered a sequence

2013-08-08 Thread Simon Feltman
New submission from Simon Feltman: This was a bit unexpected as memoryviews support all the methods of the Sequence abstract base class: >>> import collections >>> b = bytearray(b'asdf') >>> isinstance(b, collections.Sequence) True >>> m = memory

[issue14631] Instance methods and WeakRefs don't mix.

2012-11-11 Thread Simon Feltman
Simon Feltman added the comment: Some more complex examples from various libraries: https://github.com/django/django/blob/master/django/dispatch/saferef.py https://github.com/11craft/louie/blob/master/louie/saferef.py I think both of these originated in pydispatcher

[issue14631] Instance methods and WeakRefs don't mix.

2012-11-11 Thread Simon Feltman
Simon Feltman added the comment: The WeakCallableRef that was attached seemed to support regular functions (or anything callable) which is nice. The naming also leaves room for a WeakCallableProxy. -- ___ Python tracker <http://bugs.python.

[issue14631] Instance methods and WeakRefs don't mix.

2012-11-11 Thread Simon Feltman
Simon Feltman added the comment: Just a note this is also referred to as a "WeakMethod" by some folks (so this ticket shows up in those searches). See also: http://bugs.python.org/issue813299 http://bugs.python.org/issue7464 http://bugs.python.org/

[issue16452] Add support for weak reference to bound methods

2012-11-11 Thread Simon Feltman
Simon Feltman added the comment: Indeed a duplicate of: http://bugs.python.org/issue14631 -- resolution: -> duplicate status: open -> closed ___ Python tracker <http://bugs.python.org/i

[issue16452] Add support for weak reference to bound methods

2012-11-11 Thread Simon Feltman
New submission from Simon Feltman: This is a feature request to include a "WeakMethod" or similar object to the weakref module. The object decomposes a bound method and holds a weakref to the object and unbound function. This can be a very useful utility in signal and ui based p

[issue15715] __import__ now raises with non-existing items in fromlist in 3.3

2012-08-16 Thread Simon Feltman
Simon Feltman added the comment: Should have been "...Python 2.5 which it looks like importlib is NOT available." -- ___ Python tracker <http://bugs.python.o

[issue15715] __import__ now raises with non-existing items in fromlist in 3.3

2012-08-16 Thread Simon Feltman
Simon Feltman added the comment: I think pygobject still supports Python 2.5 which it look like importlib is available. I've submitted a patch to pygobject which will work regardless of if this regression is fixed or not: https://bugzilla.gnome.org/show_bug.cgi?id=6

[issue15715] __import__ now raises with non-existing items in fromlist in 3.3

2012-08-16 Thread Simon Feltman
Changes by Simon Feltman : -- type: -> behavior ___ Python tracker <http://bugs.python.org/issue15715> ___ ___ Python-bugs-list mailing list Unsubscri

[issue15715] __import__ now raises with non-existing items in fromlist in 3.3

2012-08-16 Thread Simon Feltman
New submission from Simon Feltman: This came up while trying to build pygobject with Python 3.3. The problem is there are some erroneous imports in the fromlist with these bindings that can easily be fixed. But it is a behavioral change so I just wanted to raise awareness if it is not already