On Sun, Jan 24, 2016 at 7:27 PM, Terry Reedy <tjre...@udel.edu> wrote: > > More specifically, / is not accepted in paths to be executed. It seems to be > generally accepted in path arguments, as in cd path, or > > C:\Users\Terry>C:\programs\python35\python.exe C:/programs/python34/tem.py
An exception that comes to mind is takeown.exe, which fails to parse paths that use slash as the value for /F. A couple of exceptional cases in the Windows API come to mind. The "\\?\" extended path syntax requires backslash. Also referencing named kernel objects requires a backslash after either the "Global" prefix or a private namespace prefix. For example, in "Global/ObjectName" the slash is just another character in the name, so the object manager doesn't follow the "Global" symbolic link to \BaseNamedObjects but instead creates"Global/ObjectName" in the session's named objects directory. -- https://mail.python.org/mailman/listinfo/python-list
