-
Notifications
You must be signed in to change notification settings - Fork 38
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-2.6.0 breaks pythonXX build #1129
Comments
Upstream has fixed python38 and above, so we can grab their patches:
Several suits of packages and a few one-offs are hardcoded to python37, so we should look at backporting a fix there:
Fink has dist-restricted python{34,35,36} to OS X 10.15 and below. Should we bother keeping 34/35/36 limping along by trying to backport upstream's fixes for newer pythonXX, or use this as a chance to kill them outright?
Some packages are pinned to python27, so we should look at backporting a fix there:
|
Upstream patch does not apply cleanly to 36 and below (nor to 27's, where the test failure looks different also) |
py34-36 are already dist restricted. If they can't be patched for this failure with only minimal effort, then the test can be easily skipped. That's less effort than deleting python3[456].info and modifying all existing *-py.info to remove relevant variants. Is there any indication that expat-2.6 breaks actual python function or just tickles that test? |
Python36 and below also are failing test_minidom; again looks like a test bug, as copying that test suite from newer pythonXX clears it on python{35,36}. On older, it doesn't apply as cleanly...still working on it. |
Python-upstream confirms there are test-failures due to the just-released expat-2.6.0 and has fixes. python/cpython#115133
Originally posted by @dmacks in #996 (comment)
The text was updated successfully, but these errors were encountered: