python-poetry
Support reading metadata from PEP 621 compliant pyproject.toml
Flit-core uses a dependencies block to determine requirements.
https://flit.pypa.io/en/stable/pyproject_toml.html?highlight=dependencies#dependencies
But if you look at utils/setup_reader.py -> read_setup_cfg() it only checks for "python_requires", "install_requires...etc"
Could we add support for other backends?
Also it looks like it's only able to get the requirements from setup.py or setup.cfg, why doesn't it read pyproject.toml?
Why can't poetry grab the info for the package from pyproject.toml? Why is it only gathering this data from setup.py or setup.cfg?
duplicate #3332, please close
edit: I see from your pull request that you are aiming at a very specific use case - so this isn't a duplicate after all. I'll make some comments over there.
I've edited the title of this ticket, because it was misleading. Poetry is able to gather metadata from flit and other, as long as they are PEP 518 compliant. Until now setup.py was a first class citizen, to avoid unnecessary builds to get the final metadata. For all other build-backend Poetry falls back to build the wheel file to have access to metadata it needs.
The lack of support for the standard pyproject.toml format breaks the usage of zest.releaser in Poetry projects. The library looks for the [project] section on the pyproject.toml file as specified by PEP 621 to determine the project's version number. While Poetry expects this attribute, as well as name, to be under [tool.poetry].
@maribedran support for PEP 621 in Poetry was recently merged. This issue concerns reading package metadata from editable projects included in your Poetry projects.
This is not completed
it kind of is though, since setup_reader doesn't exist any more
ie the whole approach is now abandoned, so feature requests asking for it to be enhanced are unlikely to happen