One little question: in my personal copy of this, I had
> rebound the mouse events to have the rotation follow VTK
> conventions. Wouldn't it be a good idea to be
> VTK-compatible on this front?
It would -- want to dust off your developer permissions and test a
commit to the new svn repo 
Also, I notice that proj3d defines it's own dot and cross: by simply
replacing these with the ATLAS enhanced numpy versions, we might see a
significant performance boost.
JDH
John Hunter wrote:
"Fernando" == Fernando Perez <Fernando.Perez@...76...> writes:
> One little question: in my personal copy of this, I had
> rebound the mouse events to have the rotation follow VTK
> conventions. Wouldn't it be a good idea to be
> VTK-compatible on this front?It would -- want to dust off your developer permissions and test a
commit to the new svn repo
Well, I tried installing from SVN yesterday but couldn't because
./setup.py bdist_rpm
doesn't work anymore (it used to). So for now I'm holding back on mpl updates, I'm afraid. Here, I simply can't afford the time to do non-rpm installs, because I need to distribute installs to multiple machines in a clean and upgradable way. rpms do it perfectly, and for a long time, Numeric, old-scipy and matplotlib all accepted the above command happily. Unfortunately that's not true anymore of mpl (haven't checked numpy/scipy-new yet, as those will need actual code porting).
If anyone is interested in having a go at this, the error is (just the final part):
===================================================================
Executing(%build): /bin/sh -e /var/tmp/rpm-tmp.68255
+ umask 022
+ cd /scratch/local/home/fperez/tmp/lsrc/matplotlib/build/bdist.linux-i686/rpm/BUILD
+ cd matplotlib-0.87.2dev_r2151
+ LANG=C
+ export LANG
+ unset DISPLAY
+ env 'CFLAGS=-O2 -g -pipe -m32 -march=i386 -mtune=pentium4' python setup.py build
pygtk present but import failed
Using default library and include directories for Tcl and Tk because a
Tk window failed to open. You may need to define DISPLAY for Tk to work
so that setup can determine where your libraries are located.
(setup.py:31070): Gtk-WARNING **: cannot open display:
error: Bad exit status from /var/tmp/rpm-tmp.68255 (%build)
It's really unfortunate that bdist_rpm stopped working, because it is really a tremendous help for those who want to distribute hand-made builds in their local environments, without having to wait for the upstream distributors to make official releases.
Up to 0.83.2 (last I had upgraded) this worked without a hitch.
Cheers,
f