Use pipenv with internal nexus pypi mirror

[smutel]

Hello,

I tried to find the information between several discussions and issues in this repo but I did'nt find a clear answer so I ask it here.

Is-it possible to use internal pypi repo with pipenv ?
I tried several configurations and it seems that pipenv is always looking to pypi.org.

Thanks.

[matteius]

Hi @smutel The first index specified in your Pipfile will be the default. There are some new documentation updates in master that will be published when there is a new release soon, but basically if you omit PyPI or remove it from your Pipfile and specify your private pypi repo as the first source within the Pipfile, all unspecified packages will use that index by default.

EDIT: version 2022.4.8 works for this case because it is more strict about determining if an index is in-fact pypi.

[smutel]

Even with this configuration, I have this error message:

pipenv.vendor.urllib3.exceptions.ConnectTimeoutError: (<pipenv.vendor.urllib3.connection.HTTPSConnection object at 0x7f27eec389d0>, 'Connection to pypi.org timed out. (connect timeout=10)')

which indicate that pipenv is looking at pypi.org anyway ...

[matteius]

@smutel It is because pypi.org is in your URL for the sources, so it thinks you are in fact trying to reach pypi.org I suspect.

[matteius]

@smutel There is a chance that version 2022.4.8 will work better for your case, a chance because it happens I refactored this bit here: https://github.com/pypa/pipenv/pull/5029/files#diff-62e85156fc3b274046cc03dabfe6e3ceead503f330b98fb3611645216b4b6e1fL747-R747

It looks like the new utility is more strict on how it matches if its truly pypi.org.

[smutel]

It works fine with the last version. Thanks.

[kalebmckale]

There have been a number of updates including interfacing with the indexes in the pip.conf file and adding them to Pipfile that now better handles your scenario.