ANN: matplotlib-0.90.0

http://www.python.org/pypi/matplotlib/0.90.0

http://sourceforge.net/project/showfiles.php?group_id=80706&package_id=82474&release_id=484485

Binaries will be posted in a few days.

···

===============================================================
2007-02-06 Released 0.90.0 at revision 3003

2007-01-22 Extended the new picker API to text, patches and patch
           collections. Added support for user customizable pick hit
           testing and attribute tagging of the PickEvent - Details
           and examples in examples/pick_event_demo.py - JDH

2007-01-16 Begun work on a new pick API using the mpl event handling
           frameowrk. Artists will define their own pick method with
           a configurable epsilon tolerance and return pick attrs.
           All artists that meet the tolerance threshold will fire a
           PickEvent with artist dependent attrs; eg, a Line2D can set
           the indices attribute that shows the indices into the line
           that are within epsilon of the pick point. See
           examples/pick_event_demo.py. The implementation of pick
           for the remaining Artists remains to be done, but the core
           infrastructure at the level of event handling is in place
           with a proof-of-concept implementation for Line2D - JDH

2007-01-16 src/_image.cpp: update to use Py_ssize_t (for 64-bit systems).
           Use return value of fread() to prevent warning messages - SC.

2007-01-15 src/_image.cpp: combine buffer_argb32() and buffer_bgra32() into
           a new method color_conv(format) - SC

2007-01-14 backend_cairo.py: update draw_arc() so that
           examples/arctest.py looks correct - SC

2007-01-12 backend_cairo.py: enable clipping. Update draw_image() so that
           examples/contour_demo.py looks correct - SC

2007-01-12 backend_cairo.py: fix draw_image() so that examples/image_demo.py
           now looks correct - SC

2007-01-11 Added Axes.xcorr and Axes.acorr to plot the cross
           correlation of x vs y or the autocorrelation of x. pylab
           wrappers also provided. See examples/xcorr_demo.py - JDH

2007-01-10 Added "Subplot.label_outer" method. It will set the
           visibility of the ticklabels so that yticklabels are only
           visible in the first column and xticklabels are only
           visible in the last row - JDH

2007-01-02 Added additional kwarg documentation - JDH

2006-12-28 Improved error message for nonpositive input to log
           transform; added log kwarg to bar, barh, and hist,
           and modified bar method to behave sensibly by default
           when the ordinate has a log scale. (This only works
           if the log scale is set before or by the call to bar,
           hence the utility of the log kwarg.) - EF

2006-12-27 backend_cairo.py: update draw_image() and _draw_mathtext() to work
           with numpy - SC

2006-12-20 Fixed xpdf dependency check, which was failing on windows.
           Removed ps2eps dependency check. - DSD

2006-12-19 Added Tim Leslie's spectral patch - JDH

2006-12-17 Added rc param 'axes.formatter.limits' to control
           the default threshold for switching to scientific
           notation. Added convenience method
           Axes.ticklabel_format() for turning scientific notation
           on or off on either or both axes. - EF

2006-12-16 Added ability to turn control scientific notation
           in ScalarFormatter - EF

2006-12-16 Enhanced boxplot to handle more flexible inputs - EF

2006-12-13 Replaced calls to where() in colors.py with much faster
           clip() and putmask() calls; removed inappropriate
           uses of getmaskorNone (which should be needed only
           very rarely); all in response to profiling by
           David Cournapeau. Also fixed bugs in my 2-D
           array support from 12-09. - EF

2006-12-09 Replaced spy and spy2 with the new spy that combines
           marker and image capabilities - EF

2006-12-09 Added support for plotting 2-D arrays with plot:
           columns are plotted as in Matlab - EF

2006-12-09 Added linewidth kwarg to bar and barh; fixed arg
           checking bugs - EF

2006-12-07 Made pcolormesh argument handling match pcolor;
           fixed kwarg handling problem noted by Pierre GM - EF

2006-12-06 Made pcolor support vector X and/or Y instead of
           requiring 2-D arrays - EF

2006-12-05 Made the default Artist._transform None (rather than
           invoking identity_transform for each artist only to have it
           overridden later). Use artist.get_transform() rather than
           artist._transform, even in derived classes, so that the
           default transform will be created lazily as needed - JDH

