-
Notifications
You must be signed in to change notification settings - Fork 105
-
Notifications
You must be signed in to change notification settings - Fork 105
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
Process spawn hangs forever (MacOS) #74
Comments
With
it hangs at the second call to loop.run |
This is not a bug, the loop will keep looping until no active handles are left, and process handles are always active until you call close() on them. This one works:
|
@saghul
|
I checked the code and indeed it's clear that this is handled differently. I'll report this to the libuv guys. Nevertheless, and as a rule of thumb when using pyuv, always close() handles where you are done with them. They are automatically closed if the Python object is garbage collected, but you never know when that will happen. Moreover, if you don't call close() you need to know the event loop internals to actually know when a handle is active or not, because an active handle will prevent loop.run() from returning (unless it's unref'd, but that was not this case). |
I reported this and it has already been fixed in libuv! joyent/libuv#718 I'll bump the libuv revision shortly and it will work the same on Windows and Unix. |
If I execute this simple script:
The loop.run hangs forever, it even can't be stopped with SIGINT (Ctrl+C). Happens on Python 2.7 and Python 3.3.
The text was updated successfully, but these errors were encountered: