Package in private repo with same name as one from Pypi

I have a package in a private repository with the same name as one from PyPi. The PyPi one, having a higher version number, always get installed.

[[source]]
url = "https://pypi.myrepo.com.br/pypi"
verify_ssl = true
name = "myrepo"

[[source]]
url = "https://pypi.python.org/simple"
verify_ssl = true
name = "pypi"

[packages]
mypkg = ">=0.0.1"

[requires]
python_version = "3.6"

Is there a way to define that a package comes from a certain private repo?

[seglberg]

This seems to be the same/similar issue I raised in #2102. Personally I think the current syntax is confusing because when I specify mypkg = {version: ">=0.0.1", index="myrepo"} I logically expect it to use myrepo only and disregard pypi.

I totally understand the behavior was changed to match --extra-index-url, but there is a big enough disconnect between pip and pipenv (in my mind) that I expected different behavior. I was excited at the idea of better and more simplified controls over where and how packages are downloaded for our projects.

[prcastro]

I would find more intuitive to always search in the source order defined in the Pipfile, unless a specific index is specified on the dependency.

In my case mypkg = {version: ">=0.0.1", index="myrepo"} would only search in myrepo while mypkg = ">=0.0.1" would search first in myrepo and then in pypi, getting the newest version, since this is the source order defined on the Pipfile.

However, maybe one would like to change the source order in a per-dependency basis. Then, one could add an extra_index key, so mypkg = {version: ">=0.0.1", index="pypi", extra_index="myrepo"} would search first on pypi and then on myrepo.