https://pantsbuild.org/ logo
Join Slack
Powered by
If we want to use the pex binary from python that ...
# pex
a
If we want to use the pex binary from python that isn’t 2.7 or 3.7, how are we meant to do so? If I run 
./pex37
with 3.6 as my 
python3
on my 
PATH
it complains that 
python3.7
couldn’t be found in the PATH…
e
That's issue worthy. Pex will need an update to the release process to be either less specific, ie pex3 + python3 shebang or else add another binary (pex36). I'd love not to do the latter. For now, you can build your own pex using pex or else re-write the released pex's shebang.
👍 1
The short answer should have been you're not meant to do so - you're meant to build your own.
a
Is it just the shebang?
e
Pretty darn sure, yes.
a
Can we just release one 
pex
then, and have people munge paths if they need more control?
👍 1
e
Yes. I'll file an issue this evening and perhaps solve this for the 1.6.1 release tonight.
🎉 1
a
Awesome, thanks!
e
Unfortunately, for 1.6.1, I'll just have to add pex34, pex35 and pex36 - the gory details are here: https://github.com/pantsbuild/pex/issues/654
a
Ugh fun 😞 Thanks for investigating (and flexibiling!)
IIRC @witty-crayon-22786 was looking at the ORing interpreter constraints issue…
e
He was - it looks like in the wrong place. I've updated his issue to point to the pex issue.
❤️ 1
w
thanks!
h
@average-vr-56795 did you figure out how to hackily get pex37 working with pex36? Do you rewrite PEX-INFO?
e
I published pex3{4,5,6} in addition to the existing pex{2,3}7. See here: https://github.com/pantsbuild/pex/releases/tag/v1.6.1
Do you need this for an older release?
h
Yes for older release. But now that Pants’ upgrade to Pex is coming soon I can go without this workaround! I was trying to hack a workaround to be able to iterate on Py3 release PR
e
I'm in Spain through the 20th with odd hours around climbing. While I have the chance, I'll retroactively publish pex 3{4,5,6} for 1.5.3 and 1.6.0 just in case.
❤️ 1
👌 1
OK - Done for 1.5.3 which Pants uses now and 1.6.0.
❤️ 1
w
Have fun John!
✈️ 1
e
Thanks Stu!
Open in Slack
PreviousNext
Powered by