Hi
In one somewhat bigger application of mine, which makes use of matplotlib, it
can happen that a user can assign a name to a dataset, which latex in turn is
unable to process as part of the legend. Of course it is possible to prevent
the user from doing so in most cases, but still it is possible that a
RuntimeError is raised.
My actual problem now is that there is no way to figure out where the
exception was thrown by means of simply following the traceback, because the
traceback is only about the matplotlib code. Or with other words: The
traceback shows only where the problem in the matplotlib code is, e.g.
Traceback (most recent call last):
File "/usr/lib64/python2.4/site-packages/matplotlib/backends/backend_wx.py",
line 1048, in _onPaint
self.draw(repaint=False)
<snip most of the Traceback>
File "/usr/lib64/python2.4/site-packages/matplotlib/texmanager.py", line 197,
in make_dvi
if exit_status: raise RuntimeError('LaTeX was not able to process \
RuntimeError: LaTeX was not able to process the flowing string:
<<some string>>
Here is the full report generated by LaTeX:
etc. etc. etc.
Alright, this particular error was provoked and for a small script it will be
easy to figure out where the string in question was passed to latex, but I
hope I was able to make myself clear.
Is it feasible to get a future release of matplotlib to include the individual
programmers code where the exception was triggered into the traceback? (Or
did I accidently truncate this very part of a traceback somehow?)
Regards,
Christian
PS I guess it should read:
"LaTeX was not able to process the following string" instead of "flowing
string", right?
PPS Guess I should mention too, that I don't use the most recent version of
mpl, but '0.87.3'.