Skip to content

pipenv commands are broken on Windows: 'env' is not recognized #515

@hroncok

Description

@hroncok
> pipenv run naucse serve
Creating a virtualenv for this project…
Pipfile: C:\...\naucse.python.cz\Pipfile
Using C:/.../Python/Python36/python.exe (3.6.8) to create virtualenv…
[ ===] Creating virtual environment...Using base prefix 'C:\\...\\Python\\Python36'
New python executable in C:\...\.virtualenvs\naucse.python.cz-GmZHW9w3\Scripts\python.exe
Installing setuptools, pip, wheel...
done.
Running virtualenv with interpreter C:/.../Python/Python36/python.exe

Successfully created virtual environment!
Virtualenv location: C:\...\.virtualenvs\naucse.python.cz-GmZHW9w3
'env' is not recognized as an internal or external command,
operable program or batch file.

The reason for this is that our commands are:

[scripts]
naucse = "env PYTHONPATH=. python -m naucse"
serve = "env PYTHONPATH=. python -m naucse serve"
freeze = "env PYTHONPATH=. python -m naucse freeze"
test = "python -m pytest test_naucse/"

AFAIK env doesn't work as a command on Windows, but I seriously don't know.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions