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 i
On Mon, Mar 9, 2009 at 21:55, Christopher Barker 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
On Mon, Mar 9, 2009 at 2:39 PM, Jonathan Taylor
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 abou
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. W
On Mon, Mar 9, 2009 at 2:34 PM, Ondrej Certik wrote:
> I posted only to you by a mistake -- can I reply to the list?
Oops, I posted to the list by mistake too -- sorry about it. Anyway,
here is the email that I sent to Jonathan only by a mistake:
On Sun, Mar 8, 2009 at 9:44 PM, Jonathan Taylor
I posted only to you by a mistake -- can I reply to the list?
On Mon, Mar 9, 2009 at 2:20 PM, Jonathan Taylor
wrote:
> I think that it would be a little bit more complicated than that. I
> believe that the current backends act as a canvas that you paint onto.
> I do not think an OpenGL "canvas"
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
