matplotlib-users Mailing List for matplotlib

On Jan 5, 2008 2:15 PM, Alan G Isaac <ai...@am...> wrote:
> It appears from the documentation that
> ``prop`` for a legend is the same as
> ``fontproperties`` for a label.
>
> If true, perhaps legend should accept
> ``fontproperties`` and perhaps slowly
> deprecate prop?
Yes they are the same thing, and using the same name makes sense.
After the 0.91.2 release, we can deprecate the prop usage.

It appears from the documentation that
``prop`` for a legend is the same as
``fontproperties`` for a label.
If true, perhaps legend should accept
``fontproperties`` and perhaps slowly
deprecate prop?
If false, what's the diff?
Thank you,
Alan Isaac

Thanks guys! You can also just skip a step and go:
gca().fmt_xdata = str
gca().fmt_ydata = str
:)
I changed it in Axes.py. It would be cool if there was something in
matplotlibrc, but now that I understand how it works, it's no biggy to
me.
Take care,
Jack
On Jan 4, 2008 9:18 AM, John Hunter <jd...@gm...> wrote:
> On Jan 4, 2008 7:32 AM, Michael Droettboom <md...@st...> wrote:
> > You can also set a custom formatter for each axis without hacking the
> > matplotlib code::
> >
> > def custom_formatter(value):
> > return str(value)
> >
> > gca().fmt_xdata = custom_formatter
> > gca().fmt_ydata = custom_formatter
> >
> > We may want to add a cleaner (more obvious) API for this -- but there
> > might be good reasons that it works this way that I just don't know about.
>
>
> There is no particularly good reason and it is not terribly consistent
> with the rest of the API, which tends to use function calls more than
> attribute settings. It works well enough and there is plenty of code
> (mine for example) that utilizes it. The major problem is that it is
> not easy for users to find.
>
> JDH
>

Jordan Dawe wrote:
> Ok, I compiled matplotlib from source, and installed it into my home 
> directory. import matplotlib works fine, but from pylab import * returns
> 
> >>> from pylab import *
> Traceback (most recent call last):
> File "<stdin>", line 1, in <module>
> File "/home/users/freedryk//lib/python/pylab.py", line 1, in <module>
> from matplotlib.pylab import *
> File "/home/users/freedryk//lib/python/matplotlib/pylab.py", line 208, 
> in <module>
> from matplotlib import mpl # pulls in most modules
> File "/home/users/freedryk//lib/python/matplotlib/mpl.py", line 4, in 
> <module>
> from matplotlib import axes
> File "/home/users/freedryk//lib/python/matplotlib/axes.py", line 18, 
> in <module>
> from matplotlib import dates as mdates
> File "/home/users/freedryk//lib/python/matplotlib/dates.py", line 91, 
> in <module>
> from dateutil.rrule import rrule, MO, TU, WE, TH, FR, SA, SU, YEARLY, \
> File "/home/users/freedryk//lib/python/dateutil/rrule.py", line 13, in 
> <module>
> import thread
> ImportError: No module named thread
> 
> Any hints? I have my PYTHONPATH set to /home/users/freedryk/lib/python, 
> do I need another path in there?
Jordan,
thread is a standard python module, part of the basic python 
distribution. I don't know why it is not being found. If you start 
python on a command line, can you import thread?
Eric

Ok, I compiled matplotlib from source, and installed it into my home 
directory. import matplotlib works fine, but from pylab import * returns
 >>> from pylab import *
Traceback (most recent call last):
 File "<stdin>", line 1, in <module>
 File "/home/users/freedryk//lib/python/pylab.py", line 1, in <module>
 from matplotlib.pylab import *
 File "/home/users/freedryk//lib/python/matplotlib/pylab.py", line 208, 
in <module>
 from matplotlib import mpl # pulls in most modules
 File "/home/users/freedryk//lib/python/matplotlib/mpl.py", line 4, in 
<module>
 from matplotlib import axes
 File "/home/users/freedryk//lib/python/matplotlib/axes.py", line 18, 
in <module>
 from matplotlib import dates as mdates
 File "/home/users/freedryk//lib/python/matplotlib/dates.py", line 91, 
in <module>
 from dateutil.rrule import rrule, MO, TU, WE, TH, FR, SA, SU, YEARLY, \
 File "/home/users/freedryk//lib/python/dateutil/rrule.py", line 13, in 
<module>
 import thread
ImportError: No module named thread
Any hints? I have my PYTHONPATH set to /home/users/freedryk/lib/python, 
do I need another path in there?
Jordan