Comment on #22916 Installing pants behind a firewall Discussion answered by Niccolum Thanks for the quick replies and help. I, in turn, figured out how to work with all this at the same time, so I'll write about each point: 1. At first, I didn't realize that the scie-pants release is a binary and can be run immediately after downloading it. I thought I needed to install it somehow. But no – I just downloaded it and it worked. 2. I specified cpython-3.9.23+20250612 and cpython-3.11.13+20250612 in PANTS_BOOTSTRAP_URLS. Different ones for different OS and architectures (8 links in total), and it started working just fine. 3. I didn't find a way to do this, but in principle, this isn't a problem if we use PANTS_BOOTSTRAP_URLS, where we can specify all the necessary Pythons. The only thing is, it's all hardcoded, but I can live with that. What I'd like to clarify: 1. Why was PANTS_BOOTSTRAP_URLS invented? What do you think about creating some kind of url_template in pants.toml for Python and pants.pex, respectively? Or alternative [bootstrap].urls in pants.toml? 2. I don't quite understand why pants needs both Python 3.9 and 3.11, and not just 3.11? I downloaded the latest pants 2.29.1, compiled for 3.11 pantsbuild/pants