[issue16834] ioctl mutate_flag behavior in regard to the buffer size limit

Change by Irit Katriel : -- versions: +Python 3.10, Python 3.8, Python 3.9 -Python 2.6, Python 3.4 ___ Python tracker ___ ___ Python

[issue16834] ioctl mutate_flag behavior in regard to the buffer size limit

Change by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue16834] ioctl mutate_flag behavior in regard to the buffer size limit

Martin Panter added the comment: Looking at the C code, if a writable buffer is passed, mutate_arg is false, and the buffer is longer than 1024 bytes, then a ValueError is raised: >>> ioctl(0, 0, bytearray(2048), False) Traceback (most recent call last): File "", line 1, in ValueError: ioctl

[issue16834] ioctl mutate_flag behavior in regard to the buffer size limit

Mark Lawrence added the comment: @Yuval sorry about the delay in replying. Can a *nix person comment on this please as I stick with Windows. -- nosy: +BreamoreBoy ___ Python tracker __

[issue16834] ioctl mutate_flag behavior in regard to the buffer size limit

New submission from Yuval Weinbaum: In fcntl module, the documentation states the following regarding the mutate_flag in ioctl method: *** If it is false, the buffer’s mutability is ignored and behaviour is as for a read-only buffer, except that the 1024 byte limit mentioned above is avoided –