[issue1862] Error on Save As in IDLE (Vista 32-bit)

2008-01-23 Thread Kurt B. Kaiser
Kurt B. Kaiser added the comment: r60225. Dup of Issue 1743. -- resolution: - fixed status: open - closed __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1862 __ ___

[issue1862] Error on Save As in IDLE (Vista 32-bit)

2008-01-22 Thread Martin v. Löwis
Martin v. Löwis added the comment: I've studied the problem with Process Monitor. If a file is hidden, open(f, w) fails, whereas os.open(f, os.W_OK|os.O_CREAT) succeeds. In the succeeding call, process monitor reports Desired Access: Generic Read/Write Disposition:OpenIf Options:

[issue1862] Error on Save As in IDLE (Vista 32-bit)

2008-01-19 Thread Kurt B. Kaiser
Kurt B. Kaiser added the comment: IDLE creates the .idlerc folder if needed. It seems it should be marked as not hidden. Does anyone know how to do that? __ Tracker [EMAIL PROTECTED] http://bugs.python.org/issue1862 __

[issue1862] Error on Save As in IDLE (Vista 32-bit)

2008-01-17 Thread Rich
New submission from Rich: Issue 1743 might be related to this. Using Save As... in IDLE does work, but if breakpoints.lst is hidden (which it is when Python generates it) it also generates this error in the Shell: Exception in Tkinter callback Traceback (most recent call last): File

[issue1862] Error on Save As in IDLE (Vista 32-bit)

2008-01-17 Thread Christian Heimes
Christian Heimes added the comment: It's a duplicate of an already known problem. It seems that files on Vista inherit the flags of their parent folder. Can you test it on your box and see under which circumstances a file has the hidden flag set and how it affects read and write attempts on