Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork33.3k
gh-119577: Adjust DeprecationWarning when testing element truth values in ElementTree#119762
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
… values in ElementTree
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
thanks!
Thanks@jacobtylerwalls for the PR, and@gpshead for merging it 🌮🎉.. I'm working now to backport this PR to: 3.13. |
… values in ElementTree (pythonGH-119762)Adjust DeprecationWarning when testing element truth values in ElementTree, we're planning to go with the more natural True return rather than a disruptive harder to code around exception raise, and are deferring the behavior change for a few more releases.(cherry picked from commit6b60652)Co-authored-by: Jacob Walls <jacobtylerwalls@gmail.com>
GH-120189 is a backport of this pull request to the3.13 branch. |
… values in ElementTree (pythonGH-119762)Adjust DeprecationWarning when testing element truth values inElementTree, we're planning to go with the more natural True returnrather than a disruptive harder to code around exception raise, and aredeferring the behavior change for a few more releases.
GH-120190 is a backport of this pull request to the3.12 branch. |
…h values in ElementTree (GH-119762) (GH-120189)gh-119577: Adjust DeprecationWarning when testing element truth values in ElementTree (GH-119762)Adjust DeprecationWarning when testing element truth values in ElementTree, we're planning to go with the more natural True return rather than a disruptive harder to code around exception raise, and are deferring the behavior change for a few more releases.(cherry picked from commit6b60652)Co-authored-by: Jacob Walls <jacobtylerwalls@gmail.com>
… values in ElementTree (pythonGH-119762)Adjust DeprecationWarning when testing element truth values in ElementTree, we're planning to go with the more natural True return rather than a disruptive harder to code around exception raise, and are deferring the behavior change for a few more releases.
… values in ElementTree (pythonGH-119762)Adjust DeprecationWarning when testing element truth values in ElementTree, we're planning to go with the more natural True return rather than a disruptive harder to code around exception raise, and are deferring the behavior change for a few more releases.
… values in ElementTree (pythonGH-119762)Adjust DeprecationWarning when testing element truth values in ElementTree, we're planning to go with the more natural True return rather than a disruptive harder to code around exception raise, and are deferring the behavior change for a few more releases.
…h values in Element tree (GH-119762) (#120190)gh-119577: Adjust DeprecationWarning when testing element truth values in ElementTree (GH-119762)Adjust DeprecationWarning when testing element truth values inElementTree, we're planning to go with the more natural True returnrather than a disruptive harder to code around exception raise, and aredeferring the behavior change for a few more releases.Co-authored-by: Jacob Walls <jacobtylerwalls@gmail.com>
Uh oh!
There was an error while loading.Please reload this page.
Adjust this deprecation warning to refer to returning True regardless of the existence of subelements (rather than raising an exception in 3.14).
I'm not sure whether this should be described as pending for 3.16 or just "future versions".
xml.etree.ElementTree.Element#119577📚 Documentation preview 📚:https://cpython-previews--119762.org.readthedocs.build/