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

unable to launch IDLE on windows XP #46917

Closed
Leo mannequin opened this issue Apr 21, 2008 · 6 comments
Closed

unable to launch IDLE on windows XP #46917

Leo mannequin opened this issue Apr 21, 2008 · 6 comments
Assignees
@amauryfa
Labels
topic-IDLE type-crash A hard crash of the interpreter, possibly with a core dump

Comments

@Leo
Copy link
Mannequin

Leo mannequin commented Apr 21, 2008

BPO 2665
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 = 'https://github.com/amauryfa'
closed_at = <Date 2008-04-21.22:43:28.425>
created_at = <Date 2008-04-21.08:38:12.576>
labels = ['expert-IDLE', 'type-crash']
title = 'unable to launch IDLE on windows XP'
updated_at = <Date 2008-04-21.22:43:28.423>
user = 'https://bugs.python.org/Leo'

bugs.python.org fields:

activity = <Date 2008-04-21.22:43:28.423>
actor = 'amaury.forgeotdarc'
assignee = 'amaury.forgeotdarc'
closed = True
closed_date = <Date 2008-04-21.22:43:28.425>
closer = 'amaury.forgeotdarc'
components = ['IDLE']
creation = <Date 2008-04-21.08:38:12.576>
creator = 'Leo'
dependencies = []
files = []
hgrepos = []
issue_num = 2665
keywords = []
message_count = 6.0
messages = ['65658', '65659', '65660', '65661', '65662', '65666']
nosy_count = 2.0
nosy_names = ['amaury.forgeotdarc', 'Leo']
pr_nums = []
priority = 'normal'
resolution = 'fixed'
stage = None
status = 'closed'
superseder = None
type = 'crash'
url = 'https://bugs.python.org/issue2665'
versions = ['Python 2.5']
@Leo
Copy link
Mannequin Author

Leo mannequin commented Apr 21, 2008

I recently upgraded from python 2.3 to 2.5. But idle doesn't launch
anymore, either with right-clicking a .py program an doing "edit with
IDLE" or with launching the idle.py file itself.
When I launch idle with the command line, it gives the following error
several times:

Warning : configHandler.py - IdleConf.GetThemeDict-
problem retrieving theme element 'buitlin-foreground'
from theme 'vert theme'
returning default value: 'bpo-000000'

Warning : configHandler.py - IdleConf.GetThemeDict-
problem retrieving theme element 'buitlin-background'
from theme 'vert theme'
returning default value: '#ffffff'

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

"buitlin"? Is is a typo while copying the error message?

The warnings are normal, these theme elements were added later. They
will disappear when you save the theme again.

Now, idle starts another process to interpret the commands, and use
sockets to communicate between them. You may have a firewall problem.

Can you try to run idle.py with the "-n" option? This does not create a
subprocess, all commands are run in the main process.

@Leo
Copy link
Mannequin Author

Leo mannequin commented Apr 21, 2008

it's not "buitlin" but "builtin" of course.

idle launches when I use the command line, with or without "-n", but I'm
still unable to lauch it normally (by the right click or by the windows
menu ("Démarrer/Programmes/Python25/idle")).
Before, I used python 2.3 and it worked well. I uninstalled and
installed again python 2.5 several times but I still got the same
problem.. it isn't practical at all to lauch idle by the command line!
So I hope you'll have an idea to solve my problem...

@amauryfa
Copy link
Member

I reproduced the problem.

  • "python.exe idle.py" works (with many warnings)
  • "pythonw.exe idle.py" fails

pythonw.exe is a Windows (i.e. not a console) application, so sys.stderr
points to an invalid file descriptor; printing lot of warnings raises an
exception when the file tries to flush()...

As an immediate workaround, you may delete everything in the directory named
c:/Documents and Settings/%USERNAME%/.idlerc
or if you feel it, add the missing entries in the file config-highlight.cfg.

I'll try to correct this problem for python2.5: replace
sys.stderr.write(warning)
with
try:
sys.stderr.write(warning)
except IOError:
pass

@Leo
Copy link
Mannequin Author

Leo mannequin commented Apr 21, 2008

ok, deleting the contents of .idlerc seems to work fine.
Thank you!

@amauryfa amauryfa self-assigned this Apr 21, 2008
@amauryfa
Copy link
Member

Committed r62448 & r62449.
Thanks for the report!

@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

@amauryfa amauryfa

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