Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
|
I rebased my PR and I added a NEWS entry. |
0d8f77a
to
00580bc
Compare
|
I reverted the following change: I found an issue between libpython and SOABI: https://mail.python.org/pipermail/python-dev/2019-April/157186.html I will work on a separated PR to remove "d" from SOABI, to handle properly the libpython issue. This PR is not restricted to "Py_DEBUG no longer implies Py_TRACE_REFS". |
|
@pitrou: You approved the idea on the python-dev, would you mind to approve the PR as well? @gvanrossum: Ditto. You approved the idea on the python-dev, would you mind to approve the PR as well? |
Release build and debug build are now ABI compatible: the Py_DEBUG define no longer implies Py_TRACE_REFS define which introduces the only ABI incompatibility. A new "./configure --with-trace-refs" build option is now required to get Py_TRACE_REFS define which adds sys.getobjects() function and PYTHONDUMPREFS environment variable. Changes: * Add ./configure --with-trace-refs * Py_DEBUG no longer implies Py_TRACE_REFS
|
@pablogsal: Thanks, I fixed the 3 typos. |
Release build and debug build are now ABI compatible: the Py_DEBUG
define no longer implies Py_TRACE_REFS define which introduces the
only ABI incompatibility.
A new "./configure --with-trace-refs" build option is now required to
get Py_TRACE_REFS define which adds sys.getobjects() function and
PYTHONDUMPREFS environment variable.
Changes:
https://bugs.python.org/issue36465