-
Notifications
You must be signed in to change notification settings - Fork 605
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Builds fails if stdin is redirected to empty input #469
Comments
How can I reproduce this error? (without setting up an OpenSUSE build system). |
Introduced in #276 Reproducible with:
|
Paging @jeroenjanssens: do you recall the specific reason for this block of code? I think maybe it had something to do with using a piped file and a filesystem file in the same process, though that should also be possible using the |
Fixed in #510 without figuring out csvsql's logic. |
Don't error when reading from /dev/null, fixes #469
Hi,
While packaging csvkit for fedora and OpenSuse, we (I and @tigerfoot) found out that tests that relying on stdin fail with this message:
From what we figured out, the problem is that you add
sys.stdin
to the list of input files if the script is not run on a tty. But on the packages build system, stdin is redirected to something empty. This causes the build to fail.Below is the patch that allow us to solve this issue. Is it really needed to add
sys.stdin
to input files?Originaly reported on OpenSuse packaging. See: http://opensuse.14.x6.nabble.com/python3-test-a-strange-failure-only-during-build-td5052784.html.
The text was updated successfully, but these errors were encountered: