#18955 2.17.0: `.python-build-standalone` symlink causes cross-pants-version testing issues Issue created by tgolsson Describe the bug This is a very specific edge-case of how I run tests, but I wanted to bring it up because it seems like an uncaught edge-case that maybe shouldn't be happening. I run a matrix of tests for my backends; one axis being "host" pants (

PANTS_VERSION

) and one axis being "pants target" (

pants_requirements

). This has worked fine for the versions I've been testing before; but after adding 2.17.0.dev4 this testing approach is no longer compatible. In particular;

.pants-build-standalone

is breaking testing of old

pants_requirements

with a 2.17.0.dev4 host. My understanding is that the inner pants (e.g. 2.15.0) is running in a sandbox; and the host pants adds the symlink when launching the test. This is fixable by locally adding

pants-ignore

like @thejcannon added in 61d57d8, but I'm not sure if this is intended behavior of the test setup if you can see the "host" pants from inside the test. Pants version 2.17.0dev4 OS Only tested Linux. Additional info Full thread that prompted discovering this: https://pantsbuild.slack.com/archives/C01CQHVDMMW/p1683292836600399. pantsbuild/pants