-
Notifications
You must be signed in to change notification settings - Fork 478
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
pexpect 3.3 runs failed when use multiprocessing #86
Labels
Comments
Ahh, I guess stdin is closed, as seen in https://docs.python.org/2/library/multiprocessing.html#all-platforms under section. I made this change, I'll revert it -- thanks. |
I count the same problem with celery :( |
jquast
added a commit
that referenced
this issue
Aug 24, 2014
Fallback to using stdout, and, when both stdin and stdout are *both* closed, catch ValueError and use the same constants as when the attached process is not a terminal.
Closed by #109. |
timstaley
added a commit
to timstaley/drive-casa
that referenced
this issue
Apr 15, 2015
timstaley
added a commit
to timstaley/autocrunch-ami
that referenced
this issue
Apr 15, 2015
pexpect/pexpect#86 Also improved the test-script.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I use pexpect (version 3.3) and multiprocessing in python (version 2.6) code like below:
but runs failed, with this traceback:
however pexpect 3.3 runs well in a none multiprocessing environment
And I test it on pexpect 2.4 (also with python 2.6), it runs well too.
The text was updated successfully, but these errors were encountered: