-
-
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 can't find setup.py in dependency with subdirectory #3019
Comments
I can confirm, there's been a pull request to support this in the past: #507 Example output:
Note that installing it through pip works effortlessly. |
I think I may have introduced this bug recently. @wolph can you tell me what shell you're using? |
I'm using the z-shell Not sure if it broke recently, this is the first time I've tried one of these with pipenv to be honest. |
I'm pretty sure it broke recently, I've been relying on this feature for months and it only broke when 2018.10.9 was released |
Thanks guys I think I have a fix, having a testable example was super helpful |
- Upgrade pythonfinder - Upgrade vistir - Upgrade requirementslib - Vendor backported version of `functools.lru_cache` for performance - Fix editable dependency installation when markers are present - Fix extraneous resource warnings - Fix filesystem output stream encoding issues - Fix pythonfinder non-standard python name issues - Provide full interaction layer to `Pipfile` and `Pipfile.lock` in requirementslib - Fixes #3017 - Fixes #3014 - Fixes #3021 - Fixes #3019 Signed-off-by: Dan Ryan <[email protected]>
- Upgrade pythonfinder - Upgrade vistir - Upgrade requirementslib - Vendor backported version of `functools.lru_cache` for performance - Fix editable dependency installation when markers are present - Fix extraneous resource warnings - Fix filesystem output stream encoding issues - Fix pythonfinder non-standard python name issues - Provide full interaction layer to `Pipfile` and `Pipfile.lock` in requirementslib - Fixes #3017 - Fixes #3014 - Fixes #3021 - Fixes #3019 Signed-off-by: Dan Ryan <[email protected]> Update vendored dependencies - Update shellingham, tomlkit, requests, urllib3, certifi, vistir and parse - Fixes #2820 - Fixes #2852 Signed-off-by: Dan Ryan <[email protected]> Cleanup old vendored dependencies Signed-off-by: Dan Ryan <[email protected]>
Thanks! |
Issue description
One of our projects has a dependency on a private git repo. The dependency is in a subdirectory of that repo, which is a monorepo. The dependency is specified in the Pipfile like this:
Expected result
The repo should be cloned, and pipenv should execute the
setup.py
in the subdirectory of the repo. I have confirmed this is the case in the following versions of pipenv:Actual result
Pipenv tries to execute
python setup.py ...
in the root of the dependency, rather than in the subdirectory as expected. Installing the same dependency using the latest version ofpip
directly still works. I verified that this issue was introduced inpipenv==2018.10.9
.Steps to replicate
setup.py
, but the root of the repo should not.pipenv install
and note that the installation of the dependency fails because pipenv looks forsetup.py
in the root of the cloned repo, rather than in the subdirectory.The text was updated successfully, but these errors were encountered: