[Python-bugs-list] [ python-Bugs-790162 ] a bug in IDLE on Python 2.3 i think

SourceForge.net noreply at sourceforge.net
Fri Sep 5 17:51:13 EDT 2003


Bugs item #790162, was opened at 2003-08-17 13:18
Message generated for change (Comment added) made by kbk
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=790162&group_id=5470

Category: IDLE
Group: Python 2.3
Status: Open
>Resolution: Works For Me
>Priority: 3
Submitted By: Ricardo Nunes Cerqueira (caifas1800)
Assigned to: Kurt B. Kaiser (kbk)
Summary: a bug in IDLE on Python 2.3 i think

Initial Comment:
Hi, my name is Ricardo and i think there is a bug in

the new

release of Python 2.3. When i open a .py file with

IDLE(after

opening IDLE i open another .py file with it) the

second window

does not close after clicking the respective button,

only the first(when i click the first window of IDLE)

that has no code inserted, after trying to close the

group(2

windows) only the first (the first IDLE window with no code

inserted) closes leaving the other with code inserted open.

i'm using Python 2.3 on Windows XP under an Intel PIII

1000EB FC-PGA. What i described happens after i open

Python win then i open IDLE and then i open a .py file

with IDLE, and when i try to close the .py and i can't.

thanks

----------------------------------------------------------------------

>Comment By: Kurt B. Kaiser (kbk)
Date: 2003-09-05 18:51

Message:
Logged In: YES 
user_id=149084

Assuming that IDLE is configured to open a shell (the

default action), then opening a .py file and closing

that .py window works for me.



Assuming that IDLE is configured to open an edit window,

it comes up empty.  If you then open a .py, the empty

window is replaced with the whatever.py file and can be

closed.  Works for me.



Assuming you start python, and then in the interactive

window "import idle", the windows open and close correctly,

as far as I can tell.  I'm using XP / SP 1 / P4 2.4



Please provide (in short sentences) a precise recipe

to reproduce your problem.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=790162&group_id=5470



More information about the Python-bugs-list mailing list