This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author alecsandru.patrascu
Recipients alecsandru.patrascu, benjamin.peterson, brett.cannon, martin.panter, pitrou, serhiy.storchaka, skrah, vstinner, yselivanov
Date 2016-02-08.13:48:17
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1454939298.76.0.390085078063.issue26285@psf.upfronthosting.co.za>
In-reply-to
Content
I attached the list for CPython3 (gc-removed-zones-cpython3.txt), but now split in two sections (core and parser), for more clarity as from what and where it is removed. As you can see, the reason why the module works is because the API that can be used by modules remains untouched.

What I was trying to say and prove before is that these GCC/LD flags are safe to use in CPython (and for any other software project) and will not break any compatibility with existing or future modules.
History
Date User Action Args
2016-02-08 13:48:18alecsandru.patrascusetrecipients: + alecsandru.patrascu, brett.cannon, pitrou, vstinner, benjamin.peterson, skrah, martin.panter, serhiy.storchaka, yselivanov
2016-02-08 13:48:18alecsandru.patrascusetmessageid: <1454939298.76.0.390085078063.issue26285@psf.upfronthosting.co.za>
2016-02-08 13:48:18alecsandru.patrasculinkissue26285 messages
2016-02-08 13:48:18alecsandru.patrascucreate