You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have two requirements, and they seem to be supported independently, but not together.
One requirement is that my docs be built from a folder that's deep within my repo source (specifically, python-projects/order_utils/setup.py). For this I can use a requirements.txt file, and if I specify that file in Admin, Advanced settings, then the build will properly find my project.
The other requirement is that my setup.py demands Python >= 3.6. To work with this, I've put in place a readthedocs.yaml file, specifying python: version: 3.6, and it does indeed use that version of the interpreter.
However, mixing these two together does not work. The crux of my problem seems to be that the build isn't using the requirements_file specified in my readthedocs.yaml.
However, combining these two approaches does not work.
Expected Result
A build using the interpreter and requirements file specified in readthedocs.yaml.
Actual Result
Using a requirements file but no readthedocs.yaml
Processing ./python-packages/order_utils
0x-order-utils requires Python '>=3.6, <4' but the running Python is 3.5.2
You are using pip version 9.0.1, however version 18.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
As you can see, rtd is installing your requirements file, the next step is falling because you have checked the install project option in your dashboard (can you please check that?). RTD combines both, options from the web and from the configuration file.
Also, soon you can install a setup.py from any path #4740
Details
I have two requirements, and they seem to be supported independently, but not together.
One requirement is that my docs be built from a folder that's deep within my repo source (specifically,
python-projects/order_utils/setup.py
). For this I can use a requirements.txt file, and if I specify that file in Admin, Advanced settings, then the build will properly find my project.The other requirement is that my setup.py demands Python >= 3.6. To work with this, I've put in place a
readthedocs.yaml
file, specifyingpython: version: 3.6
, and it does indeed use that version of the interpreter.However, mixing these two together does not work. The crux of my problem seems to be that the build isn't using the
requirements_file
specified in myreadthedocs.yaml
.However, combining these two approaches does not work.
Expected Result
A build using the interpreter and requirements file specified in
readthedocs.yaml
.Actual Result
Using a requirements file but no
readthedocs.yaml
https://readthedocs.org/projects/0x-order-utils/builds/7994051/
This shows that my requirements file works.
Using a
readthedocs.yaml
without specifying arequirements_file
https://readthedocs.org/projects/0x-order-utils/builds/7994020/
This build shows that my
readthedocs.yaml
file is getting me the interpreter I need, but of course it doesn't know how to find mysetup.py
.Using a readthedocs.yaml that specifies a
requirements_file
https://readthedocs.org/projects/0x-order-utils/builds/7994617/
This build shows that, even though
readthedocs.yaml
containsrequirements_file: requirements.readthedocs.txt
, the behavior is the same as when it doesn't contain that directive.The text was updated successfully, but these errors were encountered: