[issue2116] weakref copy module interaction

2009-05-15 Thread Antoine Pitrou
Antoine Pitrou added the comment: Committed in r72662, r72670. Thanks! -- resolution: -> fixed status: open -> closed ___ Python tracker ___

[issue2116] weakref copy module interaction

2009-05-01 Thread Antoine Pitrou
Antoine Pitrou added the comment: Raymond, Guido, any opinion on this one? -- assignee: tim_one -> nosy: +gvanrossum, rhettinger stage: -> patch review versions: +Python 2.7, Python 3.1 -Python 2.5 ___ Python tracker

[issue2116] weakref copy module interaction

2009-03-14 Thread Antoine Pitrou
Antoine Pitrou added the comment: Updated patch so that copied weakdicts are decoupled (adding an item to the copy doesn't mutate the original). -- Added file: http://bugs.python.org/file13335/issue2116-2.patch ___ Python tracker

[issue2116] weakref copy module interaction

2009-03-14 Thread Antoine Pitrou
Antoine Pitrou added the comment: Here is a patch providing proper copy and deepcopy support, including for weak dicts (the Proxy type is unsupported, though). -- Added file: http://bugs.python.org/file13334/issue2116.patch ___ Python tracker

[issue2116] weakref copy module interaction

2009-03-14 Thread Antoine Pitrou
Antoine Pitrou added the comment: Hmm, forget that question. If we deepcopy the weakref target, it will be destroyed just afterwards, making the deepcopied weakref useless. -- ___ Python tracker ___

[issue2116] weakref copy module interaction

2009-03-14 Thread Antoine Pitrou
Antoine Pitrou added the comment: Should a deepcopy of a weakref return the same weakref, or a weakref to a new copied object? Also, what about the optional callback? -- nosy: +pitrou ___ Python tracker ___

[issue2116] weakref copy module interaction

2008-04-03 Thread Rick Harris
Rick Harris <[EMAIL PROTECTED]> added the comment: Sorry about forgetting the -c arg! The patch is intended for python/trunk/Lib/copy.py. It looks like Raymond Hettinger has made a similar-ish change recently to make Ellipsis copyable. __ Tracker <[EMAIL PROTECTE

[issue2116] weakref copy module interaction

2008-03-19 Thread Sean Reifschneider
Sean Reifschneider <[EMAIL PROTECTED]> added the comment: Rick: In the future, please provide a context or unified diff ("diff -c") so that we get the file name that the diff is for and some additional context. -- assignee: -> tim_one keywords: +patch nosy: +jafo, tim_one priority: ->

[issue2116] weakref copy module interaction

2008-02-14 Thread Rick Harris
New submission from Rick Harris: The copy module will not properly copy/deepcopy weakrefs, it will bomb out with __new__ not having enough args. This is a problem b/c it makes deepcopying of objects that make use of Weak(Key|Value)Dictionaries difficult. To replicate: import copy, weakref class