-
-
Notifications
You must be signed in to change notification settings - Fork 29.9k
New issue
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
expat: Restore the use of pyexpatns.h to avoid link time conflicts vs other versions #79192
Comments
These lines used to exist in Modules/expat/expat_external.h: /* Namespace external symbols to allow multiple libexpat version to
co-exist. */
#include "pyexpatns.h" 5dc3f23#diff-3afaf7274c90ce1b7405f75ad825f545 removed them during an expat upgrade. This causes link time conflicts when embedding Python using its own expat in an application that also uses libexpat from the C/C++ side on its own. |
Not a release blocker as most users probably do not run into this problem, but the pyexpatns.h mechanics should be restored. |
This appears to not have been shipped in a release yet. It is new in 3.6.7. cc'ing ned daily to see if he wants to include the fix (the PR is trivial, coming ASAP). I don't have a good feel for how this impacts the real world or not. We noticed because we embed CPython in larger applications that use a different copy of libexpat on their own. |
Sorry for breaking that, and thanks for the fix! I'm curious, though, why are you still using the embedded expat rather than linking everything against the same expat? |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: