-
Notifications
You must be signed in to change notification settings - Fork 578
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to run make build
with pipenv >=2022.10.9
#2156
Comments
Oh, and I can confirm that |
theCapypara
changed the title
Unable to run
Unable to run Jan 25, 2023
make build
with pipenv 2022.12.19make build
with pipenv >=2022.10.9
adimajo
pushed a commit
to adimajo/lrtree
that referenced
this issue
Jan 27, 2023
Can confirm pretty similar issue with pipenv, version 2018.11.2
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Background:
I wanted to add something to Guake and because of this wanted to checkout the code locally and set it up for development. For that I had a look at the CI and tried to run all make commands used there to make sure I am having a stable environment to work with.
Describe the bug
I am however unable to run
make build
locally without issues.Expected behavior
When checking out the project from source, as described in the docs ( https://guake.readthedocs.io/en/stable/user/installing.html#install-from-source )I expect
make build
to run through without errors after installing dependencies viapipenv install --dev
.Actual behavior
The
pipenv_to_requirements
step fails:Upstream issue: gsemet/pipenv-to-requirements#25
Upstream PR: gsemet/pipenv-to-requirements#26
To Reproduce
See above + see below for my installed package versions.
OS: Arch Linux
Python: 3.10.9
pipenv:
2022.12.19
(The last successful build on Github Actions used2022.11.30
for reference - referring back to the issue above, I'm surprised that this works. The issue might not simply be the pipenv version.)Installed packages in the venv:
The text was updated successfully, but these errors were encountered: