This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author terry.reedy
Recipients kbk, lac, markroseman, roger.serwy, terry.reedy
Date 2016-01-18.05:14:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
I have seen another report that is likely due to masking.  I don't know why this has suddenly become seemingly much more common, but I have made fixing the problem a priority.  See new issue #26143.

I would like to narrow this issue to the user process, and broaden it to reporting all currently plausible causes of non-connection.  I revised the title to say this.

I am looking  at to see what causes people have found or think they have found.

1. Antivirus/firewall (4 people, linux iptables, Windows firewall, antivisus , so not a myth ;-)
2. Shadow files, as described above, and in the python directory (about as common, tkinter,py,
3. Registry problem (some people can fix, but most should re-install after complete removal).
4. Zombie pythonw process (kill with Windows Task manager).
5. Permissions (run as admin, though should not be needed with proper install)
?. Multiple installed versions clash due to misconfiguration?
?. example program that reads and writes (test)
6. Running after stopping run with ^C (temporary, I believe Restart Shell will fix)  Call this a timing issue.
<<Note: I have experienced temporary connection failures myself, but have not written what I did>>
7. Modem rebot (rather obsolete answer for most of us).

There are plenty of miscellaneous possibilities to add even if masking, the most common reason, is fixed.
Date User Action Args
2016-01-18 05:14:05terry.reedysetrecipients: + terry.reedy, kbk, roger.serwy, markroseman, lac
2016-01-18 05:14:05terry.reedysetmessageid: <>
2016-01-18 05:14:05terry.reedylinkissue25514 messages
2016-01-18 05:14:03terry.reedycreate