matplotlib-users Mailing List for matplotlib

Hey Folks, 
We are having a bear of a time installing matplotlib into Python2.3 on 
Solaris9-sparc.
The issues arises from "fatal: relocation error"s coming up when attempting 
to run matplotlib demos...but instead of getting into the details of this 
error, I want to simply ask.
Has anyone successfully installed and run matplotlib on Solaris 9 (or any 
other version) sparc?
If so, how did you build and install it? What version of gcc (or CC if 
that's the case), what switches, ETC?
With thanks in advance!
Mike

>>>>> "Axel" == Axel Kowald <ko...@mo...> writes:
 Axel> Hi, I'm new to matplotlib and I have a question regarding
 Axel> axes. Once I created some axes (either with the axes()
 Axel> command or with subplot() ), how can I later find out the
 Axel> limits (left bottom, width, height) of the axes ? Maybe
 7 >>> ax = subplot(111)
 8 >>> ax.get_position()
 Out[8]: [0.125, 0.10999999999999999, 0.77500000000000002, 0.79000000000000004]
You can change these values with ax.set_position. This works whether
ax is an Axes or Subplot instance.
 Axel> some trick with get() ? Btw. is there somewhere a list of
 Axel> properties that I can get/set with get() or set() ?
A timely question. This feature was just added in the last release,
0.65
 >>> set(ax) # lists all settable properties
 >>> get(ax) # lists all properties and their values
Works for any matplotlib artist or sequence of artists; see
http://matplotlib.sf.net/examples/set_and_get.py
This is still a work in progress - the introspection works in part by
examining doc strings and I have finished porting all the artist
docstrings to the new format. set(artist) should return a list of all
properties and their legal settable values. If the settable values is
listed as unknown, it means I haven't done that docstring yet.
Also, I'm working on implementing Perry's suggestion of returning
silent lists where appropriate, which will help in pretty printing the
output, eg, of get(ax).
But it's mostly functional, as is.
JDH

These notes, with links, can be read at
http://matplotlib.sf.net/whats_new.html.
 - matlab namespace renamed pylab - see
 http://matplotlib.sf.net/matplotlib_to_pylab.py for details on
 conversion. ipython pylab users should grab version 0.6.6. You
 can import the matlab interface (now known as pylab interface) with
 from pylab import blah # OK
 from matplotlib.pylab import blah # OK
 from matplotlib.matlab import blah # Deprecated
 - contouring with the contour function!! Thanks to Nadia Dencheva.
 See examples/contour_demo.py
 - matlab compatible set and get introspection to determine settable
 properties and their values. See examples/set_and_get.py. Sample
 usage
 >>> lines = plot([1,2,3]) 
 >>> set(lines)
 alpha: float
 antialiased or aa: [True | False]
 ...snip lots more...
 >>> get(lines)
 alpha = 1.0
 antialiased or aa = True
 ...snip lots more...
 - Added many new matlab compatible colormaps - autumn bone cool
 copper flag gray hot hsv jet pink prism spring summer winter -
 Thanks Perry!
 - zorder to artists to control drawing order of lines, patches and
 text in axes. See examples/zorder_demo.py 
 - mathtext in cairo backend. Also, printing now works to file
 object. Thanks Steve Chaplin.
 - printing in WX - Matthew Newville contributed a print button and
 preview for the wx backends. He also, who graciously volunteered
 to be the new wx backend maintainer.
 - matlab interface functions connect and disconnect replace
 mpl_connect and mpl_disconnect for event handling
 - Pass hold=True|False to any plotting command to override the
 current hold setting. The original hold setting will be restored
 at the end of the plot function
 - all text instances now have a bbox property which is a dict of
 Rectangle properties. If set, the text instance will display in a
 rectanglular bounding box. Example usage
 
 title('hi mom', bbox={'facecolor':'r', 'alpha':0.5})
 - legend properties now exposed as kwargs. See help(legend)
 - ishold to inspect the hold state
 - new plotting functions spy, spy2 for matrix sparsity visualization
 - pylab interface functions rgrids and thetagrids for customizing
 the grid locations and labels for polar plots - see
 examples/polar_demo.py.
 - add ion, ioff and isinteractive to pylab interface for control of
 interactive mode. See updated discussion at
 http://matplotlib.sf.net/interactive.html
Bugs fixed - 
 - Fixed colorbar bug with scatter - JDH
 - SVG clipping problem - Thanks Norm Peterson
 - numerous small legend bugs fixed
 - zoom to rect works with reversed axis limits - thanks Gregory
 - fontsizing problem fixes, ps plots correctly sized, landscape
 support for ps output
 - smaller, leaner, meaner PS output - Thanks Jochen
 - make the Gtk backends build without an X-server connection -
 Thanks Jochen
 
Downloads at http://matplotlib.sf.net
JDH

Hi,
I'm new to matplotlib and I have a question regarding axes.
Once I created some axes (either with the axes() command or with 
subplot() ), how can I later find out the limits (left bottom, width, 
height) of the axes ?
Maybe some trick with get() ?
Btw. is there somewhere a list of properties that I can get/set with 
get() or set() ?
 Many thanks,
 Axel

>>>>> "Ted" == Ted Drain <ted...@jp...> writes:
 Ted> At least where I work, our style guidelines make it a little
 Ted> more verbose. I need to use descriptive variable names (for
The new short names were meant for easy, interactive use, to minimize
the number of keystrokes. For scripts, especially if you have verbose
coding guidelines, I suggest you use the functions that are already
defined in the matplotlib __init__ file
 import matplotlib
 b = matplotlib.is_interactive()
 matplotlib.interactive(False)
 ....your plot commands here....
 matplotlib.interactive(b)
The short names call these functions, anyhow.
Note that this discussion may be moot, because when writing plotting
functions I rarely use the drawing commands of the pylab interface
since these are by and large wrappers of other methods, eg Axes
methods. Since only the pylab plotting commands trigger the
draw_if_interactive method, you can safely do things like
 ax.plot([1,2,3])
 ax.set_xlabel('time')
 ax.set_title('this is a test')
 ax.grid(True)
w/o worrying about the interactive setting.
JDH