John Sirois

I've gathered a fuller history of this feature here for perusal if it helps: Idea for `pip download`: + Break it out as its own subcommand issues: #906 and #2643...

I've worked around this bug over in https://github.com/pantsbuild/pex/pull/1367. I'd still be happy to work on a fix if any of you come around to seeing this as a bug by...

FWIW, Pex eventually progressed to allowing you to fully patch the marker environment and supported tags to take away any guesswork. So the idea is the CLI accepts a json...

Yeah. That's exactly what Pex does: https://pex.readthedocs.io/en/v2.1.79/buildingpex.html#complete-platform https://github.com/pantsbuild/pex/blob/main/pex/resolve/target_options.py#L208-L248

> This would allow for a future where you could build an e.g. lock file for a different platform as all the input data about the target platform is contained...

I'm willing to be the PEP author for this @brettcannon and write up a packaging PR for the reference implementation. I'll certainly need a bit of guidance, but as the...

I spent a good bit of time on this but failed to root cause. I'm un-assigning and placing back on the shelf.

Probably an interesting data point. I'm getting this with good regularity: ``` $ ./build-support/bin/release.sh build-wheels 01:50:32.74 [INFO] Initializing scheduler... 01:50:33.00 [INFO] Scheduler initialized. [=== 00:00 Building Pants wheels with Python...

Afaict, not intersting enough. I have 5 identical log files save for thread ids. They all look like this example from `.pants.d/exceptions.12087.log`: ``` Fatal Python error: Aborted Current thread 0x00007f2d1ccae640...

But we've also had others, like so from a user: ``` (gdb) bt #0 raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:50 #1 #2 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #3 0x00007f2702c73859 in __GI_abort () at...