matplotlib-devel Mailing List for matplotlib

On Wednesday 07 February 2007 12:09:18 pm Rob Hetland wrote:
> The MPL Qt backend requires PyQt (or, better, Qt4 and PyQt4). PyQt
> does compile against the Qt Library, and also takes quite a while to
> complete. PyQt does not use setuptools, and I am not sure how to
> make a generally usable binary distribution from it.
>
> I would say that installation is quite easy (although time consuming)
> -- perhaps just a good set of directions on the MPL site?
>
> -Rob
>
> On Feb 7, 2007, at 10:01 AM, Christopher Barker wrote:
> > Thanks for doing this Rob, its nice to get as much support on OS-X as
> > possible.
> >
> > Does the QT back-end need to be compiled against QT? or is it
> > python-only?
The Qt backend is pure python. 
Darren

The MPL Qt backend requires PyQt (or, better, Qt4 and PyQt4). PyQt 
does compile against the Qt Library, and also takes quite a while to 
complete. PyQt does not use setuptools, and I am not sure how to 
make a generally usable binary distribution from it.
I would say that installation is quite easy (although time consuming) 
-- perhaps just a good set of directions on the MPL site?
-Rob
On Feb 7, 2007, at 10:01 AM, Christopher Barker wrote:
> Thanks for doing this Rob, its nice to get as much support on OS-X as
> possible.
>
> Does the QT back-end need to be compiled against QT? or is it 
> python-only?
>
>> QT4 takes *forever* to compile, but it seems to compile easier now
>> than previous versions that needed a small library hack. The default
>> configuration compiles and installs fine. The other tools (PyQt4 and
>> SIP) also compile and install painlessly with the default 
>> configuration.
>
> Any chance you could package it up an submit it to the pythonmac 
> archive?
>
> Does it support a Universal build?
>
> -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
>
> Chr...@no...
>
> ---------------------------------------------------------------------- 
> ---
> Using Tomcat but need to do more? Need to support web services, 
> security?
> Get stuff done quickly with pre-integrated technology to make your 
> job easier.
> Download IBM WebSphere Application Server v.1.0.1 based on Apache 
> Geronimo
> http://sel.as-us.falkag.net/sel? 
> cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
----
Rob Hetland, Associate Professor
Dept. of Oceanography, Texas A&M University
http://pong.tamu.edu/~rob
phone: 979-458-0096, fax: 979-845-6331

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 :-)
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
Chr...@no...

Thanks for doing this Rob, its nice to get as much support on OS-X as 
possible.
Does the QT back-end need to be compiled against QT? or is it python-only?
> QT4 takes *forever* to compile, but it seems to compile easier now 
> than previous versions that needed a small library hack. The default 
> configuration compiles and installs fine. The other tools (PyQt4 and 
> SIP) also compile and install painlessly with the default configuration.
Any chance you could package it up an submit it to the pythonmac archive?
Does it support a Universal build?
-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
Chr...@no...

On Wednesday 07 February 2007 10:12:36 am Rob Hetland wrote:
> The patch works. Thanks. Two more things:
>
> 1 - the icons look very small in the toolbar buttons (they look
> bigger in TkAgg). Is there a fix for this?
I'm not sure. I'll look into it when I get a chance.
> 2 - the subplot configure toolbar (where you get a pop-up window that
> lets you modify the axis size and position) does not work. In
> particular, the sliders do not appear, although everything else seems
> to work (clicking in the empty window does modify the axis)
This is a known bug. We looked into it a while back, and couldn't make any 
headway.
Darren

The patch works. Thanks. Two more things:
1 - the icons look very small in the toolbar buttons (they look 
bigger in TkAgg). Is there a fix for this?
2 - the subplot configure toolbar (where you get a pop-up window that 
lets you modify the axis size and position) does not work. In 
particular, the sliders do not appear, although everything else seems 
to work (clicking in the empty window does modify the axis)
These two fixes are beyond my skill set, but I'll help where I can..
-r
On Feb 7, 2007, at 8:58 AM, Darren Dale wrote:
> Hi Rob,
>
> On Wednesday 07 February 2007 09:06:42 am Rob Hetland wrote:
>> Developers: Finally, I had to make some small changes to the qt4
>> backend so that things worked right. One is an essential change --
>> the latin1() method no longer exists in the newer qt. The other is a
>> cosmetic change so that I can see the cursor position in the toolbar
>> better. Diff below.
>
> Thanks for the notes, and for the patch. I moved the margin 
> adjustment you
> suggested into a class attribute of NavigationToolbar2QT. This way,
> FigureManagerQT can get that information, which is needed to 
> properly set the
> height of the figure window. (figsize=(6,4) should yield a 6"x4" 
> plotting
> area, the height of the entire window is larger than 4" to 
> accommodate the
> toolbar.) Changes in svn 3004.
>
> Darren
----
Rob Hetland, Associate Professor
Dept. of Oceanography, Texas A&M University
http://pong.tamu.edu/~rob
phone: 979-458-0096, fax: 979-845-6331

