-
-
Notifications
You must be signed in to change notification settings - Fork 32k
3.13.0b3: undocumented change in inspect.isroutine()
for functools.partial
#122087
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
Comments
I added the release-blocker label to make sure this is addressed one way or another before RC1 on the 30th. |
Reviewing the issue, I suspect In the backport PR, https://github.com/python/cpython/pull/121092/files#diff-b89cd06e4637abacb73f2500301ff979a67ad7ecbfa7cf151c7243715898d7eaL2558 adjusted |
@serhiy-storchaka, will you be able to look at this before rc1? |
Unfortunately, the only way to add a warning about a partial object being made a method descriptor in the future is to make it a method descriptor. We can make |
What's the expected result in 3.14? Is |
…tial objects They return now False again.
…ith partial objects
…rtial objects (GH-122218) Now they return False again.
Documentation
While investigating encode/starlette#2648, I've noticed that the behavior of
inspect.isroutine()
changed with regards tofunctools.partial()
.Please consider the following sample:
Prior to 3.13.0b3, it would evaluate to
False
. In newer versions, it evaluates toTrue
.A bisect points out that it changed as a result of 49e5740 (i.e. #121086). Neither the commit message, nor the news entry, hints anything about
inspect.isroutine()
behavior.Could you please clarify whether the change was intentional? And if it was, could we have it explicitly noted in the documentation?
Linked PRs
The text was updated successfully, but these errors were encountered: