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
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
|
.. _troubleshooting-faq:
***************
Troubleshooting
***************
.. contents::
:backlinks: none
.. _matplotlib-version:
Obtaining matplotlib version
============================
To find out your matplotlib version number, import it and print the
``__version__`` attribute::
>>> import matplotlib
>>> matplotlib.__version__
'0.98.0'
.. _locating-matplotlib-install:
:file:`matplotlib` install location
===================================
You can find what directory matplotlib is installed in by importing it
and printing the ``__file__`` attribute::
>>> import matplotlib
>>> matplotlib.__file__
'/home/jdhunter/dev/lib64/python2.5/site-packages/matplotlib/__init__.pyc'
.. _locating-matplotlib-config-dir:
:file:`.matplotlib` directory location
======================================
Each user has a :file:`.matplotlib/` directory which may contain a
:ref:`matplotlibrc <customizing-with-matplotlibrc-files>` file and various
caches to improve matplotlib's performance. To locate your :file:`.matplotlib/`
directory, use :func:`matplotlib.get_configdir`::
>>> import matplotlib as mpl
>>> mpl.get_configdir()
'/home/darren/.matplotlib'
On unix-like systems, this directory is generally located in your
:envvar:`HOME` directory. On windows, it is in your documents and
settings directory by default::
>>> import matplotlib
>>> mpl.get_configdir()
'C:\\Documents and Settings\\jdhunter\\.matplotlib'
If you would like to use a different configuration directory, you can
do so by specifying the location in your :envvar:`MPLCONFIGDIR`
environment variable -- see
:ref:`setting-linux-osx-environment-variables`.
.. _reporting-problems:
Report a problem
================
If you are having a problem with matplotlib, search the mailing
lists first: there's a good chance someone else has already run into
your problem.
If not, please provide the following information in your e-mail to the
`mailing list
<http://lists.sourceforge.net/mailman/listinfo/matplotlib-users>`_:
* your operating system; (Linux/UNIX users: post the output of ``uname -a``)
* matplotlib version::
python -c `import matplotlib; print matplotlib.__version__`
* where you obtained matplotlib (e.g. your Linux distribution's
packages or the matplotlib Sourceforge site, or the enthought
python distribution `EPD
<http://www.enthought.com/products/epd.php>`_).
* any customizations to your ``matplotlibrc`` file (see
:ref:`customizing-matplotlib`).
* if the problem is reproducible, please try to provide a *minimal*,
standalone Python script that demonstrates the problem. This is
*the* critical step. If you can't post a piece of code that we
can run and reproduce your error, the chances of getting help are
significantly diminished. Very often, the mere act of trying to
minimize your code to the smallest bit that produces the error
will help you find a bug in *your* code that is causing the
problem.
* you can get very helpful debugging output from matlotlib by
running your script with a ``verbose-helpful`` or
``--verbose-debug`` flags and posting the verbose output the
lists::
> python simple_plot.py --verbose-helpful > output.txt
If you compiled matplotlib yourself, please also provide
* any changes you have made to ``setup.py`` or ``setupext.py``
* the output of::
rm -rf build
python setup.py build
The beginning of the build output contains lots of details about your
platform that are useful for the matplotlib developers to diagnose
your problem.
* your compiler version -- eg, ``gcc --version``
Including this information in your first e-mail to the mailing list
will save a lot of time.
You will likely get a faster response writing to the mailing list than
filing a bug in the bug tracker. Most developers check the bug
tracker only periodically. If your problem has been determined to be
a bug and can not be quickly solved, you may be asked to file a bug in
the tracker so the issue doesn't get lost.
.. _git-trouble:
Problems with recent git versions
=================================
First make sure you have a clean build and install (see
:ref:`clean-install`), get the latest git update, install it and run a
simple test script in debug mode::
rm -rf build
rm -rf /path/to/site-packages/matplotlib*
git pull
python setup.py install > build.out
python examples/pylab_examples/simple_plot.py --verbose-debug > run.out
and post :file:`build.out` and :file:`run.out` to the
`matplotlib-devel
<http://lists.sourceforge.net/mailman/listinfo/matplotlib-devel>`_
mailing list (please do not post git problems to the `users list
<http://lists.sourceforge.net/mailman/listinfo/matplotlib-users>`_).
Of course, you will want to clearly describe your problem, what you
are expecting and what you are getting, but often a clean build and
install will help. See also :ref:`reporting-problems`.
|
