UNC paths are not supported. Defaulting to Windows directory.
See original GitHub issueRunning 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?
Issue Analytics
- State:
- Created 5 years ago
- Comments:31 (12 by maintainers)
Top Results From Across the Web
UNC paths are not supported. Error Message comes up. Is it ...
"CMD. EXE was started with the above path as the current directory. UNC paths are not supported. Defaulting to Window directory."
Read more >UNC Paths Not Supported - Windows and Daylighting
UNC Paths Not Supported ... If you open a file with such a path, the program will crash when you try to import...
Read more >How to run batch file from network share without "UNC path ...
I am trying to run a batch file from a network share, but I keep getting the following message: "UNC path are not...
Read more >CMD does not support UNC paths as current directories | Fix ...
Solved - Trying to access a share drive from the command prompt on your Windows 10 computer. This Video give you a details...
Read more >"UNC paths are not supported. Defaulting to Windows ...
"UNC paths are not supported. Defaulting to Windows directory." when launching Autodesk Online Deployment .bat file.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
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.