fix test failures-python sdk building #2544
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
During the process of building the Python SDK from source for versions 3.12.7 and 3.13.0 on Bullseye, we encountered build test failures ( test_xml_etree tests). Apparently, these tests having been failing from a very long time, but these are no longer ignored due to recent changes in that test repo
These tests have been deprecated in Expat version 2.6.3. To resolve this, we removed the --with-system-expat option, ensuring that the build uses the Expat XML parser library (version 2.6.3) included in the Python source.
This is a prevalent issue, and these links contains discussions on this issue.
python/cpython#125067
python/cpython#110276