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 ned.deily
Recipients mwei11, ned.deily
Date 2013-07-12.19:02:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1373655749.92.0.68405407677.issue18428@psf.upfronthosting.co.za>
In-reply-to
Content
If deleting .py files solved the problem, you probably had created a .py file with the same name as a Python standard library module.  If that file is in your Documents folder (if you are using /Applications/Python3.3/IDLE.app) or your current working directory (if you use /usr/local/bin/idle3.3), that directory is inserted first on Python's search path for modules and the files there will be found before the normal standard library version.  For example, if you create a dummy text file named socket.py in Documents and then double-click on IDLE.app, you should see the same message that the subprocess didn't make a connection because the dummy socket.py shadows the standard library socket module.  In any case, I'm glad that the problem is resolved for you.
History
Date User Action Args
2013-07-12 19:02:29ned.deilysetrecipients: + ned.deily, mwei11
2013-07-12 19:02:29ned.deilysetmessageid: <1373655749.92.0.68405407677.issue18428@psf.upfronthosting.co.za>
2013-07-12 19:02:29ned.deilylinkissue18428 messages
2013-07-12 19:02:29ned.deilycreate