[issue9591] kqueu not reporting EOF under certain circumstances

New submission from Volodymyr Kostyrko : This one is BSD related. FreeBSD 8.1. This works: # cat test.py | ./test.py -1 684 32768 0 0 # This hangs: # ./test.py < file -1 684 0 0 0 The difference is that in second case popped kevent lacks any data on EOF. -- components: Library (

[issue9591] kqueue not reporting EOF under certain circumstances

Changes by Volodymyr Kostyrko : -- title: kqueu not reporting EOF under certain circumstances -> kqueue not reporting EOF under certain circumstances ___ Python tracker <http://bugs.python.org/iss

[issue9591] kqueue not reporting EOF under certain circumstances

Volodymyr Kostyrko added the comment: Ok, I'll try to ask FreeBSD developers, too bad I'm not that familiar with C to write example other way than test if it's a system problem. -- nosy: -terry.reedy ___ Python tracker <http

[issue9591] kqueue not reporting EOF under certain circumstances

Volodymyr Kostyrko added the comment: I was wrong. The current behavior is correct. The difference between execution is a difference between pipe file object and vnode file object. vnode backed file objects doesn't send any signals and care should be taken to detect file pos