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.

Sign up for GitHub

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

Jump to bottom

Resolve seems to be inconsistent in python 3.4 #611

Closed
OniOni opened this issue Oct 26, 2018 · 1 comment · Fixed by #788
Closed

Resolve seems to be inconsistent in python 3.4 #611

OniOni opened this issue Oct 26, 2018 · 1 comment · Fixed by #788
Assignees
@jsirois
Labels
bug enhancement resolver

Comments

@OniOni
Copy link
Contributor

OniOni commented Oct 26, 2018

While looking at pants python 3 tests and trying to fix failures, we noticed that resolve was different in python 3.4 vs. python 2.7.

The test expects the resolve to find the macosx_10_10_x86_64 wheel for cffi. We have seen failures with python 3.4, where resolver grabs the macosx_10_6_intel wheel.

The result is not incorrect, but unexpected. It is also not stable, this test does not fail 100% of the time.
@jsirois
Copy link
Member

jsirois commented Oct 26, 2018

For easiest repro, the failing test in pants unstably resolves either cffi-1.9.1-cp34-cp34m-macosx_10_10_x86_64.whl or cffi-1.9.1-cp34-cp34m-macosx_10_6_intel.whl (https://pypi.org/project/cffi/1.9.1/#files) on OSX for platform v_10_10_x86_64 when running under python 3.4 on OSX in travis-ci.

@jsirois jsirois mentioned this issue Nov 3, 2018
Closed
@jsirois jsirois mentioned this issue Dec 6, 2018
Closed
@jsirois jsirois mentioned this issue Jan 23, 2019
Closed
3 tasks
@jsirois jsirois mentioned this issue Feb 6, 2019
Closed
2 tasks
@jsirois jsirois mentioned this issue Mar 10, 2019
Closed
3 tasks
@jsirois jsirois mentioned this issue Mar 26, 2019
Closed
10 tasks
@jsirois jsirois mentioned this issue Nov 14, 2019
Merged
@jsirois jsirois self-assigned this Nov 14, 2019
jsirois added a commit that referenced this issue Nov 14, 2019
@jsirois
Use pip for resolving and building distributions. (#788)
7509a89 
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
Assignees

@jsirois jsirois

Labels
bug enhancement resolver
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use pip for resolving and building distributions. jsirois/pex
2 participants
@jsirois @OniOni