[issue33384] Build does not work with closed stdin on NetBSD

STINNER Victor added the comment: > I can confirm that I can no longer reproduce this problem with Python 3.7.5 on NetBSD Great! -- ___ Python tracker ___ ___

[issue33384] Build does not work with closed stdin on NetBSD

Leonardo Taccari added the comment: Hello Victor, I can confirm that I can no longer reproduce this problem with Python 3.7.5 on NetBSD and according a double-check to Python/pylifecycle.c:is_valid_fd() now fstat() is always used on NetBSD. Thanks for the update and for looking at it! ---

[issue33384] Build does not work with closed stdin on NetBSD

STINNER Victor added the comment: I'm quite that this issue has been fixed by bpo-30225 which is part Python 3.7.4, Python 3.8.0 and newer. I mark the issue as duplicate of bpo-30225. Please reopen the bug if these versions still fail on NetBSD. commit 1c4670ea0cc3d208121af11b9b973e6bb268e5

[issue33384] Build does not work with closed stdin

Change by Leonardo Taccari : Added file: https://bugs.python.org/file47605/is_valid_fd.c ___ Python tracker ___ ___ Python-bugs-list mailing

[issue33384] Build does not work with closed stdin

Leonardo Taccari added the comment: After testing is_valid_fd() (from Python/pylifecycle.c) separately (an `is_valid_fd.c' file will be attached to ease reproduction) I think that also NetBSD is affected by bpo-30225. Using dup(2) (at is currently done in NetBSD): % cc -o ivf is_valid_fd.c

[issue33384] Build does not work with closed stdin

Leonardo Taccari added the comment: And here the backtrace of the corresponding core (this is on NetBSD/amd64 8.99.15 with lang/python36 package of today pkgsrc-current): % gdb -core python3.6.core `which python3.6` Reading symbols from /usr/pkg/bin/python3.6...done. [New process 1]

[issue33384] Build does not work with closed stdin

Leonardo Taccari added the comment: A simpler way to reproduce that (probably this problem is not limited to building but to sys module): (sleep 10; python3.6 -c 'import sys' >/tmp/log 2>&1) & exit And in `/tmp/log': Fatal Python error: Py_Initialize: can't initialize sys standard str

[issue33384] Build does not work with closed stdin

Martin Husemann added the comment: You need to exit the parent shell, to get the original stdin revoke(2)'d. That is: the Ctrl-D in the original descritpion is not line noise. Sorry, should have been more explicit (or used "exit" or something instead) -- __

[issue33384] Build does not work with closed stdin

Xavier de Gaye added the comment: I cannot reproduce the problem with Python 3.6.5, building pyephem and with the command: ( sleep 15; python setup.py build ) >foo.log 2>&1 -- nosy: +xdegaye ___ Python tracker

[issue33384] Build does not work with closed stdin

Change by Thomas Klausner : -- nosy: +wiz ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.

[issue33384] Build does not work with closed stdin

New submission from Martin Husemann : When building python extensions in the background w/o stdin (and stderr and stdout redirected to a log file), the invocation of setup.py fails. Normal build in a shell: Example from pyexpat: > /usr/pkg/bin/python3.6 setup.py build running build running b