2006-12-03 Added LogNorm to colors.py as illustrated by
           examples/pcolor_log.py, based on suggestion by
           Jim McDonald. Colorbar modified to handle LogNorm.
           Norms have additional "inverse" method. - EF

2006-12-02 Changed class names in colors.py to match convention:
           normalize -> Normalize, no_norm -> NoNorm. Old names
           are still available.
           Changed __init__.py rc defaults to match those in
           matplotlibrc - EF

2006-11-22 Fixed bug in set_*lim that I had introduced on 11-15 - EF

2006-11-22 Added examples/clippedline.py, which shows how to clip line
           data based on view limits -- it also changes the marker
           style when zoomed in - JDH

2006-11-21 Some spy bug-fixes and added precision arg per Robert C's
           suggestion - JDH

2006-11-19 Added semi-automatic docstring generation detailing all the
           kwargs that functions take using the artist introspection
           tools; eg 'help text now details the scatter kwargs
           that control the Text properties - JDH

2006-11-17 Removed obsolete scatter_classic, leaving a stub to
           raise NotImplementedError; same for pcolor_classic - EF

2006-11-15 Removed obsolete pcolor_classic - EF

2006-11-15 Fixed 1588908 reported by Russel Owen; factored
           nonsingular method out of ticker.py, put it into
           transforms.py as a function, and used it in
           set_xlim and set_ylim. - EF

2006-11-14 Applied patch 1591716 by Ulf Larssen to fix a bug in
           apply_aspect. Modified and applied patch
           1594894 by mdehoon to fix bugs and improve
           formatting in lines.py. Applied patch 1573008
           by Greg Willden to make psd etc. plot full frequency
           range for complex inputs. - EF

2006-11-14 Improved the ability of the colorbar to track
           changes in corresponding image, pcolor, or
           contourf. - EF

2006-11-11 Fixed bug that broke Numeric compatibility;
           added support for alpha to colorbar. The
           alpha information is taken from the mappable
           object, not specified as a kwarg. - EF

2006-11-05 Added broken_barh function for makring a sequence of
           horizontal bars broken by gaps -- see examples/broken_barh.py

2006-11-05 Removed lineprops and markerprops from the Annotation code
           and replaced them with an arrow configurable with kwarg
           arrowprops. See examples/annotation_demo.py - JDH

2006-11-02 Fixed a pylab subplot bug that was causing axes to be
           deleted with hspace or wspace equals zero in
           subplots_adjust - JDH

2006-10-31 Applied axes3d patch 1587359
           http://sourceforge.net/tracker/index.php?func=detail&aid=1587359&group_id=80706&atid=560722
           JDH

Hi Charlie,

Great to see a new release, will put some time aside to test it with wxPython early next week.

I can't see a reference to the wxPython backend, will it still require the Unicode build or can one use the Ansi build and which versions of wxPython are supported?

Werner

Well, we haven't built any binaries yet. We pushed a source release
fast to try to get it into Feisty. Sorry Chris! With wx2.8 out now
and this being a major release, we definitely need to rethink wx
builds. We stuck with unicode for 0.87 to avoid confusion. I would
be happy to hear what wx users think/want.

- Charlie

···

On 2/7/07, Werner F. Bruhin <werner.bruhin@...185...> wrote:

Hi Charlie,

Great to see a new release, will put some time aside to test it with
wxPython early next week.

I can't see a reference to the wxPython backend, will it still require
the Unicode build or can one use the Ansi build and which versions of
wxPython are supported?

Charlie Moad wrote:

Hi Charlie,

Great to see a new release, will put some time aside to test it with
wxPython early next week.

I can't see a reference to the wxPython backend, will it still require
the Unicode build or can one use the Ansi build and which versions of
wxPython are supported?

Well, we haven't built any binaries yet. We pushed a source release
fast to try to get it into Feisty. Sorry Chris! With wx2.8 out now
and this being a major release, we definitely need to rethink wx
builds. We stuck with unicode for 0.87 to avoid confusion. I would
be happy to hear what wx users think/want.

For me the ideal would be not to be depended on a particular release of wxPython - big surprise no :slight_smile: .
If I understand it correctly the dependency came in for performance optimization, does 2.8 change something for this.
- If yes, I would not see a problem with 0.9 requiring as a minimum 2.8.0.1 but going forward I could use any 2.8.x or newer release.
- If no, then I guess we have to live with having a "fixed" dependency, e.g. 0.87 is wxPython 2.6.x, 0.90 is wxPython 2.8.x, but it should through at least a warning if one tries to use it with another wxPython release.

