bpo-42854: Correctly use size_t for _ssl._SSLSocket.read and _ssl._SSLSocket.write#27271
bpo-42854: Correctly use size_t for _ssl._SSLSocket.read and _ssl._SSLSocket.write#27271pablogsal merged 1 commit into
Conversation
tiran
left a comment
There was a problem hiding this comment.
There are a bunch of warnings related to signed and unsigned comparison, e.g. comparison of integer expressions of different signedness: ‘size_t’ {aka ‘long unsigned int’} and ‘Py_ssize_t’ {aka ‘long int’} [-Wsign-compare]. Maybe use Py_ssize_t?
Sorry, something went wrong.
|
When you're done making the requested changes, leave the comment: |
Sorry, something went wrong.
|
I'm landing this as there is no compiler warnings anymore and I don't want to commit this very close to the rc. |
Sorry, something went wrong.
|
Thanks @pablogsal for the PR 🌮🎉.. I'm working now to backport this PR to: 3.10. |
Sorry, something went wrong.
…LSocket.write (pythonGH-27271) (cherry picked from commit 83d1430) Co-authored-by: Pablo Galindo Salgado <Pablogsal@gmail.com>
…_ssl._SSLSocket.write (pythonGH-27271)" This reverts commit 83d1430.
…_ssl._SSLSocket.write (pythonGH-27271)" This reverts commit 83d1430.
https://bugs.python.org/issue42854