[issue40262] SSL recv_into requires the object to implement __len__ unlike socket one

Change by Zackery Spytz : -- keywords: +patch nosy: +ZackerySpytz nosy_count: 3.0 -> 4.0 pull_requests: +19579 stage: -> patch review pull_request: https://github.com/python/cpython/pull/20310 ___ Python tracker

[issue40262] SSL recv_into requires the object to implement __len__ unlike socket one

Serhiy Storchaka added the comment: Yes, it is a bug. __len__ can return a value different from the amount of bytes (in array.array, memoryview). len(buffer) can be replaced with memoryview(buffer).nbytes, but maybe we could keep None and let the lower level to handle it. -- nosy:

[issue40262] SSL recv_into requires the object to implement __len__ unlike socket one

Change by Terry J. Reedy : -- versions: -Python 3.6 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue40262] SSL recv_into requires the object to implement __len__ unlike socket one

New submission from tzickel : I am writing this as a bug, as I have an object which implements the buffer protocol but not the __len__. SSL's recv_into seems to require the buffer object to implement __len__, but this is unlike the socket recv_into which uses the buffer protocol length.