|
29 | 29 | "Answer the questions that appear on the screen. In case of doubt, just press the `<Return>` key repeatedly to take the default values.\n", |
30 | 30 | "\n", |
31 | 31 | "After that, there will be a few brand-new files in the current directory.\n", |
32 | | - "You'll have to make a few changes to the file named [conf.py](conf.py). You should at least check if those two variables contain the right things:\n", |
| 32 | + "You'll have to make a few changes to the file named `conf.py`. You should at least check if those two variables contain the right things:\n", |
33 | 33 | "\n", |
34 | 34 | "```python\n", |
35 | 35 | "extensions = [\n", |
|
39 | 39 | "exclude_patterns = ['_build', '**.ipynb_checkpoints']\n", |
40 | 40 | "```\n", |
41 | 41 | "\n", |
42 | | - "Once your `conf.py` is in place, edit the file named `index.rst` and add the file names of your notebooks (with or without the `.ipynb` extension) to the [toctree](http://www.sphinx-doc.org/en/master/usage/restructuredtext/directives.html#directive-toctree) directive.\n", |
43 | | - "\n", |
44 | | - "<div class=\"alert alert-info\">\n", |
| 42 | + "For an example, see this project's [conf.py](conf.py) file.\n", |
45 | 43 | "\n", |
46 | | - "**autosummary bug:**\n", |
47 | | - "\n", |
48 | | - "If you are using the `sphinx.ext.autosummary` Sphinx extension, there is [a bug in Sphinx (below version 1.5)](https://github.com/sphinx-doc/sphinx/issues/2485) which prevents notebooks from being parsed. \n", |
49 | | - "As a work-around you can explicitly list all the files for which autosummary should be ran using the [autosummary_generate](http://www.sphinx-doc.org/en/master/ext/autosummary.html#confval-autosummary_generate) variable in `conf.py`. For example,\n", |
50 | | - "\n", |
51 | | - "```python\n", |
52 | | - "autosummary_generate = ['myfile1.rst', 'myfile2.rst']\n", |
53 | | - "```\n", |
54 | | - "\n", |
55 | | - "</div>" |
| 44 | + "Once your `conf.py` is in place, edit the file named `index.rst` and add the file names of your notebooks (with or without the `.ipynb` extension) to the [toctree](http://www.sphinx-doc.org/en/master/usage/restructuredtext/directives.html#directive-toctree) directive.\n", |
| 45 | + "For an example, see this project's [index.rst](index.rst) file." |
56 | 46 | ] |
57 | 47 | }, |
58 | 48 | { |
|
136 | 126 | "cell_type": "markdown", |
137 | 127 | "metadata": {}, |
138 | 128 | "source": [ |
139 | | - "## Automatic Creation of HTML and PDF output on [readthedocs.org](https://readthedocs.org)\n", |
| 129 | + "## Automatic Creation of HTML and PDF output on readthedocs.org\n", |
140 | 130 | "\n", |
141 | 131 | "There are two different methods, both of which are described below.\n", |
142 | 132 | "\n", |
143 | | - "In both cases, you'll first have to create an account on https://readthedocs.org/ and connect your Github/Bitbucket account. Instead of connecting, you can also manually add any publicly available Git/Subversion/Mercurial/Bazaar repository.\n", |
| 133 | + "In both cases, you'll first have to create an account on https://readthedocs.org/ and connect your GitLab/Github/Bitbucket account. Instead of connecting, you can also manually add any publicly available Git/Subversion/Mercurial/Bazaar repository.\n", |
144 | 134 | "\n", |
145 | 135 | "After doing the steps described below, you only have to \"push\" to your repository, and the HTML pages and the PDF file of your stuff are automagically created on readthedocs.org. Awesome!\n", |
146 | 136 | "\n", |
147 | 137 | "You can even have different versions of your stuff, just use Git tags and branches and select in the readthedocs.org settings (under \"Admin\", \"Versions\") which of those should be created.\n", |
148 | 138 | "\n", |
149 | | - "If your new versions are not automatically built, go to the \"Settings\" of your Github repository, continue to \"Integrations & services\", and make sure that \"ReadTheDocs\" is listed and activated in the \"Services\" section. If not, use \"Add service\". There is probably a similar thing for Bitbucket and others.\n", |
150 | | - "\n", |
151 | 139 | "<div class=\"alert alert-info\">\n", |
152 | 140 | "\n", |
153 | 141 | "**Note:**\n", |
|
222 | 210 | "**Note:**\n", |
223 | 211 | "\n", |
224 | 212 | "Most of the \"Advanced Settings\" on readthedocs.org will be ignored if you have a `readthedocs.yml` file.\n", |
| 213 | + "In this file you can control all the settings, see https://docs.readthedocs.io/en/latest/yaml-config.html.\n", |
225 | 214 | "\n", |
226 | 215 | "</div>\n", |
227 | 216 | "\n", |
|
351 | 340 | "\n", |
352 | 341 | "In the Jupyter Notebook application, you can manually clear all outputs by selecting\n", |
353 | 342 | "\"Cell\" $\\to$ \"All Output\" $\\to$ \"Clear\" from the menu.\n", |
| 343 | + "In JupyterLab, the menu items are \"Edit\" $\\to$ \"Clear All Outputs\".\n", |
354 | 344 | "\n", |
355 | 345 | "There are several tools available to remove outputs from multiple files at once without having to open them separately.\n", |
356 | 346 | "You can even include such a tool as \"clean/smudge filters\" into your Git workflow, which will strip the output cells automatically whenever a Git command is executed.\n", |
|
381 | 371 | "name": "python", |
382 | 372 | "nbconvert_exporter": "python", |
383 | 373 | "pygments_lexer": "ipython3", |
384 | | - "version": "3.6.4+" |
| 374 | + "version": "3.7.1" |
385 | 375 | } |
386 | 376 | }, |
387 | 377 | "nbformat": 4, |
|
0 commit comments