Irit Katriel added the comment:
Closing again. In addition to what Eric said, both 2.7 and 3.6 are no longer
maintained so you will need to reproduce the issue on a current version (>=
3.8) for any of us to investigate it.
--
nosy: +iritkatriel
resolution: remind -> third party
Eric V. Smith added the comment:
No, I'm sorry that I don't. The example is too large for me (or probably any of
our volunteers) to look through and reason about. I think asking on a forum
like Stack Overflow is your best bet, but even there they will ask for a
simpler example. Or maybe try
Muralidhar BN added the comment:
Dear Eric Smith,
Do we have any analysis for this issue for information shared ?
Appreciate your quick reply.
PS: Making a simple socket connection instead of paramiko or pyssh ssh
connection gives similar error
Thank you
--
Muralidhar BN added the comment:
We have checked this issue by adapting another 3rd party SSH packages ( replace
paramiko with pyssh). Using this we have found same o/p results. Which means it
is not 3rd party SSH package ( paramiko or pyssh) issue.
Issue report in Paramiko github will be
Eric V. Smith added the comment:
This was reported a few hours ago at
https://github.com/paramiko/paramiko/issues/1856.
I'm closing this as a third party issue.
--
nosy: +eric.smith
resolution: -> third party
stage: -> resolved
status: open -> closed
New submission from Muralidhar BN :
Threads shutting down in Py 2.7 but not in Py 3.69 while making SSH connection
using Paramiko module
Executing code qa-test-execute.py in Py 2.7 (Ubuntu 14.04.6 LTS)
Command 1 :
sudo python ./qa-test-execute.py
Output 1 :
2021-05-24
