Skip to content

Please Add Support for PEP 631 #819

@jax-b

Description

@jax-b

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions