-
-
Notifications
You must be signed in to change notification settings - Fork 882
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
use aclosing/closing for async/sync generators #1671
Conversation
looks like OP_NO_(SSL|TLS)* is deprecated is deprecated |
Should we add the |
@Kludex Yes, I'd suggest that we treat that as a separate pull request. |
So, my review at the moment would be that there's several different things being addressed here, and I'd probably rather see each individual thing tackled as a separate PR, which I've always found helps with clean thorough review processes. We've got:
All good stuff, but just needs a bit of separation in order to address each review part with sufficient intent and precision. However, either ways around we really need to wait until #1687 is resolved before we consider pushing on with this. |
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.
Seems like we're good to go with this one? I like the switch to closing
/aclosing
as well, quite neat. Thank you!
It looks like there's a problem with the type annotation of async_generator.aclosing python-trio/trio-typing#31 |
Also the other backport of this: jazzband/contextlib2#27 |
I'm not sure? I'm as convinced of the benefits of this. We're perfectly neat & tidy with our |
blocked by jazzband/contextlib2#42 |
I'd like us to pass on this. The trade-off from replacing two cases of |
No description provided.