[issue11349] _pickle should implement the module finalisation protocol

2013-12-01 Thread Alexandre Vassalotti
Alexandre Vassalotti added the comment: I have implemented PEP 3121 module finalization for _pickle in 64c6d52793be. -- assignee: -> alexandre.vassalotti nosy: +alexandre.vassalotti resolution: -> fixed stage: needs patch -> committed/rejected status: open -> closed __

[issue11349] _pickle should implement the module finalisation protocol

2011-05-09 Thread STINNER Victor
Changes by STINNER Victor : -- nosy: +haypo ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.

[issue11349] _pickle should implement the module finalisation protocol

2011-03-01 Thread Benjamin Peterson
Benjamin Peterson added the comment: http://mail.python.org/pipermail/python-dev/2009-October/093057.html 2011/3/1 Antoine Pitrou : > > Antoine Pitrou added the comment: > > Not sure why #812369 is bogged down. The patch simply needs updating for 3.x. > > -- > nosy: +pitrou > > ___

[issue11349] _pickle should implement the module finalisation protocol

2011-03-01 Thread Antoine Pitrou
Antoine Pitrou added the comment: Not sure why #812369 is bogged down. The patch simply needs updating for 3.x. -- nosy: +pitrou ___ Python tracker ___ _

[issue11349] _pickle should implement the module finalisation protocol

2011-03-01 Thread Nick Coghlan
Nick Coghlan added the comment: We might be able to tapdance our way around the issue by falling back to the old mechanism when dealing with extension modules without traverse/clear/dealloc methods. -- ___ Python tracker

[issue11349] _pickle should implement the module finalisation protocol

2011-02-28 Thread Benjamin Peterson
Benjamin Peterson added the comment: It's a chicken and egg problem because proper module finalization techniques like #812369 are bogged down by static globals in extension modules, and proper state storage in modules is prevented by proper module finalization. -- __

[issue11349] _pickle should implement the module finalisation protocol

2011-02-28 Thread Nick Coghlan
Nick Coghlan added the comment: In that case, the request should probably read "_pickle should implement the module finalisation protocol, and module finalisation should be designed so that doing so isn't a recipe for segfaults". It strikes me as being very similar to the existing problems we

[issue11349] _pickle should implement the module finalisation protocol

2011-02-27 Thread Benjamin Peterson
Benjamin Peterson added the comment: Unfortunately "proper" module finalization is an invitation to more segfaults because modules can be finalized before objects in them are, resulting in segfaults when its attempted to access modules. -- nosy: +benjamin.peterson ___

[issue11349] _pickle should implement the module finalisation protocol

2011-02-27 Thread Andreas Stührk
Changes by Andreas Stührk : -- nosy: +Trundle ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

[issue11349] _pickle should implement the module finalisation protocol

2011-02-27 Thread Nick Coghlan
New submission from Nick Coghlan : As discussed in issue11321, _pickle allocates a number of module level objects, but doesn't use the appropriate PEP 3121 mechanisms to manage their lifecycle. It should be updated to follow the relevant development guidelines in the documentation. --