-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Dependency resolution problem with non-pypi repository #706
Comments
Here's the
|
Is there a way to make private repositories behave like |
Hi, we're getting this same issue with a private repo. @ojii Did you find a workaround?
|
@AzMoo sadly my "workaround" for now is "not use poetry in projects that have non-pypi dependencies". |
Any news on this? Is there a good argument not to use |
Any update on this. I just spend quite some time on migrating the whole project to poetry and now i am stuck at this point. |
I've actually thought about a good reason not to use Maybe a better solution would be something like: [tool.poetry.dependencies]
privpkg = { version = "^2.13.0", repo = "privaterepo" } Though this raises the question how private and public dependencies of |
My Problem is rather that I cannot install any private packages that I would install with pip like this: Even those that don't have any dependencies. |
@ojii I think this is fixed in the latest |
Also can you test the |
I think I have the 0.12.11 release. But I will check it out tomorrow and come back to you. I will also test the prerelease. |
It almost works. The problem I'm facing now is that it tries the private repo first, then the public one. Since our private repo is not a perfect mirror of pypi but rather a place where we upload our packages, some things have trouble installing (in my case Also, I had to run
Again the old pip screwed me over at first. (I really wished poetry updated pip after creating a venv) and then the same issue, it failed to get a wheel of |
I am currently using the 0.12.11 release. There it is not working. I've updated to the prerelease you've mentioned and i get the same error message as before. When I install a public package from my own index-repository it works like a charm, when installing something last is private it can't find it anymore. (I've tested the URL through normal pip and pipenv and it works there). Here is my traceback in a minimal configuration:
|
I just figured out that even with --index-url=<private_repo> the normal pip install works, if I installed all the other dependencies manually. For some reasons poetry is still not able to find the package though. My private repository is hosted on gemfury if that helps at all. |
[EDIT] forgot to include pyproject.toml. now added below @sdispater I ran into this issue today with a local devpi instance. I tried with poetry versions 0.12.11, 0.12.15, and 1.0.0a2. In each instance, when I tried to add my local package, poetry reports that it could not find the package. When searching for the package, it was not found either. I jumped into the underlying virtual environment and tried using pip to install the package which seemed to work fine. I'm able to publish to the local devpi repo using poetry without issue. Here is some example output:
|
@sdispater Once I ammended my pyproject.toml file accordingly, it worked great. Thanks again for the great tool! working pyproject.toml:
|
@sdispater Not exactly the same issue; but I was having a similar error in a project that depends on a private github repo and 1.0.0a3 fixed that. |
@sdispater I'm sorry but we simply stopped using private packages as our "solution" to this so I no longer have an easy setup to test this. Looking at the PR though that looks like a good solution. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Version: Poetry 0.12.10
I have a private PyPI server for company internal packages. Something in poetry seems to get confused when that private package has public dependencies. Specifically this case:
private-package
depends onpublic-package
which itself has further (public) dependencies.poetry add private-package
poetry add public-package
fails with[PackageNotFound]: Package [<private-package>] not found.
However
poetry add
works for public packages not depended on byprivate-package
and also works for public packages which have no dependencies on their own, even if depended on byprivate-package
.The text was updated successfully, but these errors were encountered: