-
-
Notifications
You must be signed in to change notification settings - Fork 32.1k
gh-129843: Fix the wrong argument passed - converting positional argument to named argument #129848
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
Conversation
argument to named argument
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.
not sure, if this need an entry to news? it seems to be a kind of bug fix to me, isn't it?
Yes, It is a bug fix, and i do not think it warrants a news entry. |
It still needs a NEWS IMO because it's still a change that users may be happy to know. Something along the lines "Fix Python implementation of :func:`warnings.warn_explicit`." |
@picnixz Done |
Misc/NEWS.d/next/Library/2025-03-17-15-45-36.gh-issue-129843.NPdpXL.rst
Outdated
Show resolved
Hide resolved
Thanks @srinivasreddy for the PR, and @picnixz for merging it 🌮🎉.. I'm working now to backport this PR to: 3.12, 3.13. |
…licit` (pythonGH-129848) The pure Python implementation of `warnings.warn_explicit` constructs a `WarningMessage` with an incorrect source (it incorrectly sets the WarningMessage's line to the given `source`). (cherry picked from commit 80e00ec) Co-authored-by: Srinivas Reddy Thatiparthy (తాటిపర్తి శ్రీనివాస్ రెడ్డి) <[email protected]>
GH-131349 is a backport of this pull request to the 3.13 branch. |
…licit` (pythonGH-129848) The pure Python implementation of `warnings.warn_explicit` constructs a `WarningMessage` with an incorrect source (it incorrectly sets the WarningMessage's line to the given `source`). (cherry picked from commit 80e00ec) Co-authored-by: Srinivas Reddy Thatiparthy (తాటిపర్తి శ్రీనివాస్ రెడ్డి) <[email protected]>
GH-131350 is a backport of this pull request to the 3.12 branch. |
…plicit` (GH-129848) (#131349) gh-129843: fix pure Python implementation of `warnings.warn_explicit` (GH-129848) The pure Python implementation of `warnings.warn_explicit` constructs a `WarningMessage` with an incorrect source (it incorrectly sets the WarningMessage's line to the given `source`). (cherry picked from commit 80e00ec) Co-authored-by: Srinivas Reddy Thatiparthy (తాటిపర్తి శ్రీనివాస్ రెడ్డి) <[email protected]>
…plicit` (GH-129848) (#131350) gh-129843: fix pure Python implementation of `warnings.warn_explicit` (GH-129848) The pure Python implementation of `warnings.warn_explicit` constructs a `WarningMessage` with an incorrect source (it incorrectly sets the WarningMessage's line to the given `source`). (cherry picked from commit 80e00ec) Co-authored-by: Srinivas Reddy Thatiparthy (తాటిపర్తి శ్రీనివాస్ రెడ్డి) <[email protected]>
…licit` (python#129848) The pure Python implementation of `warnings.warn_explicit` constructs a `WarningMessage` with an incorrect source (it incorrectly sets the WarningMessage's line to the given `source`).
…licit` (python#129848) The pure Python implementation of `warnings.warn_explicit` constructs a `WarningMessage` with an incorrect source (it incorrectly sets the WarningMessage's line to the given `source`).
Uh oh!
There was an error while loading. Please reload this page.