You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
IDLE 3.2.3 crashes saving a .py file to certain folders on Windows 7 #59201
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=Noneclosed_at=<Date2012-06-07.01:43:14.148>created_at=<Date2012-06-04.01:14:54.415>labels= ['expert-IDLE', 'OS-windows', 'type-crash']
title='IDLE 3.2.3 crashes saving a .py file to certain folders on Windows 7'updated_at=<Date2012-06-07.05:36:39.593>user='https://bugs.python.org/mcuomoprestonhsorg'
changed the title [-]Python 3.2.3 freezes when saving a .py program[/-][+]IDLE 3.2.3 crashes saving a .py file to certain folders on Windows 7[/+]on Jun 5, 2012
Maureen, I have saved and run a file from the Idle editor perhaps a thousand times over the years with multiple Python versions, including 3.2.3 (retried just now) on both Windows XP and Win7. (Note: on the General tab of the Preferences dialog, one can make saving automatic for named files.) Like many others, I have had no problems, so there is something peculiar about your system or installation. For us to be of any help, please provide the information Ned already requested.
Start "Python (command line)" from Start/3.2 menu.
Enter "from idlelib import idle" to start Idle.
Either open a new or existing file and make a change.
Try to save and tell us *exactly* the directory you are in and the filename you enter.
If Idle closes, does it just go 'poof' or is there a Windows error message box?
If there is a box, what does it say?
If there is a traceback, copy *all* of it and paste into a message here.
If you have to do anything different than the above to get an error, please be specific.
Terry, I believe Maureen was confirming that this appeared to be the same problem as documented in bpo-12988. So does anyone have any idea what apparently causes this behavior on some systems and not others?
bpo-12988 was about saving specifically to a Win7 Explorer window sidebar 'library', and the OP report with 3.2.1. This is different from a normal path as you know it. Maureen said she cannot save 'any file' except to desktop and that the behavior changed from 3.2.1 to 3.2.3.
Maureen, if you reply by email, PLEASE trim everything except your reply.
serwy commented on Jun 5, 2012
serwymannequin
Mannequin
More actions
bpo-12988 only has this problem on 64-bit Win 7. The 32-bit version works correctly. Maureen tried both versions and had the same problem.
mcuomoprestonhsorg commented on Jun 6, 2012
mcuomoprestonhsorgmannequin
MannequinAuthor
More actions
I have done some experimenting. I can save a file that I created on another
computer any place. It seems the only new files cannot be save in my usual
folder. I don't save in pyton32 folder. I have another folder to save in.
I was working on a project and by instinct did a save as with a new name.
It worked fine. So just to test things. I closed out of all python files,
opened idle, opened a new window, tried to save the new window and the
swirling circle came and then the message 'python has stopped working'.
Then everything closes.
I have done some experimenting. I can save a file that I created on another
computer any place. It seems the only new files cannot be save in my usual
folder. I don't save in pyton32 folder. I have another folder to save in.
>
> Roger Serwy <roger.serwy@gmail.com> added the comment:
>
> bpo-12988 only has this problem on 64-bit Win 7. The 32-bit version
works
> correctly. Maureen tried both versions and had the same problem.
>
> ----------
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue14996\>
> _______________________________________
>
Maureen, can you please start IDLE from a command prompt and report the error message?
Launch a command prompt, enter in "cd c:\python32" and then "python -m idlelib.idle". IDLE should appear. Proceed to save something that causes the crash. You should receive some feedback in the command prompt.
mcuomoprestonhsorg commented on Jun 7, 2012
mcuomoprestonhsorgmannequin
MannequinAuthor
More actions
I get a syntax error when I type this in. I attached a word doc with the
error screen
Maureen
Maureen, can you please start IDLE from a command prompt and report the
error message?
Launch a command prompt, enter in "cd c:\python32" and then "python -m
idlelib.idle". IDLE should appear. Proceed to save something that causes
the crash. You should receive some feedback in the command prompt.
You are already in a Python shell. Type in "import idlelib.idle" to launch IDLE.
mcuomoprestonhsorg commented on Jun 7, 2012
mcuomoprestonhsorgmannequin
MannequinAuthor
More actions
OK. I did that. The idle window opened. I opened a new window to create a
file; save the file in my usual directory and the same thing happened. The
swirling circle and the message that python.exe has stopped working.
Maureen
Maureen, as I explain on bpo-12988, I believe that this was a tcl/tk problem that was fixed by the recent release of version 8.5.11 (last March). The Windows installer for Python 3.3.0a4 release (a week ago) seems to have solved the problem for me. So give that a try.
Martin or anyone else: is the same tcl/tk upgrade going into future 3.2 and 2.7 releases?
loewis commented on Jun 7, 2012
loewismannequin
Mannequin
More actions
If it really fixes the bug, I can update the Tcl version. However, for that, I would need precise instructions on how to reproduce the bug.
Activity
[-]Python 3.2.3 freezes when saving a .py program[/-][+]IDLE 3.2.3 crashes saving a .py file to certain folders on Windows 7[/+]terryjreedy commentedon Jun 5, 2012
Maureen, I have saved and run a file from the Idle editor perhaps a thousand times over the years with multiple Python versions, including 3.2.3 (retried just now) on both Windows XP and Win7. (Note: on the General tab of the Preferences dialog, one can make saving automatic for named files.) Like many others, I have had no problems, so there is something peculiar about your system or installation. For us to be of any help, please provide the information Ned already requested.
If you have to do anything different than the above to get an error, please be specific.
ned-deily commentedon Jun 5, 2012
Terry, I believe Maureen was confirming that this appeared to be the same problem as documented in bpo-12988. So does anyone have any idea what apparently causes this behavior on some systems and not others?
terryjreedy commentedon Jun 5, 2012
bpo-12988 was about saving specifically to a Win7 Explorer window sidebar 'library', and the OP report with 3.2.1. This is different from a normal path as you know it. Maureen said she cannot save 'any file' except to desktop and that the behavior changed from 3.2.1 to 3.2.3.
Maureen, if you reply by email, PLEASE trim everything except your reply.
serwy commentedon Jun 5, 2012
bpo-12988 only has this problem on 64-bit Win 7. The 32-bit version works correctly. Maureen tried both versions and had the same problem.
mcuomoprestonhsorg commentedon Jun 6, 2012
I have done some experimenting. I can save a file that I created on another
computer any place. It seems the only new files cannot be save in my usual
folder. I don't save in pyton32 folder. I have another folder to save in.
Maybe this will help
Maureen
On Tue, Jun 5, 2012 at 10:00 AM, Roger Serwy <report@bugs.python.org> wrote:
mcuomoprestonhsorg commentedon Jun 6, 2012
I was working on a project and by instinct did a save as with a new name.
It worked fine. So just to test things. I closed out of all python files,
opened idle, opened a new window, tried to save the new window and the
swirling circle came and then the message 'python has stopped working'.
Then everything closes.
Maybe this will help
Maureen
On Tue, Jun 5, 2012 at 8:11 PM, Maureen Cuomo <report@bugs.python.org>wrote:
serwy commentedon Jun 6, 2012
Maureen, can you please start IDLE from a command prompt and report the error message?
Launch a command prompt, enter in "cd c:\python32" and then "python -m idlelib.idle". IDLE should appear. Proceed to save something that causes the crash. You should receive some feedback in the command prompt.
mcuomoprestonhsorg commentedon Jun 7, 2012
I get a syntax error when I type this in. I attached a word doc with the
error screen
Maureen
On Tue, Jun 5, 2012 at 11:04 PM, Roger Serwy <report@bugs.python.org> wrote:
serwy commentedon Jun 7, 2012
You are already in a Python shell. Type in "import idlelib.idle" to launch IDLE.
mcuomoprestonhsorg commentedon Jun 7, 2012
OK. I did that. The idle window opened. I opened a new window to create a
file; save the file in my usual directory and the same thing happened. The
swirling circle and the message that python.exe has stopped working.
Maureen
On Wed, Jun 6, 2012 at 8:38 PM, Roger Serwy <report@bugs.python.org> wrote:
serwy commentedon Jun 7, 2012
Did any messages appear in the Python shell?
mcuomoprestonhsorg commentedon Jun 7, 2012
No. the window becomes 'faded' it is not reponding
Maureen
On Wed, Jun 6, 2012 at 8:51 PM, Roger Serwy <report@bugs.python.org> wrote:
serwy commentedon Jun 7, 2012
How are you using the open dialog to navigate to your usual directory?
mcuomoprestonhsorg commentedon Jun 7, 2012
File , save as, libraries, documents - then I save the file there. No other
folder right now.
Maureen
On Wed, Jun 6, 2012 at 9:01 PM, Roger Serwy <report@bugs.python.org> wrote:
terryjreedy commentedon Jun 7, 2012
Ok, I agree now that this seems to be a duplicate of bpo-12988
I will make a note there that another user had the same problem.
mcuomoprestonhsorg commentedon Jun 7, 2012
So now what happens?
Maureen
On Wed, Jun 6, 2012 at 9:21 PM, Terry J. Reedy <report@bugs.python.org>wrote:
serwy commentedon Jun 7, 2012
Further discussion of this issue will be under bpo-12988. We're working on finding a solution.
serwy commentedon Jun 7, 2012
Sorry for the re-open. I submitted an old form.
terryjreedy commentedon Jun 7, 2012
Maureen, as I explain on bpo-12988, I believe that this was a tcl/tk problem that was fixed by the recent release of version 8.5.11 (last March). The Windows installer for Python 3.3.0a4 release (a week ago) seems to have solved the problem for me. So give that a try.
Martin or anyone else: is the same tcl/tk upgrade going into future 3.2 and 2.7 releases?
loewis commentedon Jun 7, 2012
If it really fixes the bug, I can update the Tcl version. However, for that, I would need precise instructions on how to reproduce the bug.
serwy commentedon Jun 7, 2012
Precise instructions can be found in msg144106 and msg161168 from bpo-12988.