Re: [PyCUDA] Problems building PyCUDA documentation

[Andreas Kloeckner]

Tomasz Rybak  writes:
> Would you apply this patch in repository??
> Debian has policy that python means Python 3, and python3 is for Python 3 
> interpreter.
> If not - that's not a problem, now it is automatically applied during 
> building of Debian packages.

Done.

Andreas

___
PyCUDA mailing list
PyCUDA@tiker.net
https://lists.tiker.net/listinfo/pycuda

Re: [PyCUDA] Problems building PyCUDA documentation

[Tomasz Rybak]

Dnia 2016-07-01 16:02 Andreas Kloeckner napisał(a):

>Tomasz Rybak  writes:
>> I was trying to rebuild PyCUDA 2016.1.1 (as tagged on GitHub) package 
using 
>> CUDA 7.5 and Sphinx 1.4.4.
>> There was warning regarding http to https redirect on documen.tician.de, 
>> patch below:
>> Index: pycuda-2016.1.1/doc/source/conf.py
>> ===
>> --- pycuda-2016.1.1.orig/doc/source/conf.py
>> +++ pycuda-2016.1.1/doc/source/conf.py
>> @@ -187,5 +187,5 @@ latex_documents = [
>>  intersphinx_mapping = {
>>  'http://docs.python.org/dev': None,
>>  'http://docs.scipy.org/doc/numpy/': None,
>> -'http://documen.tician.de/codepy/': None,
>> +'https://documen.tician.de/codepy/': None,
>>  }
>
>Thanks for the patch, I've applied that.
>
>> This is caused by doc/source/conf.py, html_theme_options, which contains 
>> Unicode characters for floppy and rocket. I did not have any problems 
with 
>> PyOpenCL, probably because 2016.1 does not contain those glyphs.
>>
>> Andreas - how have you built documentation for your web page? Is there 
some 
>> special option for Sphinx I should use?
>
>Regarding the Sphinx build problem: I can reproduce this on Python 2,
>but I've been using Python 3, where the issue does not occur. I'm not
>entirely sure what the issue is--the traceback is somewhere deep in the
>weeds.
>

Thanks, building with Python 3 was exactly what was needed.
I changed doc/Makefile to use python3 instead of python: 
https://anonscm.debian.org/cgit/collab-maint/python-pycuda.git/tree/debian/patches/sphinx.patch?id=9b0962ca4e0c4ebd6e42415a5ffcb19b744fe02d

and now package builds without problems.

Would you apply this patch in repository??
Debian has policy that python means Python 3, and python3 is for Python 3 
interpreter.
If not - that's not a problem, now it is automatically applied during 
building of Debian packages.

Best regards.
Tomas Rybak
___
PyCUDA mailing list
PyCUDA@tiker.net
https://lists.tiker.net/listinfo/pycuda

Re: [PyCUDA] Problems building PyCUDA documentation

[Andreas Kloeckner]

Tomasz Rybak  writes:
> I was trying to rebuild PyCUDA 2016.1.1 (as tagged on GitHub) package using 
> CUDA 7.5 and Sphinx 1.4.4.
> There was warning regarding http to https redirect on documen.tician.de, 
> patch below:
> Index: pycuda-2016.1.1/doc/source/conf.py
> ===
> --- pycuda-2016.1.1.orig/doc/source/conf.py
> +++ pycuda-2016.1.1/doc/source/conf.py
> @@ -187,5 +187,5 @@ latex_documents = [
>  intersphinx_mapping = {
>  'http://docs.python.org/dev': None,
>  'http://docs.scipy.org/doc/numpy/': None,
> -'http://documen.tician.de/codepy/': None,
> +'https://documen.tician.de/codepy/': None,
>  }

Thanks for the patch, I've applied that.

> This is caused by doc/source/conf.py, html_theme_options, which contains 
> Unicode characters for floppy and rocket. I did not have any problems with 
> PyOpenCL, probably because 2016.1 does not contain those glyphs.
>
> Andreas - how have you built documentation for your web page? Is there some 
> special option for Sphinx I should use?

Regarding the Sphinx build problem: I can reproduce this on Python 2,
but I've been using Python 3, where the issue does not occur. I'm not
entirely sure what the issue is--the traceback is somewhere deep in the
weeds.

Andreas

___
PyCUDA mailing list
PyCUDA@tiker.net
https://lists.tiker.net/listinfo/pycuda