| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
This makes sense to me, but I want to run it through a huge pile of tests at work just to see what - if any - oddball code was relying on passing ignored values. I hope nothing. I'll do that this week.
Sorry, something went wrong.
|
Thank you! In the meantime, I will change the What's new entry. |
Sorry, something went wrong.
|
note to self: I included this PR in an internal test run today, I'll have results by tonight/tomorrow. |
Sorry, something went wrong.
|
hypothesis failures are not related. |
Sorry, something went wrong.
|
I found only a single instance of a parameter being passed to RLock via testing this change in our huge codebase at work: threading.RLock(verbose=True) That code was originally written for Python 2.7 which did support an undocumented verbose argument on threading.RLock. https://github.com/python/cpython/blob/v2.7.18/Lib/threading.py#L132 Easy to fix. But it does suggest that we should just do this API change via our usual DeprecationWarning cycle rather than just assuming we can make it without notice. |
Sorry, something went wrong.
|
|
||
| * Passing any arguments to :func:`threading.RLock` is now restricted. | ||
| Previously C version allowed any numbers of args and kwargs, | ||
| but they were just ignored. Python version never allowed any arguments. |
There was a problem hiding this comment.
This statement isn't accurate; Python <= 2.7 and 3.1 accepted a single undocumented verbose argument.
Sorry, something went wrong.
| Lock = _allocate_lock | ||
|
|
||
| def RLock(*args, **kwargs): | ||
| def RLock(): |
There was a problem hiding this comment.
Lets do a regular DeprecationWarning API change cycle on this.
if args or kwargs:
warnings.warn(DeprecationWarning, ...)
we can put that in 3.12 remove the ignored args/kwargs in 3.14.
Sorry, something went wrong.
There was a problem hiding this comment.
I thought that 3.12 is now only accepting bugfixes, isn't it? I would prefer to have this change as safe as possible and to put it in 3.13+. Unless you insist :)
Sorry, something went wrong.
|
A Python core developer has requested some changes be made to your pull request before we can consider merging it. If you could please address their requests along with any other requests in other reviews from core developers that would be appreciated. Once you have made the requested changes, please leave a comment on this pull request containing the phrase I have made the requested changes; please review again. I will then notify any core developers who have left a review that you're ready for them to take another look at this pull request. And if you don't make the requested changes, you will be poked with soft cushions! |
Sorry, something went wrong.
|
I have made the requested changes; please review again |
Sorry, something went wrong.
|
Thanks for making the requested changes! @gpshead: please review the changes made to this pull request. |
Sorry, something went wrong.
|
@gpshead now this is deprecated in 3.13 and stated to be changed in 3.15 :) |
Sorry, something went wrong.
|
Closing and re-opening to retrigger CLA checks. Sorry for the noise. |
Sorry, something went wrong.
|
Thanks everyone! CI is now green :) |
Sorry, something went wrong.
|
Can someone please click "merge"? :) |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
I hope that this is not really a breaking change. Here's my reasoning:
As the next step, I will propose to deprecate the Python version.