➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Safihre
Recipients Dima.Tisnek, Matthew Rocklin, Safihre, barry, benjamin.peterson, christian.heimes, jakirkham, josnyder, njs, pablogsal, paul.moore, r.david.murray, steve.dower, tim.golden, vstinner, yselivanov, zach.ware
Date 2022-03-13.20:35:59
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1647203759.64.0.56018760675.issue37355@roundup.psfhosted.org>
In-reply-to
Content 
Implementing for write is not needed as OpenSSL's SSL_write_ex that is used by write() already writes the whole buffer at once. Only reading OpenSSL does in the 16k segments.

The new option was introduced to prevent the compatibility problems for code that would not expect the EOF being read in a sinhle read(), as Josh explained in his initial PR. This way the faster (but breaking) behavior can be enabled explicitly. 

The info is also in the PR, in case there is time to review in the future.
History
Date User Action Args
2022-03-13 20:35:59Safihresetrecipients: + Safihre, barry, paul.moore, vstinner, christian.heimes, tim.golden, benjamin.peterson, r.david.murray, njs, Dima.Tisnek, zach.ware, yselivanov, steve.dower, pablogsal, Matthew Rocklin, josnyder, jakirkham
2022-03-13 20:35:59Safihresetmessageid: <1647203759.64.0.56018760675.issue37355@roundup.psfhosted.org>
2022-03-13 20:35:59Safihrelinkissue37355 messages
2022-03-13 20:35:59Safihrecreate