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

Please Add Support for PEP 631 #819

Open
1 task done
jax-b opened this issue Feb 10, 2024 · 0 comments
Open
1 task done

Please Add Support for PEP 631 #819

jax-b opened this issue Feb 10, 2024 · 0 comments

Comments

@jax-b
Copy link
Contributor

jax-b commented Feb 10, 2024

Is there an existing issue for this?

  • I have searched existing issues, it hasn't been reported yet

Use case description

Currently PEP 631 defines using the dependencies section under project for pyproject.toml as a vendor agnostic way of defining requirements. I have started to use this instead of a requirements.toml

Proposed solution (optional)

Update naming on existing poetry code, Add Parsing in to convert pyproject.toml > project > dependencies.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant