-
Notifications
You must be signed in to change notification settings - Fork 184
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
Script won't exit because paramiko thread is still running #72
Comments
Thanks for reporting, will have a look shortly. |
Thanks for looking into it! I just installed with pip. It got sshtunnel-0.1.0, paramiko-2.0.2, and pyasn1-0.1.9. |
Hi, could you please install from source ( |
I tried installing the v0.1.0 branch and it is exiting correctly now. Thank you! |
I am using 0.1.3 and if I try using sshtunnel from an interactive prompt, then exiting with CTRL-D, my session never closes. But if I explicitly call |
Any fix for this? |
Experiencing the same problem |
I'm experiencing this too, any fix? |
1 similar comment
I'm experiencing this too, any fix? |
I was able to close the the connection after setting daemon_forward_servers = True
|
@stobra Thank you! When I set things up exactly this way they worked. Even a small deviation resulted in the hanging problem. |
@stobra Thank you! I've solved the hanging problem with your suggestion |
@dem82, I'm glad to hear it was helpful. Best wishes |
@stobra you sir are a legend! |
Worked for me too, thank you so much! |
Because someone still finds this issue through a search I'll write it here:
Please, don't leave a comment here. If you have any issues and still have any issues feel free to open a new one! |
The following script works and "FINISH" is printed, but it never exits to the shell:
Python is waiting on threads to finish, but they never do. After running this script in iPython I can see the threads:
If I uncomment the last line which explicitly closes the paramiko.Transport threads, the script exits correctly. It seems like I'm missing something, but even so this default behavior is confusing.
The text was updated successfully, but these errors were encountered: