-
-
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
Remove old-deprecated ElementTree features #73395
Comments
Proposed patch removes old-deprecated ElementTree features.
Unfortunately some of these deprecations are in the documentation only or in Python implementatation, but not in C implementatation. Perhaps missed warnings should be added first (see bpo-29204). But if commit the patch from bpo-29204 in 3.6, perhaps deprecated features could be removed in 3.7. |
Patch looks right to me. I'd personally be ok with applying it to 3.7, but I'll leave the decision to you. Most of the removed "features" are non-controversial, except:
So, this will have an impact on user code, despite any previous deprecation warnings. But it's easy to resolve in a backwards compatible way. |
Serhiy, Did you want to revive this for 3.8? |
getchildren() and getiterator() have deprecation notes in their docstrings in lxml.etree. |
PR 6769 removes the html parameter and the doctype() method. getchildren() and getiterator() emit now a DeprecationWarning instead of PendingDeprecationWarning and will be removed in 3.9. |
The following two patches will remove getchildren() and getiterator() (in 3.9) and xml.etree.cElementTree (in an unspecified future). |
This should be closed. |
The rest will be removed in bpo-36543. |
The getchildren method was deprecated in python2.7 and is removed 3.10 See: - python/cpython#73395 - python/cpython#80724
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: