Re: Building docs of compiled extensions with new macros
I have also resorted to manually installing the wheel to a temporary directory in %build, then setting PYTHONPATH to include the temporary directory to build the documentation. I don’t like this solution very well either, but it is a third alternative that seems to work well. See https://src.fedoraproject.org/rpms/python-asyncpg/blob/ca0bedc42ddba790ffda74cbaa48a06daf7d141e/f/python-asyncpg.spec#_103 for an example. ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-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/python-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: An unsuccessful case study: Using pyproject-rpm-macros with PyQt-builder and sip 5
If by “are using PEP-517 build systems” you just mean those that use pyproject-rpm-macros in their spec files, I can also offer python-asyncpg and python-pyrsistent as examples. If you mean that upstream does not use setuptools in setup.py, but instead uses flit or poetry via pyproject.toml, then python-pendulum, which uses poetry, may be the only example right now. ___ python-devel mailing list -- python-devel@lists.fedoraproject.org To unsubscribe send an email to python-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/python-devel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
