so I was wondering does the set of indexes for the...
# general
b
so I was wondering does the set of indexes for the python.repos use a .netrc file or does it have to be embedded in the pants.toml
tested and it seems to work.
e
Pex uses `~/.netrc`; so if by "it" you mean credentials, then no.
b
mostly for generate-lockfiles, but also for some package builds
e
Latest Pex, which I'm pretty sure no Pants version uses, supports
--use-pip-config
to read creds from there.
b
nice. looking forward to that.
e
It won't happen unless you file and maybe pitch in and plumb.
All volunteer!
b
yeah, once I get things settled for this project I plan on trying to contribute some stuff back. Old data science packages are a complete pain.
e
Great. Yeah - they definitely are. Python / PyPA really needs to get its act together in this space.
b
I can't believe that people consider any of this acceptable. It takes so much time getting dependencies together that it's a wonder that data scientists get anything going.
e
I think they know its not good. They made the step of a PyPA survey last year or early this year - I forget - but the ensuing discussion on the feedback from the survey was classic OSS disfunction of too large a group of cooks in the kitchen leading to no progress.
b
so it looks like if you do use a .netrc the pex binary works when authenticating to a remote host. Because of the env -i command at the beginning though it clobbers the NETRC environment variable when trying to run it using a local .netrc in the build directory
so it looks like the requests library does the right thing
e
Just so you know, the
__run.sh
simulates what the Pants engine does, but the Pants engine doesn't actually use it at all. Instead, it executes the process via Rust code directly. The
__run.sh
is only generated for debugging purposes when you retain sandboxes as an additional file not normally generated or used.
And I have no clue about the NETRC env var, never heard of that being a knob.
b
oh, didn't know that
yeah, it was added a bit ago. Prior to that the requests library only looked in the ~ directory for the user
e
Ok, well you're getting lucky a few times there I think. Pex doesn't respect that var, although it does respect
~/.netrc
. That said, most network Pex operations forward to Pip which happens to use a vendored requests.
b
don't worry, I'm abusing environment variables all over the place to get things to work... 🙂