Update to build docs locally #280
Conversation
|
thanks @danielhuppmann, I just updated the docs requirements (I think). The |
|
restarted travis, this was an iiasa conneciton issue. And https://pyam-iamc.readthedocs.io/en/docs-requirements-makefile/ LGTM!! |
|
I see now the setup.py issue.. let me look |
|
Maybe we can confirm with something like |
|
I have no idea unfortunately. A fallback option would be to just point to
the setup.py for requirements rather than have them as a list for the time
being?
…On Thu, 31 Oct 2019 at 6:42 pm, Matthew Gidden ***@***.***> wrote:
Maybe we can confirm with something like from setup import REQUIREMENTS.
At what point did this break? do we know?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#280?email_source=notifications&email_token=AFUH5G2MG6EGD45EK3JAMBDQRKD47A5CNFSM4JHBHZB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECW2HZQ#issuecomment-548250598>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFUH5G6FEG435BMMQJZR3ZLQRKD47ANCNFSM4JHBHZBQ>
.
|
|
Just talked to @khaeru. His suggestion is that RTD does not guarantee the same locality. We should try to change to something like (and this is getting rather long..) Basically, we need to make sure the import is relative to this file location. If that doesn't work, I'm not sure what is best to do... also trying this now on iiasa/aneris |
|
Hi all - this approach has failed for me (there is no I am testing the setup.py version on aneris: https://readthedocs.org/projects/aneris/builds/9889492/ My work around for the moment is to read directly from |
|
I am now uber confused. Reading direct from |
|
Does it clone everything in the same level perhaps? You could make it print
the output of os.lsdir to see what it’s put where?
…On Thu, 31 Oct 2019 at 7:51 pm, Matthew Gidden ***@***.***> wrote:
I am now uber confused. Reading direct from setup.py on RTD is a success
for aneris:
https://aneris.readthedocs.io/en/test-read-from-setup/install.html
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#280?email_source=notifications&email_token=AFUH5G4LUFFCWRO6VNJ4Q63QRKMCFA5CNFSM4JHBHZB2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECW7FQA#issuecomment-548270784>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFUH5GZWM4Z6YOOA7QUKJF3QRKMCFANCNFSM4JHBHZBQ>
.
|
|
see this output when trying to use Seems it's looking for |
|
I guess it's iterating over |
|
got it in https://github.com/IAMconsortium/pyam/tree/docs-test-rtd (no idea why it's working differently from @znicholls, as this branch is on the org repo, I took the liberty of committing the fix directly |
perfect that was the hope! |
|
One more question - we have a hard requirement for |
|
we can add |
It would have to be |
|
thanks guys! |
Main changes: - Add message_ix.models module - Adjust tools.add_year for ixmp API changes - Add Scenario._backend, .years_active; delete .remove_solution - Delete Scenario.clone - Use Backend.ms_cat_set_elements - Use Backend.ms_* methods; remove Scenario._jobj shim - Re-add thin Scenario.clone() wrapper - Adjust docs cross-reference to ixmp - Convert Path to str in message_ix.cli - Provide firstmodelyear using Scenario.cat - Update RELEASE_NOTES - Coerce to int in Scenario.firstmodelyear - Remove Scenario._backend (now handled by ixmp) - Adjust add_par signature in testing.make_westeros - Compute years_active in Scenario, rather than using backend - Update documentation; remove parallel copy of ixmp API docs - Move CPLEX optfile code to MESSAGE class; adjust docs - Fix small docs typos - Further docs improvements; remove _init_scenario (no-op) - Proofread docs and comments - Update API docs per @gidden reivew - Further improve API docs Tidy CI files per ixmp: - Fix pip VCS URLs - Update Travis caching and env.sh - Update ci/requirements.txt - Add ci/appveyor-install.ps1 to echo ixmp - On AppVeyor, update pip using conda - On Travis, update pip using conda - Add numpy to explicit requirements - Add conda info to Travis for debugging - Travis: install dependencies using conda - Split requirements.txt - Give conda --yes - Add pip to testing conda env - Install conda-requirements into testing conda env - Install pip-requirements into testing conda environment - Update doc/requirements.txt - Add to conda-requirements - Move JPype, pint, plotnine from conda-req to pip-req - Return JPype to conda-req as JPype1 - Append conda-forge to default channels for JPype - Adjust coveragerc - Return CI to ixmp@master - Work around IAMconsortium/pyam#280 / IAMconsortium/pyam#281
In response to #278 and supercedes #279
closes #278