File: README.debian

package info (click to toggle)
matplotlib 3.10.1%2Bdfsg1-4
  • links: PTS, VCS
  • area: main
  • in suites: sid, trixie
  • size: 78,352 kB
  • sloc: python: 147,118; cpp: 62,988; objc: 1,679; ansic: 1,426; javascript: 786; makefile: 104; sh: 53
file content (52 lines) | stat: -rw-r--r-- 1,375 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
MatplotLib Data Directory
-------------------------

For various functions to work, for example 

  help() -> modules

you need to set the environmental variable:

  $ export MATPLOTLIBDATA=/usr/share/matplotlib/


Change the backend
------------------

From matplotlib version 3.10.1+dfsg1-1 the default backend in Debian
is again autodetected using standard upstream logic.

If you want to change it, you have two ways: system wide, changing the file

  /etc/matplotlibrc

or on a user basis, changing the file

  $HOME/.config/matplotlib/matplotlibrc

to add or modify a line like this:

  backend : <backend>

  # You can also deploy your own backend outside of matplotlib by
  # referring to the module name (which must be in the PYTHONPATH) as
  # 'module://my_backend'.

  # The Agg, Ps, Pdf and SVG backends do not require external
  # dependencies. Do not choose GTK, GTKAgg, GTKCairo, TkAgg or WXAgg if
  # you have disabled the relevant extension modules.

so usually, you can have a backend if you have the Python bindings installed:

  Tk   -> python3-tk
  QT   -> python3-pyqt5, python3-sip
  WX   -> python3-wxgtk4.0
  GTK3 -> gir1.2-gtk-3.0, python3-gi


Use MatplotLib with pkg_resources.require()
-------------------------------------------

If you want to use MatplotLib like this:

  python3 -c 'import pkg_resources; pkg_resources.require("matplotlib")'