-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
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
bpo-30266: support "= None" pattern in AbstractContextManager #1448
Conversation
@JelleZijlstra, thanks for your PR! By analyzing the history of the files in this pull request, we identified @ncoghlan, @berkerpeksag and @Yhg1s to be potential reviewers. |
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.
Could you please add a note to Misc/NEWS
?
Done, thanks for the review. |
It looks like a fourth merge is required... |
Pinging @berkerpeksag -- is this now to your satisfaction? Could we get it in 3.6.3? (I.e. before Monday June 12.) |
This seems simple enough, I'm merging it. |
@Mariatta Can you help backporting this to 3.6? |
…ythonGH-1448) contextlib.AbstractContextManager now supports anti-registration by setting __enter__ = None or __exit__ = None, following the pattern introduced in bpo-25958.. (cherry picked from commit 57161aa)
No description provided.