Hi Rob,
On Wednesday 07 February 2007 09:06:42 am Rob Hetland wrote:
> Developers: Finally, I had to make some small changes to the qt4
> backend so that things worked right. One is an essential change --
> the latin1() method no longer exists in the newer qt. The other is a
> cosmetic change so that I can see the cursor position in the toolbar
> better. Diff below.
Thanks for the notes, and for the patch. I moved the margin adjustment you 
suggested into a class attribute of NavigationToolbar2QT. This way, 
FigureManagerQT can get that information, which is needed to properly set the 
height of the figure window. (figsize=(6,4) should yield a 6"x4" plotting 
area, the height of the entire window is larger than 4" to accommodate the 
toolbar.) Changes in svn 3004.
Darren

Here are some notes I made -- I hope it might save someone a bit of 
time.
So, I finally tried out a few other backends on mac os x. I had been 
recommending and using TkAgg, as this works out of the box on mac os 
x. However, it seems unsnappy sometimes, and there was this strange 
issue with the first window not giving control back to the command line.
QT4 takes *forever* to compile, but it seems to compile easier now 
than previous versions that needed a small library hack. The default 
configuration compiles and installs fine. The other tools (PyQt4 and 
SIP) also compile and install painlessly with the default configuration.
I initially forgot to set the -q4thread for ipython (since the other - 
pylab flag is hidden in a launching script). After that it worked 
mostly fine.
I found that the correct threading was sensitive to how I started 
ipython. I have been using terminal, and I was starting ipython like 
this:
bash -l -c /path/to/ipython -q4thread
from within a terminal .term file (i.e., the terminal starts running 
ipython automatically). This seems to not work great. However, when 
I put this command in a script, and run the script like
bash -l -c pylab_start_script
thinks work as expected. This is also true when just typing these 
commands in on the command line. I almost always start ipython from 
a terminal .term file from quicksilver. This gives me a dedicated 
(color coded) ipython window instantly that does not take away my 
shell. This is all pretty slick, and I am pleased with the setup now.
Developers: Finally, I had to make some small changes to the qt4 
backend so that things worked right. One is an essential change -- 
the latin1() method no longer exists in the newer qt. The other is a 
cosmetic change so that I can see the cursor position in the toolbar 
better. Diff below.
-Rob
Index: backend_qt4.py
===================================================================
--- backend_qt4.py	(revision 2999)
+++ backend_qt4.py	(working copy)
@@ -148,7 +148,7 @@
 def _get_key( self, event ):
 if event.key() < 256:
- key = event.text().latin1()
+ key = str(event.text())
 elif self.keyvald.has_key( event.key() ):
 key = self.keyvald[ event.key() ]
 else:
@@ -290,7 +290,7 @@
 # The automatic layout doesn't look that good - it's 
too close
 # to the images so add a margin around it.
- margin = 4
+ margin = 12
 button.setFixedSize( image.width()+margin, image.height 
()+margin )
 QtCore.QObject.connect( button, QtCore.SIGNAL( 'clicked 
()' ),
@@ -301,7 +301,7 @@
 # The stretch factor is 1 which means any resizing of the 
toolbar
 # will resize this label instead of the buttons.
 self.locLabel = QtGui.QLabel( "", self )
- self.locLabel.setAlignment( QtCore.Qt.AlignRight | 
QtCore.Qt.AlignVCenter )
+ self.locLabel.setAlignment( QtCore.Qt.AlignRight | 
QtCore.Qt.AlignTop )
 self.locLabel.setSizePolicy(QtGui.QSizePolicy 
(QtGui.QSizePolicy.Ignored,
 
QtGui.QSizePolicy.Ignored))
 self.layout.addWidget( self.locLabel, 1 )
----
Rob Hetland, Associate Professor
Dept. of Oceanography, Texas A&M University
http://pong.tamu.edu/~rob
phone: 979-458-0096, fax: 979-845-6331

Darn! missed the chance to update the wx back-end -- oh well, hopefully 
the next release.
-Chris
-- 
Christopher Barker, Ph.D.
Oceanographer
NOAA/OR&R/HAZMAT (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception

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

Ok, I'll try to get it posted on SF tonight.
On 2/6/07, John Hunter <jd...@gm...> wrote:
> On 2/6/07, Charlie Moad <cw...@gm...> wrote:
> > rev3002 works great for me. I can push the windows releases this
> > Saturday. I could push a source release sooner. Is anyone opposed to
> > me pushing a source release Friday with the binaries following up on
> > Saturday? If there are no objections, let's avoid major commits until
> > after then.
>
> Let's do the source release ASAP -- I'll update the website for win32
> users to point to the older release so they can find it until the
> win32 binaries are out. That way if ubuntu wants to use this for
> their next release before the Feb 8th upstream freeze they can (and it
> will give us one day to do a point bugfix release if the whole world
> blows up). Just be sure that you use the same svn revision for the
> src release and the win32 builds which will help us with user errors.
> And email us when the new source is up so I'll know to make the
> website change.
>
> And let's call it 0.90 god-doggy. I'm getting tired of 0.87. There
> is at least one signficant API breaking new feature (the pick API)
> which alone justifies not making this a point release. There are also
> several new features sampled below
>
> 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 -
>
> 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
>
> 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
>
> 2006年12月09日 Replaced spy and spy2 with the new spy that combines
> marker and image capabilities
>
> 2006年12月19日 Added Tim Leslie's spectral patch
>
> 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
>
> 2006年11月05日 Added broken_barh function for makring a sequence of
> horizontal bars broken by gaps -- see examples/broken_barh.py
>
> Thanks!
> JDH
>