Skip to content
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

Investigate new method of determining Poetry development dependencies #996

Open
cobya opened this issue Feb 1, 2024 · 0 comments
Open
Labels
detector:poetry The poetry detector status:requirements Full requirements are not yet known, so implementation should not be started type:feature Feature (new functionality)

Comments

@cobya
Copy link
Contributor

cobya commented Feb 1, 2024

With #991 it came to our attention that with the more recent Poetry lock file changes (see https://github.com/python-poetry/poetry/blob/master/CHANGELOG.md#150---2023-05-19) the category field is no longer present.

This was being used to determine whether a dependency was used in the main package or as a development only dependency. Investigate a new method of determining which dependencies are used for development only as the detector will now be overreporting.

@cobya cobya added detector:poetry The poetry detector status:requirements Full requirements are not yet known, so implementation should not be started type:feature Feature (new functionality) labels Feb 1, 2024
@cobya cobya added status:in-progress Someone is working on implementation status:requirements Full requirements are not yet known, so implementation should not be started and removed status:requirements Full requirements are not yet known, so implementation should not be started status:in-progress Someone is working on implementation labels May 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
detector:poetry The poetry detector status:requirements Full requirements are not yet known, so implementation should not be started type:feature Feature (new functionality)
Projects
Development

No branches or pull requests

1 participant