Chris Burroughs

> a blog posts similar to I can do another emoji heavy entry if no one wants to take a stab at it. > 2.21.0 will be the next 'major'...

*polite poke* for review to see if this is on the right track.

See also #7654

>for users using execution environments with multiple, independent workers like remote execution where process invocations may end up on workers without the append-only cache filled with the third-party module sources....

Possibly related: #10078

This is rather far out of my familiarity zone, but: * "streaming pytest output" has come up internally and I think if I'm reading this right this would help with...

> this involves updating many tools, as a Big Bang, which is potentially unhelpful. In that it pulls in more updates than are strictly needed just for 3.12 compatibility?

In the python example. ``` pants --keep-sandboxes=always --print-stacktrace generate-lockfiles --resolve=python-default Pantsd has been turned off via Env. 20:44:07.50 [INFO] Preserving local process execution dir /tmp/pants-sandbox-fb5WgH for Generate lockfile for python-default...

Feedback Requests: * This takes a fairly thin approach. I suspect trying to do anything heavily abstract over pants-->pex-->pip is going to be all sorts of leaky. I made this...

Thanks for the background and context. That makes sense. I think the design question remains: If the metadata/config in pants has changed such that doing one of these `updates` is...