Skip to content
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

Jump to bottom

IDLE won't start in 2.6 final. A known fix was overlooked? #48292

Closed
rbtyod mannequin opened this issue Oct 4, 2008 · 7 comments
Closed

IDLE won't start in 2.6 final. A known fix was overlooked? #48292

rbtyod mannequin opened this issue Oct 4, 2008 · 7 comments
Labels
topic-IDLE type-crash A hard crash of the interpreter, possibly with a core dump

Comments

@rbtyod
Copy link
Mannequin

rbtyod mannequin commented Oct 4, 2008

BPO 4042
Nosy @loewis, @amauryfa

Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.

Show more details

GitHub fields:

assignee = None
closed_at = <Date 2008-10-05.19:15:09.198>
created_at = <Date 2008-10-04.22:07:52.862>
labels = ['expert-IDLE', 'type-crash']
title = "IDLE won't start in 2.6 final. A known fix was overlooked?"
updated_at = <Date 2008-10-05.19:15:09.197>
user = 'https://bugs.python.org/rbtyod'

bugs.python.org fields:

activity = <Date 2008-10-05.19:15:09.197>
actor = 'loewis'
assignee = 'none'
closed = True
closed_date = <Date 2008-10-05.19:15:09.198>
closer = 'loewis'
components = ['IDLE']
creation = <Date 2008-10-04.22:07:52.862>
creator = 'rbtyod'
dependencies = []
files = []
hgrepos = []
issue_num = 4042
keywords = []
message_count = 7.0
messages = ['74321', '74322', '74323', '74331', '74335', '74351', '74352']
nosy_count = 3.0
nosy_names = ['loewis', 'amaury.forgeotdarc', 'rbtyod']
pr_nums = []
priority = 'normal'
resolution = 'works for me'
stage = None
status = 'closed'
superseder = None
type = 'crash'
url = 'https://bugs.python.org/issue4042'
versions = ['Python 2.6']
@rbtyod
Copy link
Mannequin Author

rbtyod mannequin commented Oct 4, 2008

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

"[bpo-3943] 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
bpo-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

@rbtyod rbtyod mannequin added topic-IDLE type-crash A hard crash of the interpreter, possibly with a core dump labels Oct 4, 2008
@amauryfa
Copy link
Member

amauryfa commented Oct 4, 2008

IDLE 2.6 final works for me.
(I believe that bpo-3905 did not apply to 2.6)

Can you please open a command prompt, and start IDLE from there?
If you installed python in the default location, the command is:

C:\python26\python C:\python26\Lib\idlelib\idle

You should see interesting error messages there.

@amauryfa
Copy link
Member

amauryfa commented Oct 4, 2008

Sorry, copy/paste error. The correct command is of course:

C:\python26\python C:\python26\Lib\idlelib\idle.py

@rbtyod
Copy link
Mannequin Author

rbtyod mannequin commented Oct 4, 2008

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 bpo-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

@loewis
Copy link
Mannequin

loewis mannequin commented Oct 5, 2008

Amaury, when I tried to run IDLE from the command line as you suggested
I got:

C:\>C:\python26\Lib\idlelib\idle.py

This is not what Amaury suggested. He suggested that you put the path
to python.exe before the path of idle.py

@rbtyod
Copy link
Mannequin Author

rbtyod mannequin commented Oct 5, 2008

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

@loewis
Copy link
Mannequin

loewis mannequin commented Oct 5, 2008

Closing as "works for me", then.

@loewis loewis mannequin closed this as completed Oct 5, 2008
@ezio-melotti ezio-melotti transferred this issue from another repository Apr 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
topic-IDLE type-crash A hard crash of the interpreter, possibly with a core dump
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@amauryfa