Christoph Gohlke <cgoh...@uci.edu> 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
start python.exe as follows:
\\%COMPUTERNAME%\C$\Python27\python.exe -c "from Tkinter import *"
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "\\KLAPAUCIUS\C$\Python27\lib\lib-tk\Tkinter.py", line 38, in <module>
import FixTk
File "\\KLAPAUCIUS\C$\Python27\lib\lib-tk\FixTk.py", line 56, in <module>
for name in os.listdir(prefix):
WindowsError: [Error 3] The system cannot find the path specified:
'UNC\\KLAPAUCIUS\\C$\\Python27\\tcl/*.*'
It does not matter whether the network share is mapped as a drive letter or
not, the Tkinter import fails with the same WindowsError. Also mounted network
drives do have problems with UAC.
A local Python installation can simply be copied to a network share and used
from there from several other computers. All that eventually needs attention is
the python*.dll, some scripts, and the MSVC runtime. I have deployed Python
like this for years in several computer labs.
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue6470>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
