On Thu, 2016-09-08 at 08:24 -0700, Lydia Duncan wrote: > Hi Russel, > > In the mass of Python 2 stuff that ran by, did you get an error when > it > tried to install Sphinx? We rely on Sphinx heavily for our > generation > of html documentation, so if it isn't present then very little will > work. We aren't aware of any issues with the current build for > python > 2.7, but that doesn't mean we are necessarily robust in our set > up. We > have taken strides to be, but there's always some use case that we > didn't think of.
I can't find a way of causing the chpl-venv to be recreated to check I'm afraid. I had assumed the created virtualenv would deal with all the Python dependencies, it seems not. I had python3-sphinx installed when I ran "make chpldoc" for the first time, but not python-sphinx. I have now installed it – with loud wailing that Python 2 stuff was being installed :-) chpldoc now runs, but I then had to install the rtd theme separately. This led me to: |> chpldoc factorial.chpl Running Sphinx v1.4.6 Extension error: Could not import extension sphinxcontrib.chapeldomain (exception: No module named 'sphinxcontrib') error: building html output from chpldoc sphinx project > For context that might help you to sort out the source of your build > issue - we build chpldoc in a homemade virtual environment that we > work > within when trying to generate the output. We do this due to > licensing > issues - Sphinx was the best solution available to us for handling > the > html (a previous iteration of chpldoc tried to implement that stuff > by > hand, which was unmaintainable in the long run), and one of Sphinx's > dependencies is under the GPL license. Since we have users that > don't > want to get the GPL license imposed upon their work for various > reasons, > as a compromise we have made it so that only opt-in tools like > chpldoc > build with it - keeping that environment set up locked away in a > virtual > environment until necessary is helpful in that regard. The licence for a tool doesn't affect the material generated unless bits of the tool are copied into the generated material. Thus GCC can be used for proprietary code, but libc6 has to be LGPL not GPL. I am surprised that Sphinx is a problem, I understood it to be licenced under BSD. I guess though if you start using GPL plugins and themes, it would be important to check what they say about generated material, if they add pre-constructed bits and pieces. Having said this, I am not competent to speak about the situation in jurisdictions of the USA. I have had formal opinion about the situation in England and Wales. > Since I know via our previous correspondence that your virtual > environment set up is different than what we expect, I think this is > likely to be the source of your issue. I am doing all this on Debian Sid without virtualenvs. > If sorting those build issues out is too much trouble, I believe our > text mode (chpldoc --text-only) currently does not rely on Sphinx at > all. This will not generate html output (and will thus lose the > visual > appeal and handy links created by Sphinx), but it should be still > usable. A nice get out, but I think it better to be able to do the full thing! -- Russel. ============================================================================= Dr Russel Winder t: +44 20 7585 2200 voip: sip:[email protected] 41 Buckmaster Road m: +44 7770 465 077 xmpp: [email protected] London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------------
_______________________________________________ Chapel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/chapel-users
