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

Gabriel Genellina added the comment: This patch had unintended consequences; see #6906 -- ___ Python tracker ___ ___ Python-bugs-list

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

Changes by Sridhar Ratnakumar : -- nosy: +srid ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pytho

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

Martin v. Löwis added the comment: Committed as r68893, r68894, r68898, r68901. -- resolution: -> fixed status: open -> closed ___ Python tracker ___ ___

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

Zlm added the comment: I got my problem fixed in 4 days! Thank you for all your help, Martin! ___ Python tracker ___ ___ Python-bugs-list maili

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

Jacob added the comment: Fantastic. I started this post in October, and now we finaly found a solution. Thank you Martin. Will this patch be included in future versions of python? Best regards, Jacob. ___ Python tracker ___

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

Changes by Martin v. Löwis : -- versions: +Python 2.6, Python 2.7, Python 3.0, Python 3.1 -Python 2.5 ___ Python tracker ___ ___ Python

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

Martin v. Löwis added the comment: Here is a patch that should fix the problem. It uses Vista's GetFinalPathNameByHandleW to expand symbolic links before passing the path to Tcl. -- keywords: +patch Added file: http://bugs.python.org/file12832/symlink.diff _

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

Martin v. Löwis added the comment: > Installing to C:\Program Files\Python\ worked. > Now we just have to find out WHY it doesn't work with the > C:\[Programmer/Programmas]\ to C:\Program Files\ link. With process monitor, I made partial progress (after installing the German Vista version). It

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

Jacob added the comment: Installing to C:\Program Files\Python\ worked. Now we just have to find out WHY it doesn't work with the C:\[Programmer/Programmas]\ to C:\Program Files\ link. ___ Python tracker ___

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

Zlm 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 work. I can still

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

Daniel Diniz added the comment: Maybe it's "install into a symbolic link pointing to a path with spaces in it, and idle fails"? -- nosy: +ajaksu2 ___ Python tracker ___ _

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

Martin v. Löwis added the comment: > The problem should be related to the Vista symbolic links. Unfortunately, it isn't as simple as "install into a symbolic link, and it fails". I created c:\temp -> c:\tmp, and installed into c:\temp (i.e. into the symlink), and it still worked fine.

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

Zlm 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

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

Jacob added the comment: Great idea :) Maybe we're starting to find the problem. I'm using a Danish version of Windows Vista Home Premium SP1, and C:\Programmer is the danish path for C:\Program Files. I'll try that, and leave another message when i'we tried it.

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

Martin v. Löwis added the comment: > I don't think thats the solution. > "C:\Program Files\Python\2.6\" and > "C:\Programas\Python\2.6\" > are the same, as "C:\Program Files\Python\2.6\" is a symbolic link to > "C:\Programas\Python\2.6\" to allow compatibility with different > operation system l

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

Jacob added the comment: I don't think thats the solution. "C:\Program Files\Python\2.6\" and "C:\Programas\Python\2.6\" are the same, as "C:\Program Files\Python\2.6\" is a symbolic link to "C:\Programas\Python\2.6\" to allow compatibility with different operation system languages. ___

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

Gabriel Genellina added the comment: > 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. > "C:\Program Files\Python\2.6\Lib\idlelib>python idle.py > Traceback (most recent call last): > File "idle.py", line 21, in > idle

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

Jacob added the comment: Okay, i'll try to find a key for Vista in all my drawers, and install a clean version, try it, and then i'll tell you the result. I just can't see what could produce the error at our computers. ___ Python tracker

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

Martin v. Löwis added the comment: > I think this situation can be easily > reproduced by installing Pyhton to other than the default path on > Windows Vista. I could not reproduce it that way. I just installed Python 2.6.1 into c:\tmp\python26, on Vista SP1 x64 (although I installed the 32-bit

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

Zlm 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 also don't think this

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

Jacob added the comment: I don't think it's just his machine (and mine), but i don't think so. Unfortunealy, i don't have a Windows Vista key ready, else i'd have testet it on a clean install, but i'll try to install the same package on the next computer with Vista i stumple upon. _

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

Martin v. Löwis added the comment: > Could this problem be related to paths with slashes and backslashes? Unlikely. The exact same package works on many other machines, so there must be something strange with your machine. Can you run the Sysinternals filemon to find out what files it is acces

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

Zlm 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. "{C:\Programas\Pyt

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

Martin v. Löwis added the comment: > Yes, I did. So do you have a file C:\Programas\Python\2.6\tcl\tcl8.5\init.tcl ? ___ Python tracker ___ __

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

Zlm added the comment: Yes, I did. ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/option

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

Martin v. Löwis added the comment: zlm, did you chose to install Tcl/Tk when installing Python? ___ Python tracker ___ ___ Python-bugs-list mai

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

Zlm 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 line, the same error is

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

Jacob <[EMAIL PROTECTED]> added the comment: No, nothing. It's just a standart clean installation. ___ Python tracker <[EMAIL PROTECTED]> ___ ___

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

Martin v. Löwis <[EMAIL PROTECTED]> added the comment: Do you have TCL_DIR or TK_DIR environment variables set? -- nosy: +loewis ___ Python tracker <[EMAIL PROTECTED]> ___

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

New submission from Jacob <[EMAIL PROTECTED]>: Hello. I run Python 2.5.2 (r252:60911, Feb 21 2008, 13:11:45) on Windows Vista Home Premium. IDLE won't start if not installed in the default directory. When insalled in a custom directory, running idle.py (\Lib\idlelib\idle.py) produces this error: