GeezerVison is showing github.com — gh-90765: Catch LegacyInterpolation deprecation warning by hugovk · Pull Request #91480 · python/cpython
Conversation
hugovk
commented
Apr 12, 2022
•
edited
Loading
Uh oh!
There was an error while loading. Please reload this page.
Follow on from gh-90765, see #30927 (comment).
Before
$ PYTHONWARNINGS=always ./python.exe -Wall -m test test_configparser
Raised RLIMIT_NOFILE: 256 -> 1024
0:00:00 load avg: 5.65 Run tests sequentially
0:00:00 load avg: 5.65 [1/1] test_configparser
/Users/huvankem/github/cpython/Lib/test/test_configparser.py:1031: DeprecationWarning: LegacyInterpolation has been deprecated since Python 3.2 and will be removed from the configparser module in Python 3.13. Use BasicInterpolation or ExtendedInterpolation instead.
interpolation = configparser.LegacyInterpolation()
== Tests result: SUCCESS ==
1 test OK.
Total duration: 476 ms
Tests result: SUCCESS
After
$ PYTHONWARNINGS=always ./python.exe -Wall -m test test_configparser
Raised RLIMIT_NOFILE: 256 -> 1024
0:00:00 load avg: 5.67 Run tests sequentially
0:00:00 load avg: 5.67 [1/1] test_configparser
== Tests result: SUCCESS ==
1 test OK.
Total duration: 468 ms
Tests result: SUCCESS
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
ghost
commented
Apr 12, 2022
•
edited by ghost
Loading
Uh oh!
There was an error while loading. Please reload this page.
|
All commit authors signed the Contributor License Agreement. 
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
hugovk
changed the title
bpo-46607: Catch LegacyInterpolation deprecation warning
gh-90765: Catch LegacyInterpolation deprecation warning
Apr 12, 2022
|
@tirkarthi Does this need a news file or skip-news label?
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
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.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
All commit authors signed the Contributor License Agreement. 
@ambv any idea why the CLA CI check is red, even though the comment here says it's green?
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
I have already signed the old CLA. When I first created the PR, the CLA comment was red:

So I clicked the link to sign the new one anyway. It turned the comment green but not the check:

|
AlexWaygood reacted with confused emoji
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Assignees
No one assigned
Milestone
No milestone
Development
Successfully merging this pull request may close these issues.
Uh oh!
There was an error while loading. Please reload this page.
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.
|