https://bugzilla.redhat.com/show_bug.cgi?id=1914450 code@xxxxxxxxxxxxxxxxxx changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |code@xxxxxxxxxxxxxxxxxx --- Comment #3 from code@xxxxxxxxxxxxxxxxxx --- I think that line is a bit misleading. The full README says: They work for: traditional Setuptools-based projects that use the setup.py file, newer Setuptools-based projects that have a setup.cfg file, general Python projects that use the PEP 517 pyproject.toml file (which allows using any build system, such as setuptools, flit or poetry). They certainly work well enough for a traditional project with setup.py. The generated BR’s are especially nice. Using them is not currently mandatory, but I’ve also been trying to encourage open-minded maintainers to try them in new packages. Since this is a nice, simple project, I’m attaching a working example of making full use of the pyproject-rpm-macros. I haven’t attempted to review the package for any other issues when modifying the spec file. However, I’m happy to do the actual review once you decide what you want to do. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-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/package-review@xxxxxxxxxxxxxxxxxxxxxxx
