I've managed to build tldr package with the new macros during the hackfest session of Flock. I had to create a pyproject.toml file to specify package's build dependencies to make it work and now I'd like to send it to upstream. Therefore it would be handy to have some short user-friendly documentation about pyproject.toml files, how to use them, how they can help you etc. so an upstream maintainer can read something about it.
I'm confused. Do you except Fedora to create and maintain the docs for (upstream) pyproject.toml? This is the official reference point: https://www.python.org/dev/peps/pep-0517/ https://www.python.org/dev/peps/pep-0518/ (However I realize it has a lot of "under the hood" details.) BTW for tldr, was pyproject.toml needed to make %pyproject macros work? The macros should fallback to setuptools.
(In reply to Miro Hrončok from comment #1) > I'm confused. Do you except Fedora to create and maintain the docs for > (upstream) pyproject.toml? > > This is the official reference point: > > https://www.python.org/dev/peps/pep-0517/ > https://www.python.org/dev/peps/pep-0518/ > > (However I realize it has a lot of "under the hood" details.) Yes, PEPs are there but you don't want to submit a PR like "Hey, this is a new pyproject.toml for your project and if you want to know why read the whole PEPs." So I was thinking about some documentation of pyproject-rpm-macros which would contain steps to create a new pyptoject.toml from setup.py, some examples of pyproject.toml files and maybe some justification for upstream developers which you can use with every new PR. Maintaining pyproject.toml downstream does not make any sense so I'd put some effort to promote it in upstream, and porting packages to the new macros might be a good start how Fedora package maintainers can do that. > BTW for tldr, was pyproject.toml needed to make %pyproject macros work? The > macros should fallback to setuptools. Yes it is needed because tldr uses setuptools-scm in its setup.py file.
(In reply to Lumír Balhar from comment #2) > So I was thinking about some documentation of pyproject-rpm-macros which > would contain steps to create a new pyptoject.toml from setup.py, some > examples of pyproject.toml files and maybe some justification for upstream > developers which you can use with every new PR. Maintaining pyproject.toml > downstream does not make any sense so I'd put some effort to promote it in > upstream, and porting packages to the new macros might be a good start how > Fedora package maintainers can do that. We can definitively aim to write something, but I am not convinced it should be part of the documentation of pyproject-rpm-macros.
I think we should document how to package Python modules to make them friendly for distributions, and how to package such modules in Fedora. But not *right* now: at this point it would IMO be mostly documenting bugs and missing pieces that we're fixing and adding :)
Lumír, let's talk about this one more.
Random link on topic: https://snarky.ca/what-the-heck-is-pyproject-toml/
This isn't likely to ever have enough priority to get done. No need to track it here.