Python poetry#4016 #4445
Closed
Python poetry#4016 #4445
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…-of-missing-extras Fix resolution of packages with missing required extras
Fixes python-poetry#3026 If the context wrapped by the temporary_directory() context manager raised ImportError (for example because distutils.util cannot be imported, python-poetry#721 python-poetry#1837), it would previously keep going, causing a RuntimeError from contextlib: RuntimeError: generator didn't stop after throw() Co-authored-by: Remi Rampin <[email protected]>
This change ensures that we create closer to reality scenarios when testing init command. Relates-to: python-poetry#3073
This change ensures that we resolve dependencies to correctly propagate markers when using `lock --no-update`. Resolves: python-poetry#3048
This change ensures that package inspection will handle rich core metadata available for poetry managed projects. This will allow, nested local path dependencies to use "develop" mode packages. Resolves: python-poetry#3098
Resolves: python-poetry#3084 Co-authored-by: Etty <[email protected]>
This change, moves common functionality from exporter into the locker to allow for sharing of logic that can generate `DependencyPackage` instances given a a list of requirements using the lock data.
This change ensures that markers are propagated from top level dependencies to the deepest level by walking top to bottom instead of iterating over all available packages. In addition, we also compress any dependencies with the same name and constraint to provide a more concise representation. Resolves: python-poetry#3112 #3160
Previously, when determining nested dependencies, the check for activated extras/features of top level dependencies were done after the nested dependencies were processed. This lead to exports containing in active extras. This change resolves this by pre-selecting top level packages prior to identifying nested dependencies.
Add PyPI registry correctly to pool depending on other sources (python-poetry#3406) In the event where we defined sources that were set as secondary = True, we would end up with PyPI being after this source when it should have acted as default in that case. The main issue stems from the fact that it's not because you have sources configured that PyPI should not be a default. Instead, PyPI should be default if there are no sources with secondary = False and not default if there are sources with secondary = True.
Co-authored-by: Sébastien Eustace <[email protected]>
Co-authored-by: Sébastien Eustace <[email protected]>
Co-authored-by: Sébastien Eustace <[email protected]>
Co-authored-by: Sébastien Eustace <[email protected]>
Co-authored-by: Sébastien Eustace <[email protected]>
…get-poetry add deprecation warning for `get-poetry.py` to docs
…nv-detection-1.1 [1.1] Fix system environment detection
fix: create path dependencies relative to package rather than lockfile (python-poetry#4245)
…tive-paths-dependencies-locking [1.1] fix: create path dependencies relative to package rather than lockfile
…er-environment-for-python-3-10 [1.1] Fixed python_version for Python >= 3.10
…em-env-detection [1.1] Fix system env detection
…ive-hash-generation [1.1] Fix archive hash generation
…matically closed once we're done in the legacy repository
…n't pass any retry options, doing so fixes the [WinError 10048] Only one usage of each socket address (protocol/network address/port) is normally permitted')) error on Windows
|
Sorry, this needs to be merged to branch 1.1, not master |
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request Check List
Resolves: #4016
I'm experiencing the same issue on poetry 1.1.8 but I have created this patch to solve this issue. The problem is that by default, the requests library doesn't retry when a connection fails, and CacheControlAdapter also doesn't pass any retry parameters.
In our case this issue only arises on Windows, not on Linux, but as most developers work on Windows machines, we needed to fix this issue. We didn't experience this issue with poetry 1.0.10 though.