-
-
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 2023.8.26 and 2023.9.1 ignore editable=true for vcs install #5923
Comments
I first noticed this on AWS EC2 after upgrading Amazon Linux 2 from AL2 3.5.5 to AL2 3.5.6. AL2 3.5.5 uses pipenv 2023.7.23, whereas AL2 3.5.6 uses pipenv 2023.8.26. I was also able to reproduce the issue locally on Ubuntu 22.04.3 LTS with pipenv 2023.9.1. |
Worth checking if still an issue in |
@matteius Thanks for the quick reply. I uninstalled
UPDATE: Just verified:
|
@matteius there is a section in the pip docs: https://pip.pypa.io/en/stable/topics/vcs-support/#editable-vcs-installs (I've updated the OP with this link) |
The resolution failure you say is on 2023.9.7 only sounds troubling to me but I'd really need more details around it, since the example Pipfile is just an example format. |
@matteius I can provide more detail about the resolution failure for I verified this by removing the This is on a different (ubuntu) system. The error I'm seeing now is slightly different (both with and without the
(before, on the other system, I got Again, the fresh Should I open a separate issue for this? |
@dennisvang Actually that is probably related to: #5924 There is an associated PR that fixes it. Also I just opened a VCS editable install -- could use help checking it, but it doesn't include the fix for the resolution (two separate PRs right now). |
@dennisvang I merged the resolver fix into main and into the editable vcs branch to make it easier to verify. If you can check out the vcs branch and see if its working for your case, that would be helpful for me including it in a 2023.9.8 release (assuming it passes also CI). |
@matteius After a clean install of
|
Issue description
Pipfile contains a line as follows, to do a vcs install (git) from bitbucket:
Note the
editable = true
.Using
pipenv
2023.7.23
this works as expected: the package is installed as editable, and ends up in myvenv/src
directory.Using
pipenv
2023.8.26
(and2023.9.1
), this does not work as expected: the package is installed normally (i.e. not editable), invenv/lib/python3.8/site-packages
Expected result
I would expect the package to be installed into
venv/src
, as described in the pip docs.Actual result
Package is built and ends up in
venv/lib/python3.8/site-packages
Steps to replicate
Install a package from vcs, using a pipfile similar to the above.
References
Possibly related (?):
The text was updated successfully, but these errors were encountered: