|
| 1 | +=================== |
| 2 | +Troubleshooting FAQ |
| 3 | +=================== |
| 4 | + |
| 5 | +.. _reporting_problems: |
| 6 | + |
| 7 | +How do I report a problem? |
| 8 | +========================== |
| 9 | + |
| 10 | +If you are having a problem with matplotlib, search the mailing |
| 11 | +lists first: There's a good chance someone else has already run into |
| 12 | +your problem. |
| 13 | + |
| 14 | +If not, please provide the following information in your e-mail to the |
| 15 | +mailing list: |
| 16 | + |
| 17 | + * your operating system |
| 18 | + * matplotlib version |
| 19 | + * where you obtained matplotlib (e.g. your Linux distribution's |
| 20 | + packages or the matplotlib Sourceforge site) |
| 21 | + * any customizations to your ``matplotlibrc`` file |
| 22 | + * if the problem is reproducible, please try to provide a minimal, |
| 23 | + standalone Python script that demonstrates the problem |
| 24 | + |
| 25 | +If you compiled matplotlib yourself, please also provide |
| 26 | + |
| 27 | + * any changes you have made to ``setup.py`` or ``setupext.py`` |
| 28 | + * the output of:: |
| 29 | + |
| 30 | + rm -rf build |
| 31 | + python setup.py build |
| 32 | + |
| 33 | + The beginning of the build output contains lots of details about your |
| 34 | + platform that are useful for the matplotlib developers to diagnose |
| 35 | + your problem. |
| 36 | + |
| 37 | +Including this information in your first e-mail to the mailing list |
| 38 | +will save a lot of time. |
| 39 | + |
| 40 | +You will likely get a faster response writing to the mailing list than |
| 41 | +filing a bug in the bug tracker. Most developers check the bug |
| 42 | +tracker only periodically. If your problem has been determined to be |
| 43 | +a bug and can not be quickly solved, you may be asked to file a bug in |
| 44 | +the tracker so the issue doesn't get lost. |
| 45 | + |
0 commit comments