Werner

···

On 2/7/07, Werner F. Bruhin <werner.bruhin@...185...> wrote:

Werner F. Bruhin wrote:

Great to see a new release, will put some time aside to test it with wxPython early next week.

looking forward to your reports.

which versions of wxPython are supported?

I haven't tried the new one, but the last release worked well with wxPython2.6.3, but had some issues with 2.8.* -- I don't think anyone has addressed those yet.

Well, we haven't built any binaries yet. We pushed a source release
fast to try to get it into Feisty. Sorry Chris!

well, I've been chattering on about this for awhile, but haven't contributed anything yet...

> With wx2.8 out now

and this being a major release, we definitely need to rethink wx
builds. We stuck with unicode for 0.87 to avoid confusion. I would
be happy to hear what wx users think/want.

I think it's time to just all unicode, all the way, but I mostly deal with English anyway.

For me the ideal would be not to be depended on a particular release of wxPython - big surprise no :slight_smile:

That would be nice.

If I understand it correctly the dependency came in for performance optimization, does 2.8 change something for this.

Perhaps. 2.8 has methods for directly setting the data in wxBitmaps. Before that, you needed to create a wxImage, then convert that to a bitmap.

However, to do that right, you'd need to be able to get the Agg bitmap as a Python buffer object that is in the binary form required by the platform. I think the majors need RGB and/or RGBA, but I'm not totally sure about that (maybe OS-X is ARGB?)

- If yes, I would not see a problem with 0.9 requiring as a minimum 2.8.0.1 but going forward I could use any 2.8.x or newer release.

That would be a good way to go, or have fallback on the older methods for less than 2.8 -- so instead of saying "you need 2.8 to use the wx backend" we can say: "you'll get better performance with wx if you use > 2.8"

- If no, then I guess we have to live with having a "fixed" dependency, e.g. 0.87 is wxPython 2.6.x, 0.90 is wxPython 2.8.x, but it should through at least a warning if one tries to use it with another wxPython release.

Yes, it should. I've also started a patch for the build system that tries harder to make sure that you are building against the same wx that you are running -- that will at least help people built it themselves more easily.

NOTE: I took a look at the wx backend code a while ago, and it looks like even without the new Bitmap handlers in 2.8, it could be faster with straight Python code. Key is that a wxImage can be created from a Python buffer object without copying the data. So if we can expose the Agg buffer as a Python buffer, as RGB, then we should be able to get decent performance with pure python. You'd still need to do the wxBitmapFromImage thing, but the accelerated back-end does that too.

Look for a thread on this list a while back, with my and Ken's name on it.

-Chris

···

--
Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception

Chris.Barker@...259...

which versions of wxPython are supported?

I haven't tried the new one, but the last release worked well with
wxPython2.6.3, but had some issues with 2.8.* -- I don't think anyone
has addressed those yet.

Just to confirm, the binary posted at the following
http://downloads.sourceforge.net/matplotlib/matplotlib-0.90.0-py2.5-macosx-10.4-fat.egg?modtime=1171118530&big_mirror=0
was compiled to work with wxPython 2.6 but may work with wxPython 2.8?

Shouldn't the version of wxPython also get included in the name along with the python version and os version?

Sam

Where can I find the master TeX document for 0.90? I'd like to make some
corrections, and maybe add things.

Thanks - Damian

Pacific Engineering Systems International, 277-279 Broadway, Broadway NSW 2007
Ph:+61-2-8571-0847 .. Fx:+61-2-9692-9623 | unsolicited email not wanted here !
Views and opinions here are mine and not those of any past or present employer

Hi Damian,

For the users_guide.tex see:

You can checkout the SVN dir where the users guide is located at:

Best,
Edin

···

On 2/20/07, Damian McGuckin <damianm@...1474...> wrote:

Where can I find the master TeX document for 0.90? I'd like to make some
corrections, and maybe add things.

Thanks - Damian

Pacific Engineering Systems International, 277-279 Broadway, Broadway NSW 2007
Ph:+61-2-8571-0847 .. Fx:+61-2-9692-9623 | unsolicited email not wanted here !
Views and opinions here are mine and not those of any past or present employer