You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is at least one bug / ambiguity in behavior. If a user passes 1 interpreter (say the current interpreter executing pex) and one or more platforms that do not match the current interpreter version but do match the os arch, then the wrong interpreter will be passed to resolve and used to silently build the wrong wheel: https://github.com/pantsbuild/pex/blob/8fd5e1b989224046cd0fb038cfebc11b4c10a8c9/pex/resolver.py#L505-L568
Either the build should fail or else an attempt to find a correct local interpreter should proceed and then, if not found, the build should fail; otherwise that interpreter should be passed to resolve.
The text was updated successfully, but these errors were encountered:
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#771Fixes#763Fixes#761Fixes#735Fixes#694Fixes#660Fixes#658Fixes#642Fixes#641Fixes#628Fixes#620Fixes#614Fixes#611Fixes#608Fixes#439Fixes#415Fixes#387Fixes#315
There is at least one bug / ambiguity in behavior. If a user passes 1 interpreter (say the current interpreter executing pex) and one or more platforms that do not match the current interpreter version but do match the os arch, then the wrong interpreter will be passed to resolve and used to silently build the wrong wheel:
https://github.com/pantsbuild/pex/blob/8fd5e1b989224046cd0fb038cfebc11b4c10a8c9/pex/resolver.py#L505-L568
Either the build should fail or else an attempt to find a correct local interpreter should proceed and then, if not found, the build should fail; otherwise that interpreter should be passed to resolve.
The text was updated successfully, but these errors were encountered: