Changes by Tim Golden m...@timgolden.me.uk:
--
resolution: - out of date
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8869
___
New submission from stier08 stie...@gmail.com:
execfile() builtin function does not work with UNC paths on Windows platform
(Windows 7 x64 has been tested, python 2.6.5)
Since standard IO operations successfully process UNC paths, therefore this
behavior of execfile() seems to be a bug.
Code
Tim Golden m...@timgolden.me.uk added the comment:
Since execfile is basically shorthand for exec (open (filename).read ()),
and since open (filename) *does* support the full range of filepath
syntax on Windows, and since execfile has been removed in py3k in favour
of exec (open ...)), and since
Amaury Forgeot d'Arc amaur...@gmail.com added the comment:
Reproduced on WinXP.
execfile() does not work because it calls the system function stat();
this function does accept UNC paths (like \\machine\share\file), but not paths
which contain a wildcard character ('?' or '*')
I suggest to
stier08 stie...@gmail.com added the comment:
yep exec (open (...)) is OK here thanks
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8869
___
___
