Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
The interpreter we run Pex with affects the resolve
See original GitHub issuepython3.6 -m pex.cli lock create --style=universal --interpreter-constraint 'CPython<3.9,>=3.8' 'aioconsole'
Fails with ERROR: Package 'aioconsole' requires a different Python: 3.6.6 not in '>=3.7' .
Running with python3.7 succeeds.
Removing --style=universal succeeds.
Note: aioconsole only publishes an sdist.
Issue Analytics
- State:
- Created a year ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
PEX_PATH transitivity · Issue #1423 · pantsbuild/pex - GitHub
Activation involves resolving all needed dists for the current runtime interpreter from within the hermetic PEX in question; I.E.: Even during activation, each ......
Read more >pex 1.6.9 - PyPI
Launch an interpreter with requests, flask and psutil in the environment: ... Bug fix: Since 69649c1 we have been unpatching the side-effects of...
Read more >Error from Pants pex install: "FAILURE: Unable to detect a ...
I 'm guessing you have a pants.ini config in your repo that is missing the key name changes. There is a tool to...
Read more >Residential PEX Water Supply Plumbing Systems - HUD User
Like most plastics, the long-term performance of PEX will be affected by UV radiation from sunlight. Although most PEX pipes have some UV...
Read more >python - Pants build
[python].resolves will use your global interpreter constraints set in ... Note: Only takes effect if you use Pex lockfiles. Use the default
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Presumably, with verbosity turned up, it will be revealed this happens in the resolve post-processing phase where sdists are built into wheels to get
Requires-*metadata for the lock. If so, this was just an oversight and, when an IC is present in a universal lock Pex should pick (demand) a local interpreter that fits the IC to do the post-processing with.Putting debugging/learning notes here, even though they are likely obvious to @jsirois, or plain wrong.