Support m_free() in Py3 (PEP 3121)

[robertwb]

This is part of the work towards ticket http://trac.cython.org/ticket/173, however, it can be done much earlier. This would allow module unloading and cleanup in Py3.

It might be enough to always generate the module cleanup code (at least for Py3) and to let m_free() call it.

Migrated from http://trac.cython.org/ticket/218

[robertwb]

scoder commented

It would be nice to get http://trac.cython.org/ticket/144 resolved before this.

[robertwb]

scoder changed milestone from 0.12 to wishlist
commented

[robertwb]

scoder changed description from

This is part of the work towards ticket http://trac.cython.org/ticket/173, however, it can be done much earlier. This would allow module unloading and cleanup in Py3.

It might be enough to always generate the module cleanup code (at least for Py3) and to let m_clear() call it.

to

This is part of the work towards ticket http://trac.cython.org/ticket/173, however, it can be done much earlier. This would allow module unloading and cleanup in Py3.

It might be enough to always generate the module cleanup code (at least for Py3) and to let m_free() call it.
milestone from wishlist to 0.17
owner from somebody to scoder
status from new to assigned
summary from

Support m_clear() in Py3 (PEP 3121)

to

Support m_free() in Py3 (PEP 3121)
commented

[robertwb]

scoder commented

Here is an implementation:

ad5f8e6

[robertwb]

scoder changed resolution to fixed
status from assigned to closed
commented