You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pipenv is able to install a local wheel dependency and add it to Pipfile.
The Pipfile can be then used to install dependencies on other machines, including non-windows environments.
Actual result
The generated Pipfile works locally but fails on other machines (eg linux)
Install fails with parse error
Everything runs fine locally, and the dependency is installed properly on new enviroments.
Running pipenv install on non-windows machines fails.
Traceback from running on WSL and Heroku below.
Notes
Local Pipenv: 2018.05.18
WSL: Pipenv: 2018.05.18
Heroku Pipenv: 11.8.2
Maybe it is a windows path issue, and the way the path is added on windows?
And Posix machines trip up when the read the requirement
remote: -----> Installing dependencies with Pipenv 11.8.2…
remote: Installing dependencies from Pipfile.lock (58b73d)…
remote: WARNING: Invalid requirement, parse error at "'.\\vendor'"
remote: ABORTING INSTALL... You will have to reinstall any packages that failed to install.
remote: You may have to manually run pipenv lock when you are finished.
Expected result
Pipenv is able to install a local wheel dependency and add it to Pipfile.
The Pipfile can be then used to install dependencies on other machines, including non-windows environments.
Actual result
The generated Pipfile works locally but fails on other machines (eg linux)
Install fails with parse error
Steps to replicate
pipenv install vendor/stargate -0.14.2-py3-none-any.whl
A Pipfile is _automatically created:
(other packages omitted)
Everything runs fine locally, and the dependency is installed properly on new enviroments.
Running
pipenv install
on non-windows machines fails.Traceback from running on WSL and Heroku below.
Notes
Local Pipenv: 2018.05.18
WSL: Pipenv: 2018.05.18
Heroku Pipenv: 11.8.2
Maybe it is a windows path issue, and the way the path is added on windows?
And Posix machines trip up when the read the requirement
Full tracebacks below:
WSL
Heroku TB
Update
Manually changed pipfile entry from:
stargate = {path = ".\\vendor\\stargate-0.14.2-py3-none-any.whl"}
to
stargate = {path = "./vendor/stargate-0.14.2-py3-none-any.whl"}
After the change, the Pipfile can run on linux, and windows.
So maybe the solution is, ensure Pipfile path's are always stored posix-style?
That's 100% the problem.
Fixing the path manually to posix style also fixed my failing heroku deployment using Pipenv
11.8.2
The text was updated successfully, but these errors were encountered: