So, we have: •

python_requirements

for

requirements.txt

-style files •

pipenv_requirements

for

Pipenv.lock

•

poetry_requirements

for

pyprojec.toml

where the requirements are under

[tool.poetry.dependencies]

(and similar) I just noticed that we can also define dependencies in

pyproject.toml

under

[project].dependencies

https://packaging.python.org/en/latest/specifications/declaring-project-metadata/#dependencies-optional-dependencies Has anyone looked at writing a target that allows pants to consume those deps? Maybe

pyproject_requirements

? Or

pyproject_dependencies

? Also, I wonder if we could have a

python_project

to complement

python_artifact

but pull details from pyproject.toml instead of specifying in the BUILD file.

Also, I wonder if we could have a python_project to complement python_artifact but pull details from pyproject.toml instead of specifying in the BUILD file.

That could be interesting. Benjy knows wayyyyy more about this all than me, but we wrote the packing stuff before PEP 517 was really a big thing, back in v1. Then ported it to v2 outside of https://blog.pantsbuild.org/pants-supports-pep-517/

There's some more in a related thread: https://pantsbuild.slack.com/archives/C046T6T9U/p1658271452464949?thread_ts=1658267186.962979&cid=C046T6T9U