Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 796c10c

Browse files
committed
Remove the "Developing a new backend" section from contributing guide.
That section basically duplicates the "what is a backend" section in the usage guide, but does so less well, and doesn't provide relevant information for actually *developing* a new backend.
1 parent 512aecb commit 796c10c

File tree

1 file changed

+0
-25
lines changed

1 file changed

+0
-25
lines changed

doc/devel/contributing.rst

Lines changed: 0 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -523,31 +523,6 @@ and running the same script will display::
523523

524524
.. _logging tutorial: https://docs.python.org/3/howto/logging.html#logging-basic-tutorial
525525

526-
.. _custom_backend:
527-
528-
Developing a new backend
529-
------------------------
530-
531-
If you are working on a custom backend, the *backend* setting in
532-
:file:`matplotlibrc` (:doc:`/tutorials/introductory/customizing`) supports an
533-
external backend via the ``module`` directive. If
534-
:file:`my_backend.py` is a Matplotlib backend in your
535-
:envvar:`PYTHONPATH`, you can set it on one of several ways
536-
537-
* in :file:`matplotlibrc`::
538-
539-
backend : module://my_backend
540-
541-
* with the :envvar:`MPLBACKEND` environment variable::
542-
543-
> export MPLBACKEND="module://my_backend"
544-
> python simple_plot.py
545-
546-
* with the use directive in your script::
547-
548-
import matplotlib
549-
matplotlib.use('module://my_backend')
550-
551526
.. _sample-data:
552527

553528
Writing examples

0 commit comments

Comments
 (0)