When given a Windows style path as an editable requirement on the command line, pipenv fails to find it.

[Kroppeb]

Issue description

Using '' in a editable dependency instead of '/' will not work.

Expected result

Both pipenv install ..\..\libraries\foobar and pipenv install -e ..\..\libraries\foobar work

Actual result

The first command succeeds, but the second one doesn't. It errors with

....librariesfoobar is not a valid editable requirement. It should either be a path to a local project or a VCS URL

$ pipenv --support

Pipenv version: '2022.12.19'

Pipenv location: 'C:\\Users\\robbe\\AppData\\Local\\Programs\\Python\\Python311\\Lib\\site-packages\\pipenv'

Python location: 'C:\\Users\\robbe\\AppData\\Local\\Programs\\Python\\Python311\\python.exe'

OS Name: 'nt'

User pip version: '22.3.1'

PEP 508 Information:

{'implementation_name': 'cpython',
 'implementation_version': '3.11.2',
 'os_name': 'nt',
 'platform_machine': 'AMD64',
 'platform_python_implementation': 'CPython',
 'platform_release': '10',
 'platform_system': 'Windows',
 'platform_version': '10.0.22621',
 'python_full_version': '3.11.2',
 'python_version': '3.11',
 'sys_platform': 'win32'}

Pipenv?specific environment variables:

---

[matteius]

@Kroppeb Could you check with: #5793

[Kroppeb]

I'll see if I can try that out this week. I noticed it got merged into main, does that mean I just have to update my pipenv?

[matteius]

@Kroppeb Just released a new version 2023.8.26 that addresses some recent findings regarding editable installs -- specifically moved more of the logic to use Pathlib, so hopefully this helps in your case as well.