Skip to content

Extend catching of ValueError to 3.12.5+ #10610

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Oct 4, 2025
Merged

Extend catching of ValueError to 3.12.5+ #10610

merged 1 commit into from
Oct 4, 2025

Conversation

jacobtylerwalls
Copy link
Member

@jacobtylerwalls jacobtylerwalls commented Oct 4, 2025 •
edited
Loading

Refs #9138 (comment)

Closes #9138

@jacobtylerwalls jacobtylerwalls added Maintenance Discussion or action around maintaining pylint or the dev workflow Skip news 🔇 This change does not require a changelog entry backport maintenance/3.3.x labels Oct 4, 2025
@codecov Codecov
Copy link

codecov bot commented Oct 4, 2025 •
edited
Loading

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.96%. Comparing base (0871a4d) to head (c0e0ce2).
⚠️ Report is 7 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main   #10610   +/-   ##
=======================================
  Coverage   95.95%   95.96%           
=======================================
  Files         176      176           
  Lines       19476    19470    -6     
=======================================
- Hits        18689    18684    -5     
+ Misses        787      786    -1
Files with missing lines Coverage Δ
pylint/__init__.py 97.05% <100.00%> (+2.94%) ⬆️

... and 3 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Oct 4, 2025

🤖 According to the primer, this change has no effect on the checked open source code. 🤖🎉

This comment was generated for commit c0e0ce2

@jacobtylerwalls jacobtylerwalls merged commit 19f7a5e into pylint-dev:main Oct 4, 2025
50 checks passed
@jacobtylerwalls jacobtylerwalls deleted the jtw/value-error branch October 4, 2025 20:07
pylint-backport bot pushed a commit that referenced this pull request Oct 4, 2025
@jacobtylerwalls @pylint-backport
Extend catching of ValueError to 3.12.5+ (#10610)
d2819f5 
(cherry picked from commit 19f7a5e)
@pylint-backport pylint-backport bot mentioned this pull request Oct 4, 2025
Merged
jacobtylerwalls added a commit that referenced this pull request Oct 4, 2025
@pylint-backport @jacobtylerwalls
[Backport maintenance/3.3.x] Extend catching of ValueError to 3.12.5+ (…
81fb483 
…#10611)

Extend catching of ValueError to 3.12.5+ (#10610)

(cherry picked from commit 19f7a5e)

Co-authored-by: Jacob Walls <jacobtylerwalls@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Pierre-Sassoulas Pierre-Sassoulas Pierre-Sassoulas approved these changes

@DanielNoord DanielNoord DanielNoord approved these changes

Assignees

No one assigned

Labels

backport maintenance/3.3.x Maintenance Discussion or action around maintaining pylint or the dev workflow Skip news 🔇 This change does not require a changelog entry

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Python 3.12 - ValueError: generator already executing

3 participants

@jacobtylerwalls @Pierre-Sassoulas @DanielNoord