quick question: We're seeing this warning: `pex: P...
# general
a
quick question: We're seeing this warning:
pex: Please build pex with the subprocess32 module for more reliable requirement installation and interpreter execution
. Is this something we just
pip install
locally or is there some way of putting this in a config to always download and use (e.g in
pants.ini
)?
a
i'm not sure -- i might try asking in #pex too if no one responds here
w
how are you using pex? with pants?
a
In the case that I'm reporting from, we build the pex with pants then run the pex file itself.
let me know if I should move this to the #pex channel
w
Ok, so that would be a pants issue then I think. #pex isn't the worst place for it, but most likely this will be resolved by pex being upgraded in pants
@acoustic-book-58772 What version of pants is this?
a
1.13
we're having some issues upgrading to 1.14 because of the thrift upgrade that I haven't gotten around to
w
You can downgrade thrift by specifying an older version
Copy code
$ ./pants help-advanced thrift

thrift options:

--thrift-version=<str> (default: '0.10.0')
    Version of the thrift binary to use
so
Copy code
[thrift]
version: 0.10.0
in
pants.ini
compare/contrast the defaults in `1.13.x`/`1.14.x` and then pin to the older one
a
Hmmm. Though I think we would like to upgrade thrift, there were just a few minor details that we're still fixing through. Point is, we're on 1.13 at the moment haha.
w
sure... just pointing out that they can be decoupled
👌 1
a
But anyway, try running in 1.14 and see if this is still a problem?
w
yea. and if not that, then
1.15.0rc1
a
sounds good. I'll play with that and let you know!
Hmmm tried both
1.14.0
and
1.15.rc1
, and both were spitting out that message still. Though this time around I was just using
./pants run
instead of building the pex then running it.
w
Ok. Worth searching for existing github issues (in
pantsbuild/pants
,
pantsbuild/pex
). John has been working on updating pex in pants, and it might have been reported in that context