-
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
poetry 1.1.4 locks all packages to be pulled from secondary repo #3306
Comments
# Always put PyPI last to prefer private repositories
# but only if we have no other default source
if not poetry.pool.has_default():
has_sources = bool(sources)
poetry.pool.add_repository(PyPiRepository(), not has_sources, has_sources)
else:
if io.is_debug():
io.write_line("Deactivating the PyPI repository") It seems there's missing logic about secondary repos here, sth like |
Also affected by this. |
Also experiencing the same issue. I have fixed it on my own and was going to open a pull request but it seems it was already done :) A quick workaround is to redefine the Pypi repository but it's kind of ugly as it add an entry "package.source" in the lock file for every package coming from Pypi.
|
I tried it with 1.1.5 but my lock ran for more than 5 minutes. I guess this is not yet resolved |
@sinoroc I can confirm that this is still affecting poetry 1.1.5. Here's a simple
And the resulting
|
Is there any workaround for this?? |
@progmatic-99 update Poetry as it's already fixed for months? |
Sorry, noob mistake @jaklan |
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. |
I am on the latest Poetry version.
I have searched the issues of this repo and believe that this is not a duplicate.
If an exception occurs when executing a command, I executed it again in debug mode (
-vvv
option).OS version and name: macOS 10.14
Poetry version: 1.1.4
Issue
Hi,
I'm experiencing this behavior on 1.1.4. In
pyproject.toml
I have configured a secondary repo:As such, I expect that
poetry
will fetch most packages from the main PyPI. And 1.1.3 indeed does that. However, 1.1.4 adds this configuration to every package (non-private as well) inpoetry.lock
:IMO this is unexpected behavior. I did
git bisect
and found out that this bug was introduced in 74fc8eb, in an attempt to fix other pypi-related issues.The text was updated successfully, but these errors were encountered: