-
-
Notifications
You must be signed in to change notification settings - Fork 30.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
bpo-45948: Remove constructor discrepancy in C version of ElementTree.XMLParser
#31152
Conversation
Thanks @jacobtylerwalls for the PR, and @serhiy-storchaka for merging it 🌮🎉.. I'm working now to backport this PR to: 3.9, 3.10. |
….XMLParser (pythonGH-31152) Both implementations accept target=None now. (cherry picked from commit 168fd64) Co-authored-by: Jacob Walls <[email protected]>
Sorry, @jacobtylerwalls and @serhiy-storchaka, I could not cleanly backport this to |
GH-31292 is a backport of this pull request to the 3.10 branch. |
….XMLParser (GH-31152) Both implementations accept target=None now. (cherry picked from commit 168fd64) Co-authored-by: Jacob Walls <[email protected]>
…ntTree.XMLParser (pythonGH-31152) Both implementations accept target=None now. (cherry picked from commit 168fd64)
GH-31299 is a backport of this pull request to the 3.9 branch. |
…ntTree.XMLParser (pythonGH-31152) (pythonGH-31299) Both implementations accept target=None now. (cherry picked from commit 168fd64)
bpo-45948
Bring the C implementation of
ElementTree
into agreement with the Python implementation (and the docs) if an explicittarget=None
is provided toXMLParser
. In that case, provide a defaultTreeBuilder
.This already worked if the
target
keyword was omitted. It's possible the reporter only discovered the discrepancy when the arguments went keyword-only in 3.8.https://bugs.python.org/issue45948