-
-
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
gh-128731: Fix ResourceWarning in robotparser.RobotFileParser.read() #128733
gh-128731: Fix ResourceWarning in robotparser.RobotFileParser.read() #128733
Conversation
serhiy-storchaka
commented
Jan 11, 2025
•
edited by bedevere-app
bot
Loading
edited by bedevere-app
bot
- Issue: ResourceWarning in test_robotparser #128731
Misc/NEWS.d/next/Library/2025-01-11-13-40-12.gh-issue-128731.qpKlai.rst
Outdated
Show resolved
Hide resolved
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.
The warning is gone with this change:
» ./python.exe -m test test_robotparser
Using random seed: 3011282491
0:00:00 load avg: 3.90 Run 1 test sequentially in a single process
0:00:00 load avg: 3.90 [1/1] test_robotparser
== Tests result: SUCCESS ==
1 test OK.
Total duration: 81 ms
Total tests: run=60 skipped=1
Total test files: run=1/1
Result: SUCCESS
Thanks @serhiy-storchaka for the PR 🌮🎉.. I'm working now to backport this PR to: 3.12, 3.13. |
…ead() (pythonGH-128733) (cherry picked from commit 5e65a1a) Co-authored-by: Serhiy Storchaka <[email protected]>
GH-128755 is a backport of this pull request to the 3.13 branch. |
…ead() (pythonGH-128733) (cherry picked from commit 5e65a1a) Co-authored-by: Serhiy Storchaka <[email protected]>
GH-128756 is a backport of this pull request to the 3.12 branch. |
GH-128755 is a backport of this pull request to the 3.13 branch. |
GH-128756 is a backport of this pull request to the 3.12 branch. |
…otFileParser.read() (GH-128733) (GH-128756) (cherry picked from commit 5e65a1a) Co-authored-by: Serhiy Storchaka <[email protected]>