[issue3881] IDLE won't start in custom directory.

2009-01-23 Thread Zlm
Zlm zemari...@gmail.com added the comment: I got my problem fixed in 4 days! Thank you for all your help, Martin! ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3881

[issue3881] IDLE won't start in custom directory.

2009-01-19 Thread Zlm
Zlm zemari...@gmail.com added the comment: I reinstalled Python to C:\Program Files\Python\ (I wrote this path in the installer) and IDLE works fine. I can access the Python folder by going to C:\Programas\Python. Then, I unninstalled and installed again to C:\Programas\Python. IDLE doesn't

[issue3881] IDLE won't start in custom directory.

2009-01-18 Thread Zlm
Zlm zemari...@gmail.com added the comment: Programas is the portuguese translation to Program Files. I have just installed it to C:\Test\Python and IDLE is working! The problem should be related to the Vista symbolic links. ___ Python tracker rep

[issue3881] IDLE won't start in custom directory.

2009-01-17 Thread Zlm
Zlm zemari...@gmail.com added the comment: Hi. I have the same problem, but i'm running Pyhton 2.6.1. I'm using Windows Vista 32bit SP1. I installed Python to C:\Program Files\Python\2.6\ and when I try to run idle from the start menu, it doesn't work. When I try to run it from the command

[issue3881] IDLE won't start in custom directory.

2009-01-17 Thread Zlm
Zlm zemari...@gmail.com added the comment: Yes, I did. ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue3881 ___ ___ Python-bugs-list mailing list Unsubscribe

[issue3881] IDLE won't start in custom directory.

2009-01-17 Thread Zlm
Zlm zemari...@gmail.com added the comment: So do you have a file C:\Programas\Python\2.6\tcl\tcl8.5\init.tcl ? Yes, I have. Could this problem be related to paths with slashes and backslashes? In the error log, the first path (the right one) has backslashes, but the others have slashes

[issue3881] IDLE won't start in custom directory.

2009-01-17 Thread Zlm
Zlm zemari...@gmail.com added the comment: Can you run the Sysinternals filemon to find out what files it is accessing? I tried Sysinternals ProcessMonitor (equivalent of filemon to Windows Vista), but the simple act of trying to open IDLE produces thousands of entries to the log window. I