Network Folders don't seem to work as expected.

[GoogleCodeExporter]

When using WinPython 2.7.3.0 beta4 the Network Folder support seems broken.

Steps to reproduce the error:

1. Mount a Network Folder (in this case P:)
2. Try to change the folder

>>> os.chdir("D:\\")
>>> os.chdir("P:\\")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
WindowsError: [Error 3] The system cannot find the path specified: 'P:\\'

Cheers,
Simon

Original issue reported on code.google.com by simon.br...@gmail.com on 29 Aug 2012 at 9:06

[GoogleCodeExporter]

I can't reproduce this bug.
Here are the exact steps of my attempt to reproduce this behavior:
(I have a network folder Z: which is automatically connected at Windows startup)
  * open the WinPython python interpreter ('python.exe' launcher, the one located in the same folder as 'WPPM.exe')
  * here is the result (no error):

Python 2.7.3 (default, Apr 10 2012, 23:31:26) [MSC v.1500 32 bit (Intel)] on 
win32
Type "help", "copyright", "credits" or "license" for more information.
>>> import os
>>> os.chdir('Z:\\')
>>>

Are you sure it's related to WinPython?
(have you done the same test with a standard Python interpreter?)

Moreover, I'm not seeing how the "portable" characteristics of WinPython could 
affect the network drives.

Original comment by pierre.raybaut on 29 Aug 2012 at 9:47

[GoogleCodeExporter]

It works using Python-xy 2.7.2 but fails on WinPython. The OS is Windows 7 64 
Bit.

Output from python xy:

Python 2.7.2 (default, Jun 12 2011, 15:08:59) [MSC v.1500 32 bit (Intel)] on win
32
Type "help", "copyright", "credits" or "license" for more information.
>>> import os
>>> os.chdir("p:/")
>>>

Original comment by simon.br...@gmail.com on 29 Aug 2012 at 10:23

[GoogleCodeExporter]

I am getting the same error. Network drives seem to be problematic also 
otherwise: When I start cmd.exe from a mapped network drive (Z:\\) then it 
gives me this error quoting the unmapped UNC: 
'\\NAS\User\WinPython-64bit-2.7.3.0rc1\python-2.7.3.amd64'
CMD.EXE was started with the above path as the current directory.
UNC paths are not supported.  Defaulting to Windows directory.

Original comment by fzumst...@gmail.com on 21 Sep 2012 at 7:10

[GoogleCodeExporter]

Simon, Felix,

Could you please check if these bugs are happening only when running Python 
from a launcher (.exe files at the root directory) or if they are also 
happening when running Python from batch scripts (.bat files inside the 
'scripts' folder)?

Original comment by pierre.raybaut on 22 Sep 2012 at 6:10

[GoogleCodeExporter]

Pierre,

When running from the scripts it works perfectly well.

Original comment by fzumst...@gmail.com on 22 Sep 2012 at 8:09

[GoogleCodeExporter]

And have you tried to reproduce this bug with the "magic" Spyder launcher 
(http://www.google.com/url?sa=D&q=http://winpython.googlecode.com/files/Spyder_U
AC_test.exe)?
...we never know!

Original comment by pierre.raybaut on 22 Sep 2012 at 8:26

[GoogleCodeExporter]

yes, this seems to resolve that indeed...!

Original comment by fzumst...@gmail.com on 23 Sep 2012 at 4:09

[GoogleCodeExporter]

Wonderful!

So this issue was closed by revision 867925ba4fc2.

Original comment by pierre.raybaut on 23 Sep 2012 at 4:27

• Changed state: Fixed