serverless/serverless-python-requirements

Please Add Support for PEP 631

jax-b opened this issue · 0 comments

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.