[issue6483] Modules are not deallocated correctly if m_size = -1

2014-02-03 Thread Arfrever Frehtes Taifersar Arahesis
Changes by Arfrever Frehtes Taifersar Arahesis : -- nosy: +Arfrever ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscrib

[issue6483] Modules are not deallocated correctly if m_size = -1

2014-02-03 Thread Mark Lawrence
Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p

[issue6483] Modules are not deallocated correctly if m_size = -1

2013-05-26 Thread Mark Lawrence
Mark Lawrence added the comment: Please correct me if I'm wrong but I believe this applies to all Python 3 versions. -- nosy: +BreamoreBoy versions: +Python 3.3, Python 3.4 ___ Python tracker __

[issue6483] Modules are not deallocated correctly if m_size = -1

2010-04-25 Thread Antoine Pitrou
Antoine Pitrou added the comment: Well, in 2.x you didn't even have the choice. The dict of an extension module was always copied, becoming essentially immortal. In 3.x you can use an m_size>=0 so as to disable this behaviour. -- nosy: +pitrou versions: +Python 3.2 __

[issue6483] Modules are not deallocated correctly if m_size = -1

2010-04-20 Thread Julian Andres Klode
Julian Andres Klode added the comment: This bug still exists in Python 3.1.2. -- ___ Python tracker ___ ___ Python-bugs-list mailing l

[issue6483] Modules are not deallocated correctly if m_size = -1

2009-07-15 Thread Julian Andres Klode
Julian Andres Klode added the comment: I believe this may be related to Python/import.c (l. 592): def->m_base.m_copy = PyDict_Copy(dict); It creates a copy of the module dictionary, but the reference count of this copy is not decreased when the module object is deallocated, thus causing the

[issue6483] Modules are not deallocated correctly if m_size = -1

2009-07-14 Thread Benjamin Peterson
Changes by Benjamin Peterson : -- assignee: -> loewis nosy: +loewis ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscri

[issue6483] Modules are not deallocated correctly if m_size = -1

2009-07-14 Thread Julian Andres Klode
New submission from Julian Andres Klode : The documentation states that m_size should be -1 if no additional memory is needed. But this causes the objects inside the module to not be deallocated at all. The attached module (test) stores an object of a type 'Test', which prints "Deallocation is h