matplotlib-devel Mailing List for matplotlib (Page 3)

Thanks for the report.
It seems that the clipping rectangles were applied additively, rather 
than being set and removed for each axes.
This is now fixed in SVN.
Mike
Nathaniel Smith wrote:
> I ran into a very curious bug tonight, where if I
> -- had multiple axes in a figure
> -- and they had axison=False
> -- and there was a patch or line in each axes
> -- and there was an image in each axes
> Then the image is not rendered (or, after some fiddling with how the
> subplots overlap, is sometimes partially rendered).
>
> It took a few hours to isolate :-(.
>
> I tried the GTKCairo and GTKAgg backends; the Cairo backend shows the
> bug, while the Agg backend renders it correctly.
>
> This is with matplotlib 0.98.5.2, running on Linux x86-64.
>
> Minimal code to reproduce the bug is:
> --------
> from matplotlib import patches, pyplot
> def bug():
> f = pyplot.figure()
> a1 = f.add_axes([0, 0, 0.4, 0.9])
> a2 = f.add_axes([0.5, 0, 0.4, 0.9])
> a3 = f.add_axes([0.2, 0.2, 0.4, 0.9])
> for a in [a1, a2, a3]:
> # This shows up in axis 1, but not axis 2, and only partially in axis 3:
> a.imshow(np.arange(100).reshape(10, 10),
> extent=(-1, 1, 1, -1))
> # If you comment out either of these lines, then it works properly:
> a.axison = False
> a.plot([0, 0], [1, 1])
> pyplot.draw()
> -------
>
> Renders with agg and cairo are attached for comparison. Note that in
> the cairo rendering, axes 1 is drawn correctly, axes 2 is not drawn at
> all, and the only part of axes 3 that is drawn is that part that
> overlaps axes 2.
>
> -- Nathaniel
> 
>
> ------------------------------------------------------------------------
>
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> ------------------------------------------------------------------------
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> 
-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

Sherif Ahmed wrote:
>
> Hello all,
>
> I am using matplotlib in order to generate a scientific drawing called 
> "Smith Chart". It consists of many shifted circles drawn in polar 
> plot. This chart is widely used in electrical engineering field.
>
> I am facing a problem now with the new version of matplotlib. After 
> trying around I figured out that the plot function does not connect 
> the given points in straight lines however by a circle or a circle 
> sector. This causes a very wrong drawing and producing parasitic, 
> false, circles when the points are to cross the theta=180° line.
>
You can turn off this feature by passing "resolution=1" to the polar() 
method. This is the default in SVN versions of matplotlib, and will be 
in the next releases.
You've clearly done a lot of work on the Smith chart plotting already... 
It would be great to package that code into something for general use 
and include in the matplotlib core.
Mike
>
>
> ------------------------------------------------------------------------
>
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> ------------------------------------------------------------------------
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

I ran into a very curious bug tonight, where if I
 -- had multiple axes in a figure
 -- and they had axison=False
 -- and there was a patch or line in each axes
 -- and there was an image in each axes
Then the image is not rendered (or, after some fiddling with how the
subplots overlap, is sometimes partially rendered).
It took a few hours to isolate :-(.
I tried the GTKCairo and GTKAgg backends; the Cairo backend shows the
bug, while the Agg backend renders it correctly.
This is with matplotlib 0.98.5.2, running on Linux x86-64.
Minimal code to reproduce the bug is:
--------
from matplotlib import patches, pyplot
def bug():
 f = pyplot.figure()
 a1 = f.add_axes([0, 0, 0.4, 0.9])
 a2 = f.add_axes([0.5, 0, 0.4, 0.9])
 a3 = f.add_axes([0.2, 0.2, 0.4, 0.9])
 for a in [a1, a2, a3]:
 # This shows up in axis 1, but not axis 2, and only partially in axis 3:
 a.imshow(np.arange(100).reshape(10, 10),
 extent=(-1, 1, 1, -1))
 # If you comment out either of these lines, then it works properly:
 a.axison = False
 a.plot([0, 0], [1, 1])
 pyplot.draw()
-------
Renders with agg and cairo are attached for comparison. Note that in
the cairo rendering, axes 1 is drawn correctly, axes 2 is not drawn at
all, and the only part of axes 3 that is drawn is that part that
overlaps axes 2.
-- Nathaniel

#######################################################################
#
# $Id: PlotSmith.py,v 1.3 2008年08月18日 06:13:14 lorenz Exp $
# 
# Copyright (C) 2004-2008 Petr Lorenz
# All rights reserved.
# 
# ##### BEGIN LICENSE BLOCK #####
#
# Version: MPL 1.1 / GPL 2.0 / LGPL 2.1
#
# The contents of this file are subject to the Mozilla Public License
# Version 1.1 (the "License"); you may not use this file except in
# compliance with the License. You may obtain a copy of the License at
# http://www.mozilla.org/MPL/
# 
# Software distributed under the License is distributed on an "AS IS"
# basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the
# License for the specific language governing rights and limitations
# under the License.
# 
# The Original Code is Petr Lorenz emGine Graphical User Interface (GUI).
# 
# The Initial Developer of the Original Code is Petr Lorenz.
# Portions created by the Initial Developer are Copyright (C) 2004-2008.
# All Rights Reserved.
#
# Contributor(s): Sherif Sayed Ahmed
# 
# Alternatively, the contents of this file may be used under the terms of
# either the GNU General Public License Version 2 or later (the "GPL"), or the
# GNU Lesser General Public License Version 2.1 or later (the "LGPL"), in which
# case the provisions of the GPL or the LGPL are applicable instead of those
# above. If you wish to allow use of your version of this file only under the
# terms of either the GPL or the LGPL and not to allow others to use your
# version of this file under the MPL, indicate your decision by deleting the
# provisions above and replace them with the notice and other provisions
# required by the GPL or LGPL. If you do not delete the provisions above, a
# recipient may use your version of this file under the terms of any one of the
# MPL License, the GPL or the LGPL.
#
# ##### END LICENSE BLOCK #####
#
#######################################################################
# 
# $Log: PlotSmith.py,v $
# Revision 1.3 2008年08月18日 06:13:14 lorenz
# Changes related to 0.7.5 testing version:
# - new docking window manager
# - changed calculation of S-Parameters
# - triangulation of polygons
#
# Revision 1.2 2008年04月07日 05:09:35 lorenz
# Smith diagram integration.
#
# Revision 1.1 2008年03月28日 06:18:27 lorenz
# Initial commit.
#
#
#######################################################################
#
# March 2008
#
# 2D plotting with matplotlib
#
import wx
from matplotlib.backends.backend_wxagg import FigureCanvasWxAgg as FigureCanvas
from matplotlib.backends.backend_wx import NavigationToolbar2Wx
from matplotlib.figure import Figure
##import XYDataSource
# to calculate the phases
from numpy import *
##def phase(num):
## return math.atan2(num.imag, num.real)
## 
class PlotSmith:
 def __init__(self, master):
 self.hold = 0
 
 # create the matplotlib-based Plot
 self.figure = Figure(facecolor = 'w')
 
 self.figure_canvas = FigureCanvas(master, -1, self.figure)
 self.hide() # hide the widget
 def clear(self):
 self.figure.clf()
 def hold_on(self):
 self.hold = True
 self.axes.hold(True)
 def hold_off(self):
 self.hold = False
 self.axes.hold(False)
 def set_dimensions(self, x1, y1, x2, y2):
 self.figure_canvas.SetDimensions(x1, y1, x2, y2)
 def show(self):
 self.figure_canvas.Show(True)
 def hide(self):
 self.figure_canvas.Show(False)
 def refresh(self):
 # Q&D refresh
 self.hide()
 self.show()
 def set_legend(self, legend):
 self.axes.set_title(legend, fontsize =20)
 def set_legend_01(self, legend = None):
 #ToDo: autoscale the figure windows to allow good view for the legend box
 
## self.axes.legend(legend)
 self.axes.legend(handlelen=0.05, loc=(1.06, 0.85), shadow=True)
## self.axes.autoscale_view
 def plot_data(self, real_values, imag_values , freq_values, title = "No data name"):
 
 if (len(real_values) != len(imag_values)):
 print "!! Error! Something is wrong with your data to plot"
 return
 if (len(real_values) != len(freq_values)):
 print "!! Error! Something is wrong with your data to plot"
 return
 # convert to numpy array
 data = array(real_values, dtype=complex) 
 data.imag = imag_values
 
 if not self.hold:
 self.figure.clf()
 self.axes = self.figure.add_axes([0.1,0.1,0.8,0.8], projection='polar', aspect='equal')
 
 
 
 # plot smithchart circles
 # -----------------------
 self.plotsmithcircles()
 
 # Plot the data
 #-------------- 
 self.axes.plot(angle(data),abs(data),label=title,linewidth = 2,zorder=10)
 
 #self.axes.set_title( "Smith chart" , fontsize =20)
 
 # Show freq limits
 #-----------------
 self.axes.plot([angle(data[0])],[abs(data[0])],'oc',linewidth = 5,zorder=10)
 self.axes.plot([angle(data[len(data)-1])],[abs(data[len(data)-1])],'sm',linewidth = 5,zorder=10)
 # Disable Polar grid
 #------------------- 
 self.axes.set_rgrids([1],['',''])
 self.axes.set_thetagrids([0,180],['',''])
 self.axes.grid(False)
 # Set the scale of smith chart
 #-----------------------------
 self.axes.set_rmax(1)
 
 
 def plotsmithcircles(self):
 linetype = 'k'
 linewidth = 0.5
 linewidth2 = 1.5
 # plot R circle 
 r_array = (0.0, 0.2, 0.4, 0.7, 1.0, 1.4, 2.0, 3.0, 5.0)
 z = zeros((1,2000),complex)
 z.imag = arange(-50,50,0.05) 
 x_shift = 1e-3 # can be 1e-3 but not zero
 for r in r_array:
 z.real = r
 gamma_r = transpose((z-1)/(z+1))
 
 if r==1:
 self.axes.plot(angle(gamma_r), abs(gamma_r), linetype,linewidth = linewidth2,zorder=0)
 else:
 self.axes.plot(angle(gamma_r), abs(gamma_r), linetype,linewidth = linewidth,zorder=0)
 
 if not r==0:
 self.axes.text(angle((r+x_shift*1j-1)/(r+x_shift*1j+1)), 1e-6+abs((r+x_shift*1j-1)/(r+x_shift*1j+1)), "%.1f" %(r), backgroundcolor='white', alpha=1, horizontalalignment='center', verticalalignment='center', rotation=0) 
 
 # plot X circle 
 x_array = (0.2, 0.4, 0.6, 0.8, 1.0, 1.4, 2.0, 3.0, 5.0, 10.0)
 z = zeros((1,1000),complex)
 z.real = arange(0, 100, 0.1)
 for x in x_array:
 z.imag = x
 gamma_x = transpose((z-1)/(z+1))
 
 if x==1:
 self.axes.plot(angle(gamma_x),abs(gamma_x), linetype,linewidth = linewidth2,zorder=0)
 else:
 self.axes.plot(angle(gamma_x),abs(gamma_x), linetype,linewidth = linewidth,zorder=0)
 
 
 self.axes.text(angle((x*1j-1)/(x*1j+1)),1.05,"%.1f" %(x),horizontalalignment='center',verticalalignment='center',rotation=angle((x*1j-1)/(x*1j+1),'Degrees')-90)
 
 for x in multiply(-1,x_array):
 z.imag = x
 gamma_x = transpose((z-1)/(z+1))
 
 if x==-1:
 self.axes.plot(angle(gamma_x),abs(gamma_x), linetype,linewidth = linewidth2,zorder=0)
 else:
 self.axes.plot(angle(gamma_x),abs(gamma_x), linetype,linewidth = linewidth,zorder=0)
 
 self.axes.text(angle((x*1j-1)/(x*1j+1)),1.05,"%.1f" %(x),horizontalalignment='center',verticalalignment='center',rotation=angle((x*1j-1)/(x*1j+1),'Degrees')+90)
 
 # plot X=0 line
 self.axes.plot([-pi , 0],[1 , 1], linetype,linewidth = linewidth2 ,zorder=0)
 self.axes.text(-pi ,1.0,'0',horizontalalignment='center',verticalalignment='center',rotation = 0 , backgroundcolor='white',fontsize=12)
 
 # plot infinite symbol
 self.axes.text(0 ,1.0,'$\infty$',horizontalalignment='center',verticalalignment='center',rotation = 0 , backgroundcolor='white',fontsize=12)
 def plot_dummy(self):
 r1 = transpose(.1+arange ( 0 , 0.7 , 0.001))
 theta1 = -1.5 * pi *r1
 freq1 = r1*10e9
 data1 = multiply(r1,exp(1j*theta1))
 self.plot_data(data1.real, data1.imag,freq1,'my first data')
 
 self.hold_on()
 r2 = transpose(arange ( 0 , 0.9 , 0.001))
 theta2 = +2 * pi *r2
 freq2 = r2*10e9
 data2 = multiply(r2,exp(1j*theta2))
## self.plot_data(data2.real, data2.imag,freq2,'my second data')
## self.plot_data([0.4 ,0.2],[-0.5,0.5] ,[1,2],'my third data')
 
 self.set_legend("Test Smith Chart Plot")
 self.set_legend_01()
## r = transpose(.1+arange ( 0 , 0.7 , 0.001))
## theta = -4.5 * pi *r
## freq = r*10e9
## data = multiply(r,exp(1j*theta))
##
## self.plot_data(data.real, data.imag,freq,'my first data')
## 
## self.hold_on()
##
##
## r = transpose(arange ( 0 , 0.9 , 0.001))
## theta = +2 * pi *r
## freq = r*10e9
## data = multiply(r,exp(1j*theta))
##
## self.plot_data(data.real, data.imag,freq,'my second data')
## 
## self.set_legend()
###############################################
if __name__ == '__main__':
 print "Testing PlotSmith Module..."
 app = wx.PySimpleApp()
 frame = wx.Frame(None, -1, "Testing PlotSmith Module", size = (800, 600))
 frame.Show(True)
 PlotSmith = PlotSmith(frame)
 PlotSmith.plot_dummy()
 PlotSmith.show()
 app.MainLoop()
 app.Destroy() 

Hi all,
I reworked the code in axis3d so that the XYZ-planes are always behind
the object you're plotting. I also updated the label/ticks drawing a
bit and dropped a lot of unnecessary code. I pushed it to my git repo
at http://qtwork.nano.tudelft.nl/cgi-bin/gitweb.cgi?p=users/rwh/mplot3d;a=summary
Regards,
Reinier
On Wed, Mar 11, 2009 at 11:22 PM, Reinier Heeres <re...@he...> wrote:
> Hi Jon,
>
> Good point, I forgot about that!
>
> It's available for cloning now: git clone
> http://qtwork.nano.tudelft.nl/public_git/users/rwh/mplot3d
>
> Cheers,
> Reinier
>
> On Wed, Mar 11, 2009 at 6:43 PM, Jonathan Taylor
> <jon...@ut...> wrote:
>> Hi, that is great! Can you give me a git repository address to pull
>> from? I can't from the web viewer.
>>
>> Thanks,
>> J.
>>
>> On Wed, Mar 11, 2009 at 4:25 AM, Reinier Heeres <re...@he...> wrote:
>>> Hi,
>>>
>>> I updated my patch a bit more, and now all tests are running (try
>>> "python axes3d.py"). Only the contourf3D is not working correctly yet,
>>> but I'm sure it's fixable soon. There are also some obvious bugs (e.g.
>>> the semi-3D histograms are not depth-sorted).
>>>
>>> Anyway, I have applied the commit in a different git repo that also
>>> has gitweb.cgi for viewing:
>>> http://qtwork.nano.tudelft.nl/cgi-bin/gitweb.cgi?p=users/rwh/mplot3d;a=summary
>>>
>>> Jon, I got rid of the spurious commit-and-revert entries but included
>>> your latest commits; perhaps you can clone from this tree now?
>>>
>>> Although I've not had a close look at the BSD license it definitely
>>> sounds like a good idea to add it if it applies to the original code.
>>> Shall we try to work to some sort of easily-installable form of the
>>> again-working code?
>>>
>>> Regards,
>>> Reinier
>>>
>>> On Mon, Mar 9, 2009 at 3:45 AM, Jonathan Taylor
>>> <jon...@ut...> wrote:
>>>> Hi Reinier,
>>>>
>>>> Awesome. Those plots are making me smile! I also agree with your
>>>> refactoring and have applied your patch to my git repository.
>>>>
>>>> I agree with you concerning the sympy plotting routines. I think what
>>>> we have here is quite flexible and does a very good job of replicating
>>>> the equivalent functionality of MATLAB. I think it would be a huge
>>>> effort trying to make 2D plots and 3D plots look consistent if another
>>>> approach was taken. Indeed, this is a desirable characteristic. In
>>>> addition, the code is actually very short and easy to maintain. Given
>>>> that matplotlib has had trouble maintaining 3D code in the past, it
>>>> might not be a good idea to switch to a more complicated codebase.
>>>>
>>>> You should grab some of my more recent changes as I have added a few
>>>> more fixes. Most importantly, if you reuse the same figure, the old
>>>> event handlers will still attached preventing Axes objects from dieing
>>>> and causing interactive manipulation of the plots to be very sluggish.
>>>> Also, in terms of performance, I have found that switching to TkAgg
>>>> from GTKAgg was helpful.
>>>>
>>>> Also, I think the original code from John Porter was under a BSD
>>>> license. I am thinking of adding our names and the BSD license to the
>>>> top of each file to protect it while its not officially part of
>>>> matplotlib. What do you think?
>>>>
>>>> Best,
>>>> Jonathan.
>>>
>>> --
>>> Reinier Heeres
>
> --
> Reinier Heeres
-- 
Reinier Heeres
Waalstraat 17
2515 XK Den Haag
The Netherlands
Tel: +31 6 10852639

Hello everyone. I'm having some trouble compiling setup.py for Matplotlib. I'm trying to run it on Cygwin.
$ uname -a
CYGWIN_NT-5.1 name 1.5.25(0.156/4/2) 2008年06月12日 19:34 i686 Cygwin
$ gcc --version
gcc (GCC) 3.4.4 (cygming special, gdc 0.12, using dmd 0.125)
Copyright (C) 2004 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
I have Python 2.5.2 installed, as well as libpng, freetype2, and zlib, although for some reason the compiler cannot determine the version. I got Matplotlib from sourceforge. Here is the output when I run the code:
$ python setup.py build
============================================================================
BUILDING MATPLOTLIB
 matplotlib: 0.98.5.2
 python: 2.5.2 (r252:60911, Dec 2 2008, 09:26:14) [GCC
 3.4.4 (cygming special, gdc 0.12, using dmd 0.125)]
 platform: cygwin
REQUIRED DEPENDENCIES
 numpy: 1.2.1
 freetype2: found, but unknown version (no pkg-config)
OPTIONAL BACKEND DEPENDENCIES
 libpng: found, but unknown version (no pkg-config)
Test
Traceback (most receent call last):
 File "setup.py", line 134, in <module>
 if check_for_tk() or (options['build_tkagg'] is True):
 File "/home/firstname lastname/matplotlib-0.98.5.2/setupext.py", line 782, in check
_for_tk
 explanation = add_tk_flags(module)
 File "/home/firstname lastname/matplotlib-0.98.5.2/setupext.py", line 1043, in add_
tk_flags
 result = parse_tcl_config(tcl_lib_dir, tk_lib_dir)
 File "/home/firstname lastname/matplotlib-0.98.5.2/setupext.py", line 900, in parse
_tcl_config
 tk_lib = tk_vars.get("default", "TK_LIB_SPEC")[1:-1].split()[0][2:]
IndexError: list index out of range
It seems as though the error is in line 900 of setupext.py, but I don't have quite enough programming knowledge to be certain. Any help anyone could give me would be greatly appreciated.
Thanks!
_________________________________________________________________
Hotmail® is up to 70% faster. Now good news travels really fast. 
http://windowslive.com/online/hotmail?ocid=TXT_TAGLM_WL_HM_70faster_032009 

Hi all,
[ apologies for the semi-spam, I'll keep this brief and expect all
replies off-list ]
IPython is a project that many of you on this list are likely to use
in your daily work, either directly or indirectly (if you've embedded
it or used it as a component of some other system). I would simply
like to ask you, if IPython has been significantly useful for a
project you use, lead, develop, etc., to let me know.
For legal/professional reasons, I need to gather information about who
has found IPython to be of value. I started IPython as a toy
'afternoon hack' in late 2001, and today it continues to grow, as the
nicely summarized Ohloh stats show: https://www.ohloh.net/p/ipython
(obviously, this is now the result of the work of many, not just
myself, as is true of any healthy open source project as it grows).
But I have never systematically tracked its impact, and now I need to
do so.
So, if you have used IPython and it has made a significant
contribution to your project, work, research, company, whatever, I'd
be very grateful if you let me know. A short paragraph on what this
benefit has been is all I ask. Once I gather any information I get, I
would contact directly some of the responders to ask for your
authorization before quoting you.
I should stress that any information you give me will only go in a
documentation packet in support of my legal/residency process here in
the USA (think of it as an oversized, obnoxiously detailed CV that
goes beyond just publications and regular academic information).
To keep traffic off this list, please send your replies directly to
me, either at this address or my regular work one:
Fer...@be...
In advance, many thanks to anyone willing to reply. I've never asked
for anything in return for working on IPython and the ecosystem of
scientific Python tools, but this is actually very important, so any
information you can provide me will be very useful.
Best regards,
Fernando Perez.

Paul Kienzle wrote:
> On Mar 12, 2009, at 9:49 AM, Michael Droettboom wrote:
>
> 
>> We've done some experiments with Enthought Traits at various times to
>> address this issue. There were always various obstacles to making it
>> work, but it may be worth another look. Traits has its nice auto- 
>> built
>> property editors (that may address your request), but it would also
>> address one of my long-standing niggles that properties of graphs are
>> often checked far too late and the error messages presented to the 
>> user
>> are very obscured because of it.
>>
>> Of course, all that is a major undertaking -- basically rewriting all
>> the getters and setters on the artist classes to use traits -- but I
>> could see it having quite the payoff in the end.
>>
>> 
>
> I'm not sure if traits can do it.
> 
Why not? Everything you describe below screams "traits" to me.
> I would like to see CSS-like properties, so that when I change the 
> font size on the graph, the title, which is size +2, and the legend 
> which is size -1 also get updated. I can imagine changing the font 
> for an axes, for a figure or for all figures. The latter should be 
> stored in a resource file so it doesn't have to be done every 
> session. Properties which are not set should look up their values 
> elsewhere; if the property of some object has been specialized, then 
> it should not change when the figure properties are set. Properties 
> for printed figures may be different from properties of figures on 
> the screen, e.g., because the printer is monochrome.
>
> Eventually I would like interactive editing of properties by point 
> and click. Particularly for plotted data the question will be 
> whether the change applies to the data point only, to its line, or to 
> all lines on the graph, to all graphs on the figure, or to all 
> figures, depending on the property. Doing this without cluttering 
> the UI will be a challenge.
> 

On Mar 12, 2009, at 9:49 AM, Michael Droettboom wrote:
> We've done some experiments with Enthought Traits at various times to
> address this issue. There were always various obstacles to making it
> work, but it may be worth another look. Traits has its nice auto- 
> built
> property editors (that may address your request), but it would also
> address one of my long-standing niggles that properties of graphs are
> often checked far too late and the error messages presented to the 
> user
> are very obscured because of it.
>
> Of course, all that is a major undertaking -- basically rewriting all
> the getters and setters on the artist classes to use traits -- but I
> could see it having quite the payoff in the end.
>
I'm not sure if traits can do it.
I would like to see CSS-like properties, so that when I change the 
font size on the graph, the title, which is size +2, and the legend 
which is size -1 also get updated. I can imagine changing the font 
for an axes, for a figure or for all figures. The latter should be 
stored in a resource file so it doesn't have to be done every 
session. Properties which are not set should look up their values 
elsewhere; if the property of some object has been specialized, then 
it should not change when the figure properties are set. Properties 
for printed figures may be different from properties of figures on 
the screen, e.g., because the printer is monochrome.
Eventually I would like interactive editing of properties by point 
and click. Particularly for plotted data the question will be 
whether the change applies to the data point only, to its line, or to 
all lines on the graph, to all graphs on the figure, or to all 
figures, depending on the property. Doing this without cluttering 
the UI will be a challenge.
- Paul

We've done some experiments with Enthought Traits at various times to 
address this issue. There were always various obstacles to making it 
work, but it may be worth another look. Traits has its nice auto-built 
property editors (that may address your request), but it would also 
address one of my long-standing niggles that properties of graphs are 
often checked far too late and the error messages presented to the user 
are very obscured because of it.
Of course, all that is a major undertaking -- basically rewriting all 
the getters and setters on the artist classes to use traits -- but I 
could see it having quite the payoff in the end.
Mike
João Luís Silva wrote:
> Paul Kienzle wrote:
> 
>> Hi,
>>
>> What's the status of interactive property editors for mpl graphs?
>>
>> I would like something that would allow me to change properties such 
>> as the size and position of the graph, grids, scales, ranges, colors, 
>> symbols, line styles, fonts, etc., and add annotations. Some of this 
>> already exists, but allowing users to enter specific values will need 
>> an underlying widget toolkit.
>>
>> Does anybody have anything that I can build on for wx?
>>
>> 
>
> I though about making such a program but concluded it would be a major 
> undertaking. I considered using GTK because that's what I use, but 
> otherwise any toolkit will do. I still have some major unresolved design 
> issues to implement such an application:
>
> - How would the state of the editor be saved? In a new file type (in 
> json for example)? Is there any standard format for this? If it was 
> feasible I'd like to import and export small python scripts, but the 
> import capabilities seem unlikely.
>
> - Mpl is very flexible (just look at the gallery). Would the editor be 
> limited to a subset of the capabilities or the objective would be to 
> take mpl to the limit? Including subplots? and heterogeneous graphics? 
> The interface could get very complex very quickly indeed.
>
> - I seem to recall an open source graphics application along these 
> lines, but can't remember its name (maybe SciGraphica).
>
> If someone is working on such a thing, or if you want to make one I 
> could tinker a bit, but I really don't have enough time to start a major 
> application. BTW I'm not a mpl developer, just a satisfied user :)
>
> Regards,
> João Silva
>
>
> ------------------------------------------------------------------------------
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> 
-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

Paul Kienzle wrote:
> Hi,
> 
> What's the status of interactive property editors for mpl graphs?
> 
> I would like something that would allow me to change properties such 
> as the size and position of the graph, grids, scales, ranges, colors, 
> symbols, line styles, fonts, etc., and add annotations. Some of this 
> already exists, but allowing users to enter specific values will need 
> an underlying widget toolkit.
> 
> Does anybody have anything that I can build on for wx?
> 
I though about making such a program but concluded it would be a major 
undertaking. I considered using GTK because that's what I use, but 
otherwise any toolkit will do. I still have some major unresolved design 
issues to implement such an application:
- How would the state of the editor be saved? In a new file type (in 
json for example)? Is there any standard format for this? If it was 
feasible I'd like to import and export small python scripts, but the 
import capabilities seem unlikely.
- Mpl is very flexible (just look at the gallery). Would the editor be 
limited to a subset of the capabilities or the objective would be to 
take mpl to the limit? Including subplots? and heterogeneous graphics? 
The interface could get very complex very quickly indeed.
- I seem to recall an open source graphics application along these 
lines, but can't remember its name (maybe SciGraphica).
If someone is working on such a thing, or if you want to make one I 
could tinker a bit, but I really don't have enough time to start a major 
application. BTW I'm not a mpl developer, just a satisfied user :)
Regards,
João Silva

Hi Jon,
Good point, I forgot about that!
It's available for cloning now: git clone
http://qtwork.nano.tudelft.nl/public_git/users/rwh/mplot3d
Cheers,
Reinier
On Wed, Mar 11, 2009 at 6:43 PM, Jonathan Taylor
<jon...@ut...> wrote:
> Hi, that is great! Can you give me a git repository address to pull
> from? I can't from the web viewer.
>
> Thanks,
> J.
>
> On Wed, Mar 11, 2009 at 4:25 AM, Reinier Heeres <re...@he...> wrote:
>> Hi,
>>
>> I updated my patch a bit more, and now all tests are running (try
>> "python axes3d.py"). Only the contourf3D is not working correctly yet,
>> but I'm sure it's fixable soon. There are also some obvious bugs (e.g.
>> the semi-3D histograms are not depth-sorted).
>>
>> Anyway, I have applied the commit in a different git repo that also
>> has gitweb.cgi for viewing:
>> http://qtwork.nano.tudelft.nl/cgi-bin/gitweb.cgi?p=users/rwh/mplot3d;a=summary
>>
>> Jon, I got rid of the spurious commit-and-revert entries but included
>> your latest commits; perhaps you can clone from this tree now?
>>
>> Although I've not had a close look at the BSD license it definitely
>> sounds like a good idea to add it if it applies to the original code.
>> Shall we try to work to some sort of easily-installable form of the
>> again-working code?
>>
>> Regards,
>> Reinier
>>
>> On Mon, Mar 9, 2009 at 3:45 AM, Jonathan Taylor
>> <jon...@ut...> wrote:
>>> Hi Reinier,
>>>
>>> Awesome. Those plots are making me smile! I also agree with your
>>> refactoring and have applied your patch to my git repository.
>>>
>>> I agree with you concerning the sympy plotting routines. I think what
>>> we have here is quite flexible and does a very good job of replicating
>>> the equivalent functionality of MATLAB. I think it would be a huge
>>> effort trying to make 2D plots and 3D plots look consistent if another
>>> approach was taken. Indeed, this is a desirable characteristic. In
>>> addition, the code is actually very short and easy to maintain. Given
>>> that matplotlib has had trouble maintaining 3D code in the past, it
>>> might not be a good idea to switch to a more complicated codebase.
>>>
>>> You should grab some of my more recent changes as I have added a few
>>> more fixes. Most importantly, if you reuse the same figure, the old
>>> event handlers will still attached preventing Axes objects from dieing
>>> and causing interactive manipulation of the plots to be very sluggish.
>>> Also, in terms of performance, I have found that switching to TkAgg
>>> from GTKAgg was helpful.
>>>
>>> Also, I think the original code from John Porter was under a BSD
>>> license. I am thinking of adding our names and the BSD license to the
>>> top of each file to protect it while its not officially part of
>>> matplotlib. What do you think?
>>>
>>> Best,
>>> Jonathan.
>>
>> --
>> Reinier Heeres
-- 
Reinier Heeres
Waalstraat 17
2515 XK Den Haag
The Netherlands
Tel: +31 6 10852639

Eric Firing wrote:
> I have applied your patch, plus related changes to backend_wx and 
> backend_wxagg as suggested by Chris, to the 0.98.5 maintenance branch, 
> and then used svnmerge to propagate the changes to the trunk. (In other 
> words, I judged the changes to be a bug fix rather than a new feature.)
Great, thanks! thanks for taking care of us wx users...
-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 Wed, Mar 11, 2009 at 20:49, Eric Firing <ef...@ha...> wrote:
> I have applied your patch, plus related changes to backend_wx and
> backend_wxagg as suggested by Chris, to the 0.98.5 maintenance branch, and
> then used svnmerge to propagate the changes to the trunk. (In other words,
> I judged the changes to be a bug fix rather than a new feature.)
Yes, indeed they are a bugfix... hence: thanks for merging them!! :)
Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

Sandro Tosi wrote:
> On Fri, Mar 6, 2009 at 22:24, Sandro Tosi <mo...@de...> wrote:
>> On Fri, Mar 6, 2009 at 22:12, Sandro Tosi <mo...@de...> wrote:
>>>>>> import wxversion
>>>>>> wxversion.select('2.8')
>>>>>> from wx import *
>>>>>> wx.__version__
>>> '2.8.7.1'
>>>
>>> That solves the problem of multi-wx on a system.
>>>
>>> What do you think about adding those 2 line into wx examples?
>> Moreover, I will provide a patch to move from
> 
> Here it is the promised patch (sorry for the late, that proves how
> busy I am these days).
> 
> It uses the 'wxversion.ensureMinimal' function as Chris pointed out,
> and move from "from wx import *" to "import wx".
> 
> I tested them on a sys (Debian sid) with both wx2.6 and wx2.8: before
> the patch the examples goes in abort, after they select wx2.8 and uses
> it displaying the windows (even though ex2 and 3 seems a little "too
> compress" do not know if it's due to code or patch ;) ).
Sandro,
I have applied your patch, plus related changes to backend_wx and 
backend_wxagg as suggested by Chris, to the 0.98.5 maintenance branch, 
and then used svnmerge to propagate the changes to the trunk. (In other 
words, I judged the changes to be a bug fix rather than a new feature.)
Eric

a
On Wed, Mar 11, 2009 at 1:29 PM, Jonathan Taylor <
jon...@ut...> wrote:
> Hi John,
>
> You should be able to check out a copy from my git repo via
>
> git clone http://jonathantaylor.ca/mplot3d.git
> cd mplot3d
> git pull
OK thanks.
Just a word of warning. It appears you are developing against an older
version of mpl (0.98?). For example, matplotlib.text.TextWithDash used in
axis3d has been removed from svn HEAD. The attribute self._autoscaleon in
axes3d is no longer available (use self.get_autoscale_on())
As soon as feasible, I suggest getting a svn co of mpl HEAD and working with
that, to speed integration with the main line. You could resurrect
TextWithDash internally for mplot3d if you want, but we found it difficult
to maintain.
JDH

Hi John,
You should be able to check out a copy from my git repo via
git clone http://jonathantaylor.ca/mplot3d.git
cd mplot3d
git pull
I am missing Reiniers final update though but you should be able to
run demo.py and the first few examples in the __name__ == '__main__'
clause of axes3d.py.
Best, J.
On Wed, Mar 11, 2009 at 2:21 PM, John Hunter <jd...@gm...> wrote:
>
>
> On Wed, Mar 11, 2009 at 3:25 AM, Reinier Heeres <re...@he...> wrote:
>>
>> Hi,
>>
>> I updated my patch a bit more, and now all tests are running (try
>> "python axes3d.py"). Only the contourf3D is not working correctly yet,
>> but I'm sure it's fixable soon. There are also some obvious bugs (e.g.
>> the semi-3D histograms are not depth-sorted).
>>
>> Anyway, I have applied the commit in a different git repo that also
>> has gitweb.cgi for viewing:
>>
>> http://qtwork.nano.tudelft.nl/cgi-bin/gitweb.cgi?p=users/rwh/mplot3d;a=summary
>>
>> Jon, I got rid of the spurious commit-and-revert entries but included
>> your latest commits; perhaps you can clone from this tree now?
>>
>> Although I've not had a close look at the BSD license it definitely
>> sounds like a good idea to add it if it applies to the original code.
>> Shall we try to work to some sort of easily-installable form of the
>> again-working code?
>
> One thing you can do is send a patch against lib/mpl-toolkits and I'll apply
> it to svn trunk.
>
> I was briefly scrolling through the recent diffs on art3d, and noticed
>
> +  try:
> +    zs = float(zs)
> +    zs = [zs for i in range(len(paths))]
> +  except:
> +    pass
>
> Except in very special cases, we do not allow blanket excepts -- eg you
> should catch explicitly the error you are trying to trap. Also, it is
> usually better to try just the part you are trying to catch and then do the
> rest in an else. So if you are trying to catch the case where zs is not a
> float
>
> try:
>   zs = float(zs)
> except TypeError:
>   pass
> else:
>   zs = [zs for i in range(len(paths))]
>
>
> Also, again I am not excatly sure what you are trying to do here, mpl has
> "duck typing" helpers to test whether something is iterable or num-like. So
> you can do
>
>
>  import matplotlib.cbook as cbook
>  if not cbook.iterable(zs):
>    zs =float(zs)
>    zs = [zs for i in range(len(paths))]
>
> Anyway -- great work so far. I'm having trouble making a git co work so I
> am looking forward to testing this when you have a snapshot or svn diff.
>
> JDH
>
> ------------------------------------------------------------------------------
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>

On Wed, Mar 11, 2009 at 3:25 AM, Reinier Heeres <re...@he...> wrote:
> Hi,
>
> I updated my patch a bit more, and now all tests are running (try
> "python axes3d.py"). Only the contourf3D is not working correctly yet,
> but I'm sure it's fixable soon. There are also some obvious bugs (e.g.
> the semi-3D histograms are not depth-sorted).
>
> Anyway, I have applied the commit in a different git repo that also
> has gitweb.cgi for viewing:
>
> http://qtwork.nano.tudelft.nl/cgi-bin/gitweb.cgi?p=users/rwh/mplot3d;a=summary
>
> Jon, I got rid of the spurious commit-and-revert entries but included
> your latest commits; perhaps you can clone from this tree now?
>
> Although I've not had a close look at the BSD license it definitely
> sounds like a good idea to add it if it applies to the original code.
> Shall we try to work to some sort of easily-installable form of the
> again-working code?
One thing you can do is send a patch against lib/mpl-toolkits and I'll apply
it to svn trunk.
I was briefly scrolling through the recent diffs on art3d, and noticed
+ try:
+ zs = float(zs)
+ zs = [zs for i in range(len(paths))]
+ except:
+ pass
Except in very special cases, we do not allow blanket excepts -- eg you
should catch explicitly the error you are trying to trap. Also, it is
usually better to try just the part you are trying to catch and then do the
rest in an else. So if you are trying to catch the case where zs is not a
float
try:
 zs = float(zs)
except TypeError:
 pass
else:
 zs = [zs for i in range(len(paths))]
Also, again I am not excatly sure what you are trying to do here, mpl has
"duck typing" helpers to test whether something is iterable or num-like. So
you can do
 import matplotlib.cbook as cbook
 if not cbook.iterable(zs):
 zs =float(zs)
 zs = [zs for i in range(len(paths))]
Anyway -- great work so far. I'm having trouble making a git co work so I
am looking forward to testing this when you have a snapshot or svn diff.
JDH

Hi,
What's the status of interactive property editors for mpl graphs?
I would like something that would allow me to change properties such 
as the size and position of the graph, grids, scales, ranges, colors, 
symbols, line styles, fonts, etc., and add annotations. Some of this 
already exists, but allowing users to enter specific values will need 
an underlying widget toolkit.
Does anybody have anything that I can build on for wx?
Thanks,
 - Paul

Hi, that is great! Can you give me a git repository address to pull
from? I can't from the web viewer.
Thanks,
J.
On Wed, Mar 11, 2009 at 4:25 AM, Reinier Heeres <re...@he...> wrote:
> Hi,
>
> I updated my patch a bit more, and now all tests are running (try
> "python axes3d.py"). Only the contourf3D is not working correctly yet,
> but I'm sure it's fixable soon. There are also some obvious bugs (e.g.
> the semi-3D histograms are not depth-sorted).
>
> Anyway, I have applied the commit in a different git repo that also
> has gitweb.cgi for viewing:
> http://qtwork.nano.tudelft.nl/cgi-bin/gitweb.cgi?p=users/rwh/mplot3d;a=summary
>
> Jon, I got rid of the spurious commit-and-revert entries but included
> your latest commits; perhaps you can clone from this tree now?
>
> Although I've not had a close look at the BSD license it definitely
> sounds like a good idea to add it if it applies to the original code.
> Shall we try to work to some sort of easily-installable form of the
> again-working code?
>
> Regards,
> Reinier
>
> On Mon, Mar 9, 2009 at 3:45 AM, Jonathan Taylor
> <jon...@ut...> wrote:
>> Hi Reinier,
>>
>> Awesome. Those plots are making me smile! I also agree with your
>> refactoring and have applied your patch to my git repository.
>>
>> I agree with you concerning the sympy plotting routines. I think what
>> we have here is quite flexible and does a very good job of replicating
>> the equivalent functionality of MATLAB. I think it would be a huge
>> effort trying to make 2D plots and 3D plots look consistent if another
>> approach was taken. Indeed, this is a desirable characteristic. In
>> addition, the code is actually very short and easy to maintain. Given
>> that matplotlib has had trouble maintaining 3D code in the past, it
>> might not be a good idea to switch to a more complicated codebase.
>>
>> You should grab some of my more recent changes as I have added a few
>> more fixes. Most importantly, if you reuse the same figure, the old
>> event handlers will still attached preventing Axes objects from dieing
>> and causing interactive manipulation of the plots to be very sluggish.
>> Also, in terms of performance, I have found that switching to TkAgg
>> from GTKAgg was helpful.
>>
>> Also, I think the original code from John Porter was under a BSD
>> license. I am thinking of adding our names and the BSD license to the
>> top of each file to protect it while its not officially part of
>> matplotlib. What do you think?
>>
>> Best,
>> Jonathan.
>
> --
> Reinier Heeres
> Waalstraat 17
> 2515 XK Den Haag
> The Netherlands
>
> Tel: +31 6 10852639
>
> ------------------------------------------------------------------------------
> Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
> powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
> easily build your RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

Hi,
I updated my patch a bit more, and now all tests are running (try
"python axes3d.py"). Only the contourf3D is not working correctly yet,
but I'm sure it's fixable soon. There are also some obvious bugs (e.g.
the semi-3D histograms are not depth-sorted).
Anyway, I have applied the commit in a different git repo that also
has gitweb.cgi for viewing:
http://qtwork.nano.tudelft.nl/cgi-bin/gitweb.cgi?p=users/rwh/mplot3d;a=summary
Jon, I got rid of the spurious commit-and-revert entries but included
your latest commits; perhaps you can clone from this tree now?
Although I've not had a close look at the BSD license it definitely
sounds like a good idea to add it if it applies to the original code.
Shall we try to work to some sort of easily-installable form of the
again-working code?
Regards,
Reinier
On Mon, Mar 9, 2009 at 3:45 AM, Jonathan Taylor
<jon...@ut...> wrote:
> Hi Reinier,
>
> Awesome. Those plots are making me smile! I also agree with your
> refactoring and have applied your patch to my git repository.
>
> I agree with you concerning the sympy plotting routines. I think what
> we have here is quite flexible and does a very good job of replicating
> the equivalent functionality of MATLAB. I think it would be a huge
> effort trying to make 2D plots and 3D plots look consistent if another
> approach was taken. Indeed, this is a desirable characteristic. In
> addition, the code is actually very short and easy to maintain. Given
> that matplotlib has had trouble maintaining 3D code in the past, it
> might not be a good idea to switch to a more complicated codebase.
>
> You should grab some of my more recent changes as I have added a few
> more fixes. Most importantly, if you reuse the same figure, the old
> event handlers will still attached preventing Axes objects from dieing
> and causing interactive manipulation of the plots to be very sluggish.
> Also, in terms of performance, I have found that switching to TkAgg
> from GTKAgg was helpful.
>
> Also, I think the original code from John Porter was under a BSD
> license. I am thinking of adding our names and the BSD license to the
> top of each file to protect it while its not officially part of
> matplotlib. What do you think?
>
> Best,
> Jonathan.
-- 
Reinier Heeres
Waalstraat 17
2515 XK Den Haag
The Netherlands
Tel: +31 6 10852639

On Fri, Mar 6, 2009 at 22:24, Sandro Tosi <mo...@de...> wrote:
> On Fri, Mar 6, 2009 at 22:12, Sandro Tosi <mo...@de...> wrote:
>>>>> import wxversion
>>>>> wxversion.select('2.8')
>>>>> from wx import *
>>>>> wx.__version__
>> '2.8.7.1'
>>
>> That solves the problem of multi-wx on a system.
>>
>> What do you think about adding those 2 line into wx examples?
>
> Moreover, I will provide a patch to move from
Here it is the promised patch (sorry for the late, that proves how
busy I am these days).
It uses the 'wxversion.ensureMinimal' function as Chris pointed out,
and move from "from wx import *" to "import wx".
I tested them on a sys (Debian sid) with both wx2.6 and wx2.8: before
the patch the examples goes in abort, after they select wx2.8 and uses
it displaying the windows (even though ex2 and 3 seems a little "too
compress" do not know if it's due to code or patch ;) ).
HTH, cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

Sandro Tosi wrote:
>>>>>> What do you think about adding those 2 line into wx examples?
>> hmmm - only the examples? or should it be in the wx back-end itself?
>> Maybe at least a version check?
> 
> I'll leave this to the mpl gurus...
fair enough.
> yeah, that's what we need: I got 2 version installed (2.6 and 2.8) and
> here is the output
> In [2]: import wxversion
> 
> In [3]: wxversion.ensureMinimal('2.8')
> 
> In [4]: import wx
> 
> In [5]: wx.__version__
> Out[5]: '2.8.7.1'
> 
> So I'm going to use it in the examples. Thanks for spotting it out!
great -- thanks for working on those -- good examples are key!
> I only hope that 2.8->2.10 (or higher) would not introduce such corner
> cases like in 2.6->2.8.
Less likely, with 2.8, we eliminated the compiled parts of the wx 
back-end, by using some new features.
However, if future versions of wxPython get the new enhanced buffer 
interface, it might be nice to use 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...

On Mon, Mar 9, 2009 at 21:55, Christopher Barker <Chr...@no...> wrote:
> Sandro Tosi wrote:
>>>>>>>> import wxversion
>>>>>>>> wxversion.select('2.8')
>>>>>>>> from wx import *
>>>>>>>> wx.__version__
>>>>> '2.8.7.1'
>>>>>
>>>>> That solves the problem of multi-wx on a system.
>>>>>
>>>>> What do you think about adding those 2 line into wx examples?
>
> hmmm - only the examples? or should it be in the wx back-end itself?
> Maybe at least a version check?
I'll leave this to the mpl gurus...
> Anyway -- certainly the examples
...while I'll concentrate on them :)
>>>> Moreover, I will provide a patch to move from
>>>>
>>>>>>> from wx import *
>>>> to
>>>>>>> import wx
>
> who hoo! thanks!
>
>> AFAIUI, it's not possible to say "2.8+" == "2.8 and all the higher
>> versions",
>
> I think there is:
>
> http://www.wxpython.org/docs/api/wxversion-module.html
>
> you need:
>
> import wxversion
> wxversion.ensureMinimal('2.8')
>
> I think that will do it, but I haven't tested much -- I only have one
> version installed now. If it does work, I say we definitely ue it in the.
>
> Another option is to put it in the wx back-end in a try block:
>
> wxversion.ensureMinimal('2.4')
> Traceback (most recent call last):
>  File "<stdin>", line 1, in <module>
>  File
> "/usr/local/lib/wxPython-unicode-2.8.9.1/lib/python2.5/site-packages/wxversion.py",
> line 181, in ensureMinimal
>   raise AlreadyImportedError("wxversion.ensureMinimal() must be
> called before wxPython is imported")
> wxversion.AlreadyImportedError: wxversion.ensureMinimal() must be called
> before wxPython is imported
>
> which might be the safest, and would catch both pylab use, and people's
> home-written apps that need the wxversion call.
yeah, that's what we need: I got 2 version installed (2.6 and 2.8) and
here is the output
In [1]: import wxversion
In [2]: help(wxversion.ensureMinimal)
In [3]: wxversion.ensureMinimal('2.6')
In [4]: import wx
In [5]: wx.__version__
Out[5]: '2.6.3.2'
and
In [2]: import wxversion
In [3]: wxversion.ensureMinimal('2.8')
In [4]: import wx
In [5]: wx.__version__
Out[5]: '2.8.7.1'
So I'm going to use it in the examples. Thanks for spotting it out!
I only hope that 2.8->2.10 (or higher) would not introduce such corner
cases like in 2.6->2.8.
Cheers,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

On Mon, Mar 9, 2009 at 2:39 PM, Jonathan Taylor
<jon...@ut...> wrote:
> Sure, I thought it was going to the list too ;) So no problem.
>
> I am not sure what you can do with that module. It seems a shame to
> waste. Perhaps it should be split out into a seperate 3d only
> plotting library that cares less about being matplotlib'ish than
> something packaged with MPL would. What do you think?
Yes, we could do that. The problem is that I don't have time to
maintain plotting stuff, so I need to find ways to attract someone
else to take over it. :) So maybe creating some optional addon to
matplotlib, as you say, could attract people's attantion.
Ondrej