[issue8869] execfile does not work with UNC paths

Changes by Tim Golden : -- resolution: -> out of date status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue8869] execfile does not work with UNC paths

stier08 added the comment: yep exec (open (...)) is OK here thanks -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue8869] execfile does not work with UNC paths

Amaury Forgeot d'Arc 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 remove the leading '\\

[issue8869] execfile does not work with UNC paths

Tim Golden 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 Python 2.x is nearin

[issue8869] execfile does not work with UNC paths

New submission from stier08 : 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 to reproduce (ass