Navigation Menu

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 subprocess error #46960

Closed
Kris mannequin opened this issue Apr 28, 2008 · 5 comments
Closed

IDLE subprocess error #46960

Kris mannequin opened this issue Apr 28, 2008 · 5 comments
Labels
topic-IDLE type-bug An unexpected behavior, bug, or error

Comments

@Kris
Copy link
Mannequin

Kris mannequin commented Apr 28, 2008

BPO 2708
Nosy @terryjreedy, @kbkaiser

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 2010-12-31.02:11:46.046>
created_at = <Date 2008-04-28.14:10:39.867>
labels = ['expert-IDLE', 'type-bug']
title = 'IDLE subprocess error'
updated_at = <Date 2010-12-31.02:11:46.044>
user = 'https://bugs.python.org/Kris'

bugs.python.org fields:

activity = <Date 2010-12-31.02:11:46.044>
actor = 'terry.reedy'
assignee = 'none'
closed = True
closed_date = <Date 2010-12-31.02:11:46.046>
closer = 'terry.reedy'
components = ['IDLE']
creation = <Date 2008-04-28.14:10:39.867>
creator = 'Kris'
dependencies = []
files = []
hgrepos = []
issue_num = 2708
keywords = []
message_count = 5.0
messages = ['65918', '66251', '66260', '87579', '124948']
nosy_count = 5.0
nosy_names = ['terry.reedy', 'kbk', 'gpolo', 'Kris', 'ChrisAltona']
pr_nums = []
priority = 'normal'
resolution = 'out of date'
stage = 'test needed'
status = 'closed'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue2708'
versions = ['Python 2.6', 'Python 3.0']
@Kris
Copy link
Mannequin Author

Kris mannequin commented Apr 28, 2008

Hi all.
I'w been looking for an answer to this.
If I use IDLE for som "just fore fun" programming and then exit, I have
to "kill" IDLE, dispite theres nothin "running" persay, then when i
start IDLE again I get too error messages popping up:

1: Socket Error: Connection refused
2: IDLE's subprocess didn't make connection. Either IDLE can't start a
subprocess or personal firewall is blocking the connection.

The code written in IDLE that triggers the problem can be something 
simple like:
>>> a = 'hello world'
>>> print a

I have to reboot to get past the error.
I'm only getting the error when running vista and xp theres no problom
in any of the other systems i'v tried (mainly linux)
I should mention that the error dosn't come every time I "kill" IDLE, I
would say about every 3rd run, or there about.
I'v tried removeing/killing windows owen firewall and then running IDLE
but with the same result.
Like I said, i been look around fore a "fix" fore this but havent found
any...
If I have made a "double post" please let me know and remove this
post....

@Kris Kris mannequin added type-crash A hard crash of the interpreter, possibly with a core dump topic-IDLE labels Apr 28, 2008
@kbkaiser
Copy link
Contributor

kbkaiser commented May 4, 2008

  1. Which version of Python / IDLE are you running?
  2. Why do you "have to kill" IDLE instead of doing a normal quit?

@Kris
Copy link
Mannequin Author

Kris mannequin commented May 5, 2008

Python 2.5.2 IDLE 1.2.2
It dosnt matter how i try to "end" IDLE: red cross, close(alt+F4), exit
(Ctrl+Q) or writing exit(), it will ask me to kill the program.
I dont think it's IDLE im "killing" but the program im writing.

@devdanzin devdanzin mannequin added type-bug An unexpected behavior, bug, or error and removed type-crash A hard crash of the interpreter, possibly with a core dump labels Apr 26, 2009
@ChrisAltona
Copy link
Mannequin

ChrisAltona mannequin commented May 11, 2009

I found that if I go into the Windows Task Manager and end (somtimes
both of) the Python processes, the program will run properly the next
time I open it.
Hope this helps.

@terryjreedy
Copy link
Member

3.0 is closed to fixed and 2.6 is security fix only.
This is otherwise a duplicate of similar issues.

@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-bug An unexpected behavior, bug, or error
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@kbkaiser @terryjreedy