-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot build the doc target on Linux-Arch64 (virtualenv uses python3) #209
Comments
In build.py:25 I changed And it seemed to solve the python3 problem. Now I get
Seems cppformat.css is missing.
|
Thanks for the bug report. Regarding the python2/python3 issue, the only reason why build.py uses Python 2 is because |
Ah, I didn't have lessc (or node, npm, less-plugin-clean-css) installed. So I installed them all, and my build of doc works fine. So this bug is for python2/3 multi installs (need to call Maybe you need to note that you need to have a look at |
As an aside, could you check why my pull request for #208 is failing? Since I can now build doc fine locally. |
Sorry, I don't quite know what the execfile replacement is for python3. Maybe stack overflow can help? |
Most of the dependencies are installed automatically, but I've improved the error message in a596b87. Now it should give
instead of exception and stack trace. |
I wasn't building the doc target via travis-ci. I was building it locally. The error message will help, but I installed the lessc npm, only to have it fail as I didn't install the clean-css plugin (which for me was a seperate install locally). Anyway, that is all off topic. Does virtualenv2 exist on your python install? maybe run that instead of virtualenv (which will default to pytohn3 for multi python installs). |
I don't have |
And I've added section Building the documentation with the list of dependencies. Hope I haven't missed anything. Thanks! |
Trying to pass the CI tests for Issue #205 (Issue #208), and it fails to build the doc target.
So I tried to build it myself, and get introduced to the hellish world of python dependencies.
My fundamental problem is that I have both python2 and python3 installed, and it seems even though the doc script is python2
#!/usr/bin/env python2
the virtualenv and pip utilities are using python3. I'm pretty sure that's bad.The text was updated successfully, but these errors were encountered: