I have been chasing a few bugs/issues and trying to improve the automatically generated Sphinx docs. I have made a few fixes on my fork of Phoenix, but I am encountering a slight bump. The docs simply don’t build on Windows - I mean, I get the html files, but Sphinx generates more than 60,000 warnings, most of them related to images it can’t find.
Sample of warning message:
headings.inc:195: WARNING: image file not readable: _staticimagessphinxdocsmodule_summary.png
Which is kind of funny as the actual declaration is:
No, that’s not the issue. I wrote half of the code that converts the wxWidgets docs into Phoenix ones, a few years back. And it was still working not long ago.
The sphinx installation that I have certainly does not work with a backslash in the file name. Single slash or double backslash are working. I would suggest to modify the conversion code to use slashes.
Regards,
Dietmar
···
On 11/12/2017 9:30 PM, Andrea Gavana wrote:
No, that’s not the issue. I wrote half of the code that converts the wxWidgets docs into Phoenix ones, a few years back. And it was still working not long ago.
No, that’s not the issue. I wrote half of the code that converts the
wxWidgets docs into Phoenix ones, a few years back. And it was still
working not long ago.
The sphinx installation that I have certainly does not work with a
backslash in the file name. Single slash or double backslash are
working. I would suggest to modify the conversion code to use
slashes.
I perfectly understand what you wrote, what I’m puzzled about is that the very same code (as far as I can see) used to work a few months back with no modifications. I’ll dig into the docstrings generation code to see if anything has changed since then.
The dist-docs builder on the buildbot is running on a Windows machine, so you may want to look at the logs for recent builds there to see if it gives you any clues. One thing that comes to mind is that Sphinx and its dependencies hasn’t been updated there in a long time, so it may be related to you using a newer version of Sphinx or other packages.
No, that’s not the issue. I wrote half of the code that converts the
wxWidgets docs into Phoenix ones, a few years back. And it was still
working not long ago.
The sphinx installation that I have certainly does not work with a
backslash in the file name. Single slash or double backslash are
working. I would suggest to modify the conversion code to use
slashes.
I perfectly understand what you wrote, what I’m puzzled about is that the very same code (as far as I can see) used to work a few months back with no modifications. I’ll dig into the docstrings generation code to see if anything has changed since then.
Andrea.
Regards,
Dietmar
–
You received this message because you are subscribed to the Google Groups “wxPython-dev” group.
Ran into same issue. Fixed in Github commit. Should be in next release.
Thanks Robin!
···
On Monday, 13 November 2017 12:38:10 UTC-5, Robin Dunn wrote:
Hi Andrea,
The dist-docs builder on the buildbot is running on a Windows machine, so you may want to look at the logs for recent builds there to see if it gives you any clues. One thing that comes to mind is that Sphinx and its dependencies hasn’t been updated there in a long time, so it may be related to you using a newer version of Sphinx or other packages.
No, that’s not the issue. I wrote half of the code that converts the
wxWidgets docs into Phoenix ones, a few years back. And it was still
working not long ago.
The sphinx installation that I have certainly does not work with a
backslash in the file name. Single slash or double backslash are
working. I would suggest to modify the conversion code to use
slashes.
I perfectly understand what you wrote, what I’m puzzled about is that the very same code (as far as I can see) used to work a few months back with no modifications. I’ll dig into the docstrings generation code to see if anything has changed since then.
Andrea.
Regards,
Dietmar
–
You received this message because you are subscribed to the Google Groups “wxPython-dev” group.