[issue3943] IDLE won't start in 3.0rc1 "Subprocess didn't make connection...."
New submission from Robert Yodlowski <[EMAIL PROTECTED]>: I installed 3.0rc1 on a Win XP 2.4Gzh system with all current updates with no problems. Cmd line Python and docs work fine. Tried to start IDLE but got error message: "IDLE's subprocess didn't make connection. Either IDLE can't start subprocess or personal firewall is blocking." I turned off my firewall but got the same error message. IDLE works fine in Python 2.5 and 2.6 on this same machine. Tried change to idlelib\run.py suggested in bug report #3905 but it had no effect. ...Bob -- components: IDLE messages: 73613 nosy: rbtyod severity: normal status: open title: IDLE won't start in 3.0rc1 "Subprocess didn't make connection" type: crash versions: Python 3.0 ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3943> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3943] IDLE won't start in 3.0rc1 "Subprocess didn't make connection...."
Robert Yodlowski <[EMAIL PROTECTED]> added the comment: Amaury, I did as you suggested - running idle.py directly both from a command line and by clicking on it and the results were the same. Each time, I got the same error message window as before. In addition, several seconds before the error window came up I got the following traceback in the command window: C:\Python30>python Lib/idlelib/idle.py Traceback (most recent call last): File "", line 1, in File "C:\Python30\lib\idlelib\run.py", line 76, in main sockthread.set_daemon(True) AttributeError: 'Thread' object has no attribute 'set_daemon' I hope this helps. ...Bob ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3943> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue3943] IDLE won't start in 3.0rc1 "Subprocess didn't make connection...."
Robert Yodlowski <[EMAIL PROTECTED]> added the comment: Amaury, my stupid! I must have forgotten to delete the run.pyc file before trying out the modified run.py as suggested in #3905 . It all works now and IDLE starts up just fine. Sorry and, thanks for the help. ...Bob ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue3943> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4042] IDLE won't start in 2.6 final. A known fix was overlooked?
New submission from Robert Yodlowski <[EMAIL PROTECTED]>: I just installed the 2.6 final release on my fully updated Win XP system. When I tried to run IDLE I got the same... "IDLE's subprocess didn't make connection. Either IDLE can't start subprocess or personal firewall is blocking." ...fatal error message I got when I installed the last release candidate version on Sept 22, 2008. I put in a bug report at that time "[issue3943] IDLE won't start in 3.0rc1 "Subprocess didn't make connection"" but it was closed since the fix to LIB/idlelib/run.py (on line 76) in #3905 message 73496 by Georg Brandl fixes this problem. I believe that this known fix was overlooked when 2.6 final was released this week. ...Bob -- components: IDLE messages: 74321 nosy: rbtyod severity: normal status: open title: IDLE won't start in 2.6 final. A known fix was overlooked? type: crash versions: Python 2.6 ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4042> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4042] IDLE won't start in 2.6 final. A known fix was overlooked?
Robert Yodlowski <[EMAIL PROTECTED]> added the comment: Amaury, when I tried to run IDLE from the command line as you suggested I got: C:\>C:\python26\Lib\idlelib\idle.py IDLE Subprocess: socket error: An attempt was made to access a socket in a way forbidden by its access permissions, retrying IDLE Subprocess: socket error: An attempt was made to access a socket in a way forbidden by its access permissions, retrying IDLE Subprocess: socket error: An attempt was made to access a socket in a way forbidden by its access permissions, retrying IDLE Subprocess: Connection to IDLE GUI failed, exiting. ...followed by 2 error windows: Socket Error:An attempt was made to access a socket in a way forbidden by its access permissions and... IDLE's subprocess didn't make connection. Either IDLE can't start a subprocess or personal firewall software is blocking the connection ...BUT when I try to run IDLE from the "all programs" menu it runs just fine - which it did NOT when I created today's bug report. To try to reproduce the original behavior, I first put back the unfixed version of run.py and IDLE STILL RAN FINE from the program menu I was VERY confused at this point and I completely uninstalled Python2.6 and reinstalled it from the same .msi installer I used before. After I reinstalled 2.6, IDLE again ran fine from the programs menu WITHOUT making the fix in run.py but NOT from the command line - producing the same error messages as at the top of this entry. Right now I am so confused I don't know what to do. I cannot reproduce the original problem I reported in this bug report and IDLE runs fine from the menu but not from the command line. It know that IDLE would not run from the programs menu until I changed run.py but once I did that, removing the fix seems to make no difference. (I've been careful to remove the run.pyc file each time.) I believe that the behavior I saw today with 2.6 was the same as I saw on Sept 22 with 3.0 when I submitted #3943 - and with the same confusing property where the fix is needed to make IDLE run but removing it makes no difference. I hope this makes sense to you. It doesn't to me. ...Bob ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4042> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue4042] IDLE won't start in 2.6 final. A known fix was overlooked?
Robert Yodlowski <[EMAIL PROTECTED]> added the comment: Problem Solved. It was my firewall. When I ran IDLE from the command line (the RIGHT way this time), in addition to the error messages and popup windows that I got before, I also got a popup window from my firewall asking if I was willing to grant Python access permission. I granted permission and, when I tried starting IDLE again, everything worked just fine. Thank you, Amaury and Martin, for your help and your patience with me. ...Bob ___ Python tracker <[EMAIL PROTECTED]> <http://bugs.python.org/issue4042> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue5140] Some Built-in Functions entries in Library Manual are missing Permalinks
New submission from Robert Yodlowski : In http://docs.python.org/3.0/library/functions.html these function entries seem to be missing Permalinks. dict() frozenset() memoryview() set() Hope this helps. The Permalinks are a great idea. I hope you add lots more. ...Bob -- assignee: georg.brandl components: Documentation messages: 81027 nosy: georg.brandl, rbtyod severity: normal status: open title: Some Built-in Functions entries in Library Manual are missing Permalinks versions: Python 3.0 ___ Python tracker <http://bugs.python.org/issue5140> ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
