[issue6470] Tkinter import fails when running Python.exe from a network share

Martin v. Löwis added the comment: Thanks for the patch. Committed as r81701, r81702, r81703 and r81704. -- resolution: -> accepted status: open -> closed ___ Python tracker ___

[issue6470] Tkinter import fails when running Python.exe from a network share

Christoph Gohlke added the comment: > The patch seems to deal with paths that have "UNC" in them; > and the test seems not to. The UNCW path is a result of the call to ctypes.windll.kernel32.GetFinalPathNameByHandleW() in FixTk.py, which translates "\\Server\Share\File" paths to "\\?\UNC\Ser

[issue6470] Tkinter import fails when running Python.exe from a network share

Christoph Gohlke added the comment: Btw, this bug is also present in Python 3.1, of course when using tkinter instead of Tkinter. Here is how to reproduce the bug on your local system: Install python-2.7b2.msi into C:\Python27. Then open a command prompt with administrator privileges and sta

[issue6470] Tkinter import fails when running Python.exe from a network share

Amaury Forgeot d'Arc added the comment: to reproduce: on Vista, start \\%COMPUTERNAME%\c$\python26\python.exe -c "import Tkinter; print Tkinter" In this case, the path returned by GetFinalPathNameByHandle starts with \\?\UNC\. -- ___ Python tracke

[issue6470] Tkinter import fails when running Python.exe from a network share

Martin v. Löwis added the comment: Also, cgohlke, can you please provide complete, detailed instructions on how to reproduce this issue? How do I get python.exe into \\Server\Share in the first place? And why did you not map a network drive letter? --

[issue6470] Tkinter import fails when running Python.exe from a network share

Martin v. Löwis added the comment: Can somebody please explain how the test and the reported bug are related? The patch seems to deal with paths that have "UNC" in them; and the test seems not to. -- ___ Python tracker

[issue6470] Tkinter import fails when running Python.exe from a network share

Christoph Gohlke added the comment: Any chance to get this fixed in 2.7? On Windows, the bug prevents some popular applications and packages, such as pymol and matplotlib, to be used when installed on network shares, as is common practice in computer labs. --

[issue6470] Tkinter import fails when running Python.exe from a network share

Christoph Gohlke added the comment: This issue is also present in Python 2.7b2. The svn trunk requires a slightly different patch (attached). -- versions: +Python 2.7 Added file: http://bugs.python.org/file17304/Tkinter-import-UNCW-trunk.patch ___ P

[issue6470] Tkinter import fails when running Python.exe from a network share

Changes by Brian Curtin : -- type: crash -> behavior ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail

[issue6470] Tkinter import fails when running Python.exe from a network share

Amaury Forgeot d'Arc added the comment: Confirmed here. Added a unit test. -- assignee: -> loewis keywords: +needs review nosy: +amaury.forgeotdarc, loewis stage: -> patch review Added file: http://bugs.python.org/file14491/tk-unc.patch ___ Python

[issue6470] Tkinter import fails when running Python.exe from a network share

New submission from Christoph Gohlke : On Windows Vista 64-bit, when running Python 2.6.2 (32 or 64 bit) from a network share, e.g. \\Server\Share\python26\python.exe, importing Tkinter fails with "WindowsError: [Error 3] The system cannot find the path specified". See session output below for tr