pipenv: UNC paths are not supported. Defaulting to Windows directory.
Running pipenv shell from (Administrator) command prompt in Windows 10 Pro to launch virtual environment outputs:
UNC paths are not supported. Defaulting to Windows directory.
when run from within a mapped network drive.
The virtual environment does not show up in () before the drive. (If I am in the virtual environment at this point, it is easy to forget that I am and I could forget to exit out. Moreover, it doesn’t show which environment I’m in).
If I type activate afterwards, the environment in () shows up, but I don’t have to be in the folder where Pipfile or Pipfile.lock are located.
- Is this expected behavior?
- Is this somehow a holdover from virtualenv’s or virtualenvwrapper’s ability to utilize UNC paths?
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 31 (12 by maintainers)
Hello @techalchemy and @erinxocon. I can confirm on my machine that PR #2331 has solved the issue of this PR! (Must clone repo into site-packages and install with
pip install -e .as not yet available from current pipenv wheel usingpip install pipenv.) Thank you so much for your help.As an aside, I’m getting a few new interesting errors when trying to install packages now. This is a separate issue though. I’ll post on StackOverflow to see if I can get any resolution on it, but here is the text file for your records.
locking_devpackages_errors.txt
Thank you again so much and have a great weekend!
@techalchemy Can we start over? I feel we got off on the wrong foot and I’m sorry. I was frustrated.
I respect your authority as the maintainer and completely understand its importance and necessity. I’m sorry if I came across as though I had the right to contribute. I do not. I apologize.