pip change to pypi.org

[Niccolum]

Hello!

I'm continuing to debug pants with a closed network.

Honestly, I'm almost there, just a little bit more to go.

Now I'm trying to run the pants package with blocked pypi.org.

My /etc/hosts looks like this:

127.0.0.1 files.pythonhosted.org
::1 files.pythonhosted.org

127.0.0.1 pypi.org
::1 pypi.org

When running it locally, whether using pants generate-lockfiles (to install setuptools in the internal loop via install_from_resolve) or using pants package my_lib::, I get the error - https://gist.github.com/Niccolum/9166980b6c60dc06f1b3b78641bf6e15

Can you tell me what I'm doing wrong?

P.S. Everything works fine without blocking pypi.org

UPD: pants.toml - https://gist.github.com/Niccolum/003aad1011ece876f9ebd912915710ea

[benjyw]

Presumably whatever https server you're running on localhost does not have a valid cert for pypi.org...

[Niccolum]

I'm trying to get pants to work without access to pypi.org. I explicitly blocked it in /etc/hosts to test it. But it's not working yet, and I want to figure out what I need to do to make it work.

I have private repository and i don't know how to use it for pip itself

[benjyw]

Ah I see, it looked like you were trying to redirect traffic bound to pypi to a server running on localhost, but you're saying you are just treating 127.0.0.1 as a block (so presumably you have no server there on port 443).

[benjyw]

Can you run Pants with --keep-sandboxes=on_failure, which will print out the location of the sandbox, and then post the contents of __run.sh in that sandbox.

[benjyw]

Let's wait for the Pex maintainer to weigh in, just to be sure I am correctly understanding the problem. But basically if/when Pex fixes this, you can upgrade the version of Pex that Pants uses without upgrading Pants itself (and of course we will upgrade the default version of Pex for future versions of Pants).

[benjyw]

Since it's coming up on the holiday season this may take some time, so we appreciate your patience.

[Niccolum]

Thank you, I'm actually pleasantly surprised that despite it being open source, you're very responsive and really help solve the problem.

[jsirois]

Believe me, Pants is not really responsive, but Pex is. I'll have a fix out ~12/17 as noted in the other issue.

[jsirois]

Alrighty, that took way longer than I like, but the fix is available in Pex 2.76.1: https://github.com/pex-tool/pex/releases/tag/v2.76.1
You can upgrade whatever Pants version your using by adding the following to pants.toml

[pex-cli]
version = "v2.76.1"
known_versions = [
  "v2.76.1|macos_x86_64|57192b7cf4a870c8f2d6fd1fe8125fb02ca6a02c83328c6291debb54fc5cb3a2|4941852",
  "v2.76.1|macos_arm64|57192b7cf4a870c8f2d6fd1fe8125fb02ca6a02c83328c6291debb54fc5cb3a2|4941852",
  "v2.76.1|linux_x86_64|57192b7cf4a870c8f2d6fd1fe8125fb02ca6a02c83328c6291debb54fc5cb3a2|4941852",
  "v2.76.1|linux_arm64|57192b7cf4a870c8f2d6fd1fe8125fb02ca6a02c83328c6291debb54fc5cb3a2|4941852"
]