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
_SSLProtocolTransport
doesn't have the get_write_buffer_limits
implementation.
#90645
Comments
When calling Traceback (most recent call last):
File "/home/mooncell/works/test.py", line 26, in <module>
asyncio.run(main())
File "/usr/lib/python3.10/asyncio/runners.py", line 44, in run
return loop.run_until_complete(main)
File "/usr/lib/python3.10/asyncio/base_events.py", line 641, in run_until_complete
return future.result()
File "/home/mooncell/works/test.py", line 24, in main
print(transport.get_write_buffer_limits())
File "/usr/lib/python3.10/asyncio/transports.py", line 306, in get_write_buffer_limits
return (self._low_water, self._high_water)
AttributeError: '_SSLProtocolTransport' object has no attribute '_low_water'. Did you mean: '_high_water'? We looked into the implementation and found out that |
_SSLProtocolTransport
doen't have the get_write_buffer_limits
implementation._SSLProtocolTransport
doesn't have the get_write_buffer_limits
implementation.
_SSLProtocolTransport
doen't have the get_write_buffer_limits
implementation._SSLProtocolTransport
doesn't have the get_write_buffer_limits
implementation.
Technically it should not provide the method according to the current design. WriteTransport requires only get_write_buffer_size() and set_write_buffer_limits() *setter* but not get_write_buffer_limits() getter. I agree, looks weird. Would you prepare a pull request? I'm happy to review/merge it. |
Forgot to write, after making the method public we can implement it in SSL transport easily. |
Hey Andrew, thanks for the reply!
Sure.
Apparently so please can you clarify on what did you mean by that? I am sorry this is my first time here. |
Sorry, I didn't look into docs before writing. The PR should contain fixes for transports.py and sslproto.py only (plus a blurb record for NEWs). Sorry for misleading you. |
Done, thanks! |
get_write_buffer_limits
to Write and _SSLProtocol transports #30958get_write_buffer_limits
to Write and _SSLProtocol transports (GH-30958) #31055get_write_buffer_limits
to Write and _SSLProtocol transports (GH-30958) #31056Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: