-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
pipenv 2022.9.20 broken #5367
Comments
@scastria We changed dependencies for the Pipfile to plette -- so far I am unable to reproduce this though -- environment variable expansion seems to work. I am wondering if you need to make |
Unfortunately, there is no error. It succeeds but installs no dependencies at all. None from pypi and none from my private source. Adding verbose doesn't add much. I don't think it is an expansion issue because if that was the case, I should get an error stating it can't find my_utils. Here is the output:
|
Hopefully, you have access to docker. That should be a good way to allow you to reproduce since you will start with exactly the same starting point as me. Here is the Pipfile:
Here is the Dockerfile:
If you run the docker container, it spits out the list of dependencies. You will see it does NOT list requests as a dependency since pipenv didn't actually do anything:
|
If you then change the Dockerfile to install 2022.9.8 version of pipenv, like this:
and then run that new container, it works and shows requests in the list of dependencies:
|
@scastria That first example worked for me -- meaning it actually worked and did not reproduce the issue:
|
This seems to be a regression in the |
I can confirm that :
|
Can you provide instructions on how to test with a branch of pipenv? I have not done that before. |
|
I had a similar issue running: |
|
Hi, I hate to be the bearer of bad news, but it seems that |
@TurnrDev Could you provide updated reproduction steps? |
Absolutely, we had two git branches we were swtiching between, one had a requirement that the other didn't. Our devs then run So, basically... I guess it could also be reproduced by directly editing the I tested on three versions. 2022.10.4, 2022.10.8 and 2023.3.20. It only worked in 2022.10.4 Specifically, the new requirement we added was inflection, but the bug was not isolated to that requirement. On 2022.10.8 and 2023.3.10, |
I can run new tests and get the program outputs but I promise it's entirely useless. Just showing this regardless:
|
Shawn -- please have a look at #5653 and
help me validate if this truly fixes the problem. Local testing seemed
good, the CI is running the unit tests now, but I'd appreciate more eyes on
it.
…-Matt Davis
On Sun, Apr 16, 2023 at 7:22 PM Shawn Castrianni ***@***.***> wrote:
Any update on this? I just tried the latest 2023.3.20 and it fails with
pipenv install --skip-lock
—
Reply to this email directly, view it on GitHub
<#5367 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADVFFBX5UMYFRNENLJGGFDXBR5KZANCNFSM6AAAAAAQRQJVKQ>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
@matteius Sorry, I posted here by mistake as my problem is new. |
When I run: pipenv install --system --skip-lock
it doesn't install anything.
My Pipfile is:
If I use pipenv 2022.9.8 (the previous version), everything works fine.
The text was updated successfully, but these errors were encountered: