-
-
Notifications
You must be signed in to change notification settings - Fork 258
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
pex packaging code from git? (git+https support?) #439
Comments
+1 |
This would help out tremendously! Sometimes it is necessary to install from a git version of a package until a release is made available. Even worse, when a package is abandoned and it takes weeks to get control over it. |
+1 |
I think like for #429 a PR implementing this support would be welcome. |
Today I wanted to test this branch of importlib_metadata against pex, but couldn't readily due to this issue. I'd love to see this. I was able to work around the issue by:
|
This changes Pex to vendor pip and defer all resolution and building to it. As part of this change some ambiguous and / or broken features were changed and APIs adjusted: + The egg distribution format is no longer supported. + The deprecated `--interpreter-cache-dir` CLI option was removed. + The `--cache-ttl` CLI option and `cache_ttl` resolver API argument were removed. + The resolver API replaced `fetchers` with a list of `indexes` and a list of `find_links` repos. + The resolver API removed (http) `context` which is now automatically handled. + The resolver API removed `precedence` which is now pip default precedence - wheels when available and not ruled out via the `--no-wheel` CLI option or `use_wheel=False` API argument. + The `--platform` CLI option and `platform` resolver API argument now must be full platform strings that include platform, implementation, version and abi; e.g.: `--platform=macosx-10.13-x86_64-cp-36-m`. + The `--manylinux` CLI option and `use_manylinux` resolver API argument were removed. Instead, to resolve manylinux wheels for a foreign platform, specify the manylinux platform to use with an explicit `--platform` CLI flag or `platform` resolver API argument; e.g.: `--platform=manylinux2010-x86_64-cp-36-m`. Fixes #781 Additionally: Fixes #771 Fixes #763 Fixes #761 Fixes #735 Fixes #694 Fixes #660 Fixes #658 Fixes #642 Fixes #641 Fixes #628 Fixes #620 Fixes #614 Fixes #611 Fixes #608 Fixes #439 Fixes #415 Fixes #387 Fixes #315
Like #429, I'm trying to use pex with Pipenv. Unlike #429, I'm trying package code from an upstream git repo into a pex file.
giving me a requirements.txt including lines like:
which pex chokes on:
Is this a desired feature of pex? Am I doing something wrong?
Thanks!
The text was updated successfully, but these errors were encountered: