Stephan Bellegy stephan.bell...@gmail.com added the comment:
Reproduced today with Python 2.6.6 and 2.7 on Win7 32 bits.
Deleting .idlerc directory made it.
Doesn't look like fixed guys ! ;-)
--
nosy: +Stephan.Bellegy
versions: +Python 2.6 -Python 2.5, Python 3.1
Martin v. Löwis mar...@v.loewis.de added the comment:
Please submit this as a new bug issue, preferably with precise instructions on
how to reproduce it. Can you provide some clue how the file became hidden in
the first place?
--
___
Python tracker
Stephan Bellegy stephan.bell...@gmail.com added the comment:
New bug reported here
http://bugs.python.org/issue9925
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1743
___
Kurt B. Kaiser added the comment:
backported 2.5.2c1
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1743
__
___
Python-bugs-list mailing list
Unsubscribe:
Kurt B. Kaiser added the comment:
Thanks for the fix. r60225.
--
resolution: - fixed
status: open - closed
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1743
__
___
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:
Martin v. Löwis added the comment:
As a follow-up, it appears that Windows didn't allow truncating hidden
or system files since Windows 2000. If you change the flags on .idlerc
to hidden in (say) W2k3, IDLE will also fail to start - so it's not a
Vista issue.
The question is why the folder
Rich added the comment:
Aha! There is no difference in Permissions, but the working recent-
files file isn't hidden but the one generated originally by IDLE was.
If I make the one I made hidden then IDLE stops working again.
The .idlerc folder has been hidden all along though - that doesn't
Martin v. Löwis added the comment:
We should clearly separate issues. Changing the organization of files is
entirely independent from fixing the bug reported here, and the issues
must not at all be mixed.
I'm puzzled as to why making the file hidden should have any effect, but
at least that's
Kurt B. Kaiser added the comment:
1. Could you look at the properties of the .idlerc\recent-files.lst that you
saved and compare them to the new file which worked? In particular, what
about access permissions?
2. I agree that IDLE should have a better error response if opening a user
config
Rich added the comment:
I can't get it to do it again. Unless someone else is still
experiencing the problem, perhaps it was fixed (deliberately or
otherwise) by this month's Vista hotfixes that came down automatically
a couple of days ago.
Thanks for your help everyone.
Rich added the comment:
I've been away for a couple of days, but can replicate everything
Joakim has reported in my abscence. Deleting/renaming recent-files.lst
allows me to launch IDLE (from cmd or Start Menu).
Oddly though, if I close IDLE, copy/paste the contents of the old
recent-files
Martin v. Löwis added the comment:
Can anybody provide a complete, reproducible procedure for that bug
(rather than reproducible procedures to work around it)? Such a
procedure might have to start with installing Python.
__
Tracker [EMAIL PROTECTED]
Joakim added the comment:
I have the exact same problem also running 32-bit vista.
Idle worked the first time I started it but after that it doesn't start.
I did run the command and got this error.
C:\Users\JoakimC:\Python25\python.exe C:\Python25\Lib\idle.py
C:\Python25\python.exe: can't open
Christian Heimes added the comment:
Can you access the file C:\\Users\\Joakim\\.idlerc\\recent-files.lst
with the explorer? Do the directory and the file exist?
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1743
__
Joakim added the comment:
I can access the file. I renamed the file and tried the command again.
Then I started IDLE and got a window. A new recent-files.lst was
created. So I guess I solved the problem temporarily.
__
Tracker [EMAIL PROTECTED]
Christian Heimes added the comment:
It smells like a Vista issue.
But IDLE shouldn't crash w/o a notice if the recent list can't be opened.
--
assignee: - kbk
nosy: +kbk
priority: - low
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1743
New submission from Rich:
Launching IDLE from the start menu has no effect, no windows open.
Command line Python still works. Reinstalling Python does not fix the
problem.
I haven't changed my system configuration since everything was working.
Any ideas for things to check to fix this on my
Christian Heimes added the comment:
What's your OS and how did you install Python on your machine?
--
nosy: +tiran
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1743
__
Rich added the comment:
I'm on 32-bit Windows Vista, and I installed with the Python 2.5 msi.
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue1743
__
___
Python-bugs-list mailing
Martin v. Löwis added the comment:
Please open IDLE from the command line:
1. start cmd.exe
2. run path to python.exe path to python/Lib/idle/idle.py
That should give you an error, please report it.
--
nosy: +loewis
__
Tracker [EMAIL PROTECTED]
21 matches
Mail list logo