-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Could not import extension readthedocs_ext.readthedocs #1926
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
Comments
This might be another issue related to conda usage. Looks like our extension wasn't installed. |
We should be pip installing the readthedocs extension, I'm not sure why it wouldn't be picked up in the conda environment. We just deployed some conda fixes yesterday that might fix this. Are you still seeing it? |
Just did another build and still seeing it |
What is the readthedocs.yml and environment.yml file you're using? On Fri, Jan 15, 2016 at 3:22 PM, Ivo Flipse [email protected]
Eric Holscher |
The readthedocs.yml is:
The environment.yml is:
|
I believe this is overriding the Python key in the yaml file. Try using this:
The issue is likely that it's installing the pip dependencies into the Python 2 conda environment, then when the environment upgrades it to 3, it isn't found. |
We'll try this today. We weren't aware of this behaviour of YAML: >>> yaml.load('python:\n- test')
{'python': ['test']}
>>> yaml.load('python:\n- test\npython:\n- test2')
{'python': ['test2']}
>>> yaml.load('python:\n- test\n- test2')
{'python': ['test', 'test2']} |
It seems we're no longer getting this error, but now get this issue: #1901 Which seems an indication that indeed Python 3 is now chosen, as our readthedocs.yml file indicates. So I'm closing this |
While building the docs for one of our projects on RTD.com we get the following error and this step:
python /home/docs/checkouts/readthedocs.org/user_builds/clinical-graphics-articulis3/conda/latest/bin/sphinx-build -T -b readthedocs -d _build/doctrees-readthedocs -D language=en . _build/html
Any idea what might be causing this issue?
The text was updated successfully, but these errors were encountered: