[issue18660] os.read behavior on Linux

Louis Riviere added the comment: Thanks Benjamin ! I should have known that "Python doesn't break things" :) -- ___ Python tracker ___ ___

[issue18660] os.read behavior on Linux

Benjamin Peterson added the comment: This is not a Python bug. Linux is just not accepting "0" as a valid size argument to read(). You don't see this using libc.read because you don't check errno. Just don't call os.read() if size == 0. -- resolution: -> invalid status: open -> closed

[issue18660] os.read behavior on Linux

Benjamin Peterson added the comment: Can you please explain what the bug is in Python; that is, what exactly was wrong with os.read? -- nosy: +benjamin.peterson ___ Python tracker _

[issue18660] os.read behavior on Linux

Changes by Tshepang Lekhonkhobe : -- nosy: +tshepang ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mai

[issue18660] os.read behavior on Linux

Changes by Ronald Oussoren : -- nosy: +ronaldoussoren ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://ma

[issue18660] os.read behavior on Linux

New submission from Louis RIVIERE: A call to os.read that used to work on older Linux kernel, doesn't anymore with newer Linux kernel. As a workaroud we can use libc.read (ctypes) instead of os.read. But I feel like os.read should work, as it used to. The code (and comments) can be seen here :