You could try adding -v as an argument to rustpython, e.g target/release/rustpython -v get-pip.py. That should at least tell you what the last thing that gets imported is, and you can add more v's to get more verbose logs.

Thanks.

I did some manual debugging with more verbosity to figure out where rustpython hangs

...
DEBUG: Running bootstrap...
DEBUG: monkeypatch_for_cert
DEBUG: from pip._internal.commands.install import InstallCommand
# trying /home/ryuta/packages/rustpython/rustpython/vm/pylib-crate/Lib/encodings/ascii.py
# /home/ryuta/packages/rustpython/rustpython/vm/pylib-crate/Lib/encodings/__pycache__/ascii.rustpython-01.pyc matches /home/ryuta/packages/rustpython/rustpython/vm/pylib-crate/Lib/encodings/ascii.py
# code object from '/home/ryuta/packages/rustpython/rustpython/vm/pylib-crate/Lib/encodings/__pycache__/ascii.rustpython-01.pyc'
import 'encodings.ascii' # <SourceFileLoader object at 0x55f9ca455110>

What's puzzling is that rustpython -c "import encodings.ascii" has no issue at all.

Does cargo run --features ssl --release -- -v --install-pip work or give the same error? That's what we run in CI to make sure pip can install, though manually running the get-pip.py shouldn't be any different.

Hmm. cargo run --features ssl --release -- -v --install-pip works perfectly fine.

Weird...

For now --install-pip works, so no big deal. I'll come back and try to figure out what's going on.

Also ref: #3097

Can we close these issues or is the hanging still triggered in some way?

Closing as get-pip.py (or --install-pip) works on Linux.
For Windows, see #2671.