Hi there
Even after reading our packaging doc I'm wondering what's the proper
way to handle sphinx doc autogenerated from built sources.
The issue is that %build is the section where all building should be
done, followed by %install and %check. Building the documentation
(e.g. using sphinx autodoc) is clearly a build step, but often
requires the build products, and often *installed* build products.
[I came across an upstream which even calls "pip install" from
sphinx's docs/conf.py ... ]
So, what do you guys do? Build docs in %install and point py/sphinx to
the installed sources? Build docs after the wheel and point py to
%{pyproject_whichone_please}? I somehow cannot find a solution without
failed imports being reported by sphinx.
[Yes, partly py-specific, but not totally.]
Michael
--
_______________________________________________
devel mailing list -- [email protected]
To unsubscribe send an email to [email protected]
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/[email protected]
Do not reply to spam, report it:
https://forge.fedoraproject.org/infra/tickets/issues/new
