Summary
code-block are not tested, moving them to self-contained python files in docs/examples and referencing them using literalinclude should be better.
list of rst to be changed (run this in docs : grep -rl --include="*.rst" ".. code-block:: python" .):
those are rst files that arent going to be needed
- [ ] ./changelog.rst
for each sub-issue you would do the following:
example of suck a change is available in #167
Summary
code-blockare not tested, moving them to self-contained python files indocs/examplesand referencing them usingliteralincludeshould be better.list of rst to be changed (run this in docs :
grep -rl --include="*.rst" ".. code-block:: python" .):those are rst files that arent going to be needed- [ ] ./changelog.rstfor each sub-issue you would do the following:
code-blockinside a python file in the relevant directory inside docs/example, the file name should betest_something_xwhere x is the index of the code-block inside the rst you're modifying.example of suck a change is available in #167