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.

Sign up for GitHub

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 3.0rc1 "Subprocess didn't make connection...." #48193

Closed
rbtyod mannequin opened this issue Sep 23, 2008 · 7 comments
Closed

IDLE won't start in 3.0rc1 "Subprocess didn't make connection...." #48193

rbtyod mannequin opened this issue Sep 23, 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 Sep 23, 2008

BPO 3943
Nosy @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-09-25.19:20:28.604>
created_at = <Date 2008-09-23.02:55:46.973>
labels = ['expert-IDLE', 'invalid', 'type-crash']
title = 'IDLE won\'t start in 3.0rc1 "Subprocess didn\'t make connection...."'
updated_at = <Date 2008-09-25.19:20:28.603>
user = 'https://bugs.python.org/rbtyod'

bugs.python.org fields:

activity = <Date 2008-09-25.19:20:28.603>
actor = 'amaury.forgeotdarc'
assignee = 'none'
closed = True
closed_date = <Date 2008-09-25.19:20:28.604>
closer = 'amaury.forgeotdarc'
components = ['IDLE']
creation = <Date 2008-09-23.02:55:46.973>
creator = 'rbtyod'
dependencies = []
files = []
hgrepos = []
issue_num = 3943
keywords = []
message_count = 7.0
messages = ['73613', '73620', '73622', '73623', '73751', '73771', '73806']
nosy_count = 3.0
nosy_names = ['amaury.forgeotdarc', 'jmfauth', 'rbtyod']
pr_nums = []
priority = 'normal'
resolution = 'not a bug'
stage = None
status = 'closed'
superseder = None
type = 'crash'
url = 'https://bugs.python.org/issue3943'
versions = ['Python 3.0']
@rbtyod
Copy link
Mannequin Author

rbtyod mannequin commented Sep 23, 2008

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 bpo-3905 but it had no effect.

...Bob

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

It is probably already corrected in svn.

Can you please try from a command prompt:

cd <path_to_python3.0rc1>
python Lib/idlelib/idle.py

Does this display some error message?

@jmfauth
Copy link
Mannequin

jmfauth mannequin commented Sep 23, 2008

I think the problem is fixed.
See bpo-3905.

@amauryfa
Copy link
Member

But bpo-3905 is not yet fixed, furthermore the OP already tried the
correction suggested there.

@rbtyod
Copy link
Mannequin Author

rbtyod mannequin commented Sep 24, 2008

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 "<string>", line 1, in <module>
  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

@amauryfa
Copy link
Member

Did you *really* follow the suggested change proposed in bpo-3905 ?
http://bugs.python.org/msg73496

@rbtyod
Copy link
Mannequin Author

rbtyod mannequin commented Sep 25, 2008

Amaury, my stupid! I must have forgotten to delete the run.pyc file
before trying out the modified run.py as suggested in bpo-3905 . It all
works now and IDLE starts up just fine.

Sorry and, thanks for the help.

...Bob

@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