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
support for --editable pip requirements? #134
Comments
+1 . I can't say that it is because of the described issue. However editable dependencies are clearly not supported. |
What is missing to support this? There are so many ways to build packages in python, so it might help to give a concrete use case and point out how and where the new feature appear. |
From the looks of it it seems that the shebang-rename script should peek into the One could make this optional by detecting possible I think for supporting this the passing of the flag is already supported, either via the provided extra arguments for |
Is there a reason to use editable at all? If you drop As for the pth file problem, we've solved this in other places with virtualenv-tools. Our fork which supports pth files |
Remove "-e " from your requirements.txt and all will works fine. Now, in pip its supported. See point 4 https://pip.pypa.io/en/stable/user_guide/#requirements-files |
Should be resolved by mentioning it in "howtos" ⇒ add "docs" label |
This commit removes dh-virtualenv build path in editable pip requirements and other local/bin files. There's a bug in dh-virtualenv editable paths: spotify/dh-virtualenv#134 It happens when requirements.txt file has the "-e" option for git sources, but it worked in AM version < 1.10 because the "-e" was not used.
This commit removes dh-virtualenv build path in editable pip requirements and other local/bin files. There's a bug in dh-virtualenv editable paths: spotify/dh-virtualenv#134 It happens when requirements.txt file has the "-e" option for git sources, but it worked in AM version < 1.10 because the "-e" was not used.
This commit removes dh-virtualenv build path in editable pip requirements and other local/bin files. There's a bug in dh-virtualenv editable paths: spotify/dh-virtualenv#134 It happens when requirements.txt file has the "-e" option for git sources, but it worked in AM version < 1.10 because the "-e" was not used.
This commit removes dh-virtualenv build path in editable pip requirements and other local/bin files. There's a bug in dh-virtualenv editable paths: spotify/dh-virtualenv#134 It happens when requirements.txt file has the "-e" option for git sources, but it worked in AM version < 1.10 because the "-e" was not used
This rebuild was needed due to a bug in dh-venv: archivematica/Issues#903 spotify/dh-virtualenv#134
This commit removes dh-virtualenv build path in editable pip requirements and other local/bin files. There's a bug in dh-virtualenv editable paths: spotify/dh-virtualenv#134 It happens when requirements.txt file has the "-e" option for git sources, but it worked in AM version < 1.10 because the "-e" was not used
This rebuild was needed due to a bug in dh-venv: archivematica/Issues#903 spotify/dh-virtualenv#134
This rebuild was needed due to a bug in dh-venv: archivematica/Issues#903 spotify/dh-virtualenv#134
This commit removes dh-virtualenv build path in editable pip requirements and other local/bin files. There's a bug in dh-virtualenv editable paths: spotify/dh-virtualenv#134 It happens when requirements.txt file has the "-e" option for git sources, but it worked in AM version < 1.10 because the "-e" was not used
This rebuild was needed due to a bug in dh-venv: archivematica/Issues#903 spotify/dh-virtualenv#134
My requirements.txt file has requirements that point to my company's internal git repo, for example:
When I build a package, the easy-install.pth file references the build directory, not the dpkg install dir.
Everything else works fine; If I update the easy-install.pth file, the service runs as expected.
Are -e or "editable" dependencies supported by dh-virtualenv?
The text was updated successfully, but these errors were encountered: