-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"ERROR: No matching distribution found" in updating Pipfile.lock in installing a package from private Package Repository of GitLab.com #5021
Comments
I have narrowed down the bug: It happened sometime after the "2022.1.8" version of Pipenv. You can get a working, older version of Pipenv like this:
|
There's a long ticket where we discovered the same bug here: PyTorch can't be installed from a PEP-503 repo anymore with the latest Pipenv. The 2022.1.8 vversion works. I have not checked all of the March 2022 releases but I know for a fact that Pipenv 2022.3.28 is broken. |
I am wondering if you are falling into an edge case of the index restriction fixes. #4983 Could you try naming the non pypi index and calling out the name on the line that requires it? For @masato-yasuda that would look like:
|
@matteius Confirmed. That is the problem. Results are over at: |
@matteius
Result (No Error)
@Bananaman |
I have spent some time debugging this tonight. Here is what I have found; 1.) It works to specify on the CLI by index such as 2.) The problem with passing in ---extra-index-url is that it basically assumes you mean that the default --index is pypi. 3.) Pip itself says about --extra-index-url that it is used to "Search an additional index during install, in addition to PyPI"
4.) Hash generation was broken with package restrictions in place for some scenarios and so I have a new PR out to fi that. In conclusion tonight, my current analysis is that we should perhaps remove the If you have thoughts further on this issue would love to hear them because we will want to make a decision on this for the April release. |
@matteius |
@masato-yasuda No this seems to work fine, since in the example of torch repositories, the are in a private repository and pull in other dependencies from pypi. Here is a sample Pipfile.lock I generated:
|
@matteius |
Hi everyone, @matteius we seem to be having a similar issue. In our case, one of our private packages has a dependent package also in our private repo. It works fine with v2022.1.8, but failing with v2022.5.2.
This fails to find a matching distribution for one of the dependencies of Thanks in advance |
@juanitosvq You have at least a couple options without any further pipenv development to get this scenario working, though perhaps you could propose imporvements to the docs as well. I've added some improvements already to https://pipenv.pypa.io/en/latest/advanced/#specifying-package-indexes 1.) You can try swapping the order of your source definitions so that "repo.io" comes first. This makes that one the default index for not specified packages. This may require that you have mirrored your pypi packages to the private server, while best practice, may not always be possible. I hope this helps! |
When we try to install a private package from our Package Repository of GitLab.com, we got the following error.
(It worked in v2022.1.18. However, we got this error in v2022.3.23 and v2022.3.24.)
My Pipfile is the following.
My Pipfile.lock is the following.
Our package "mypackage20220329" is uploaded at GitLab.com.
We prepared the package by following the instruction at https://docs.gitlab.com/ee/user/packages/pypi_repository/ .
Note: We can't reproduce the error if the package name is "mypypipackage". It's because "mypypipackage" is already on pypi.
Therefore, we suspect that this error is caused by search at the wrong location in checking the existence of "mypackage20220329".
The text was updated successfully, but these errors were encountered: