Add support for excluding dev dependencies for poetry >= 1.5.1 #252
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
koraytugay
changed the title
|
Please review when time permits. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
package.categorysection was removed in: https://github.com/python-poetry/poetry/pull/7637/filesThis means the current implementation in https://github.com/sonatype-nexus-community/vscode-iq-plugin/blob/main/ext-src/packages/poetry/PoetryUtils.ts#L33 will not filter dev dependencies anymore.
This PR introduces a way to filter out dev dependencies by reading the production dependencies from
pyproject.tomlfile (if it exists) and resolving the transitive dependency of the production dependencies frompoetry.lock.I am attaching test files that can be used to manually test the new functionality. testfiles.tar.gz
cc @bhamail / @DarthHater