one pip knows about a private repo, it appears to always check it when installing any package, including ones not expected to be in a private repo. So if you're off VPN, pipenv quietly times out retrying a repo it can't reach & takes a million years.
`pipenv install --dev --skip-lock --verbose`
will tell you what package it is hung up on, but it won't tell you that it is trying to reach a private repo whilst off VPN.
To find out that, you have to run `pip install {some package}`♡ 0 ↻ 0