Skip to content
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

When using resolve_multi, not all combinations of interpreters and platforms work. #658

Closed
jsirois opened this issue Jan 30, 2019 · 0 comments · Fixed by #788
Closed

When using resolve_multi, not all combinations of interpreters and platforms work. #658

jsirois opened this issue Jan 30, 2019 · 0 comments · Fixed by #788
Assignees

Comments

@jsirois
Copy link
Member

jsirois commented Jan 30, 2019

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.

@jsirois jsirois self-assigned this Nov 14, 2019
jsirois added a commit that referenced this issue Nov 14, 2019
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant