Aoife Moloney venit, vidit, dixit 2025-06-07 14:49:21: > Wiki - https://fedoraproject.org/wiki/Changes/DeprecateSetuppyMacros > Discussion thread - > https://discussion.fedoraproject.org/t/f43-change-proposal-deprecate-rpm-macros-for-setup-py-based-python-builds-self-contained/155251 >
The discussion in the devel thread teaches us that conversion is simple: complain to Miro and he will reply with a PR ;-) More seriously: > Minimal migration example: > > Old: > > BuildRequires: python3-devel > BuildRequires: python3-setuptools > ... > > %build > %py3_build > > %install > %py3_install > > New: > > BuildRequires: python3-devel > ... > > %generate_buildrequires > %pyproject_buildrequires > > %build > %pyproject_wheel > > %install > %pyproject_install > > There are more macros and options you can use. > See the current > [https://docs.fedoraproject.org/en-US/packaging-guidelines/Python/ > Python packaging guidelines] for more information. This example and most that I know use a BR on python3-devel and %pyproject_buildrequires, whereas the guidelines tell you to use *one* of them. The result with both is the same as with just the macro, but the path there is different: in the latter case the macro installs python3-devel. I don't mind either way, but maybe we should decide on a "best practice" and have the guidelines and examples match. Cheers Michael -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
