On 19. 08. 21 15:45, Miro Hrončok wrote:
On 19. 08. 21 10:25, Elliott Sales de Andrade wrote:
It seems that pip may be changing to in-tree builds?
https://github.com/pypa/pip/issues/7555
Are we moving towards that as well? It seems like that would make it
simpler to build the docs for cases
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
On 19. 08. 21 10:25, Elliott Sales de Andrade wrote:
It seems that pip may be changing to in-tree builds?
https://github.com/pypa/pip/issues/7555
Are we moving towards that as well? It seems like that would make it
simpler to build the docs for cases like this.
Eventually yes.
--
Miro Hrončok
On Wed, 18 Aug 2021 at 19:51, Miro Hrončok wrote:
>
> On 18. 08. 21 11:09, Elliott Sales de Andrade wrote:
> > I've been experimenting with the new macros for Python packages, and
> > ran into some issues building Sphinx docs for compiled extensions.
> >
> > When building docs, one usually has to
On 18. 08. 21 11:09, Elliott Sales de Andrade wrote:
I've been experimenting with the new macros for Python packages, and
ran into some issues building Sphinx docs for compiled extensions.
When building docs, one usually has to be able to import the project.
When the project uses compiled
I've been experimenting with the new macros for Python packages, and
ran into some issues building Sphinx docs for compiled extensions.
When building docs, one usually has to be able to import the project.
When the project uses compiled extensions, it is not sufficient to
point to the original
