[issue27016] BlockingIOError not raised inside function.

Change by Irit Katriel : -- resolution: -> works for me stage: -> resolved status: pending -> closed ___ Python tracker ___ ___ Py

[issue27016] BlockingIOError not raised inside function.

Irit Katriel added the comment: On a Mac I get the "BlockingIOError: [Errno 35] Resource temporarily unavailable" with both version (with and without the function). -- nosy: +iritkatriel status: open -> pending ___ Python tracker

[issue27016] BlockingIOError not raised inside function.

R. David Murray added the comment: If I copy the second code, and add an import for fcntl, and run the resulting program twice from two different shells, I get a BlockingIOError. This is on linux. -- nosy: +r.david.murray ___ Python tracker

[issue27016] BlockingIOError not raised inside function.

Ned Deily added the comment: What platform are you running this on and can you give a more detailed procedure for reproducing the problem you see? -- nosy: +ned.deily ___ Python tracker ___

[issue27016] BlockingIOError not raised inside function.

padraic cunningham added the comment: When the following code snippets are run from two separate shells, the code inside the function does not raise any error on the second call while the second snippet successfully raises a BlockingIOError on the second run: # No error raised. def func():

[issue27016] BlockingIOError not raised inside function.

New submission from padraic cunningham: When the following code snippets are run from two separate shells, the code inside the function does not raise any error on the second call while the second snippet successfully raises a BlockingIOError on the second run: # No error raised. def func():