On 06. 09. 22 16:52, Michael J Gruber wrote:
On Mon, Sep 5, 2022 at 2:01 PM Sandro <lists(a)penguinpee.nl> wrote:
pyproject does not work well, and is not backwards compatible. This is
particularly a problem for EPEL ports from Fedora. Personally, I'd
like to see it fixed for EPEL before relying on it for anything in
Fedora.
The current py packaging guidelines recommend the opt-in dependency generator (which uses pyproject.toml) unless EPEL 8 or non-current Fedoras are used. Should this caveat be extended to F36 and EPEL 9, or am I mis-understanding the role of pyproject.toml for the packaging macros?
This is explicitly about project metadata (name, version, etc.) in
pyproject.toml a new feature of setuptools.
The macros use pyproject.toml for different purpose and don't need this feature
unless upstream uses it.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
