Many moons ago, we talked about doing a bugfix release 0.90.1. Since
there are known bugs in the production release (eg Jeff Peery's recent
plot_date bug) I would like to put out a new release. Any objections?
backend driver looks good.
I've run some tests with memleak_hawaii with the agg backe
On Thursday 31 May 2007 10:27:30 am John Hunter wrote:
> Many moons ago, we talked about doing a bugfix release 0.90.1. Since
> there are known bugs in the production release (eg Jeff Peery's recent
> plot_date bug) I would like to put out a new release. Any objections?
>
> backend driver looks g
John Hunter wrote:
> Many moons ago, we talked about doing a bugfix release 0.90.1. Since
> there are known bugs in the production release (eg Jeff Peery's recent
> plot_date bug) I would like to put out a new release. Any objections?
I'd love to see a new release resolve the wxPython issues. Ha
On 5/31/07, Christopher Barker <[EMAIL PROTECTED]> wrote:
> John Hunter wrote:
> > Many moons ago, we talked about doing a bugfix release 0.90.1. Since
> > there are known bugs in the production release (eg Jeff Peery's recent
> > plot_date bug) I would like to put out a new release. Any objectio
John Hunter wrote:
> So if the wx stuff is ready to
> go, by all means let's check it in and include it, but if not I don't
> see that we need to hold for it.
I think all the real work is done, but I"m not totally sure what's
checked in now. There may be some changes needed to the build scripts s
I'm here. It would be nice to use the pure-python wx so we don't have
to provide separate 2.6 and 2.8 builds.
- Charlie
On 5/31/07, Christopher Barker <[EMAIL PROTECTED]> wrote:
> John Hunter wrote:
> > So if the wx stuff is ready to
> > go, by all means let's check it in and include it, but if
Hi. I've been trying to port an application to older distros such as RH3
without much luck.
I'm using numpy and pylab. I can usually get numpy installed but pylab has lots
of dependencies on gtk2 and other things. What's the minimal backend to use to
eliminate, as much as possible, the dependenc
On May 31, 2007, at 12:42 PM, Christopher Barker wrote:
>
> I think all the real work is done, but I"m not totally sure what's
> checked in now. There may be some changes needed to the build
> scripts so
> that it doesn't try to build the accelerator by default.
I'm not sure either. My modifica
On May 31, 2007, at 12:51 PM, Charlie Moad wrote:
>
> It would be nice to use the pure-python wx so we don't have to
> provide separate 2.6 and 2.8 builds.
At this point it should be possible to include a _wxagg.so built for
wxPython 2.6 and have everything Just Work with 2.8. If mixing
ver
On 5/31/07, Ken McIvor <[EMAIL PROTECTED]> wrote:
> At this point it should be possible to include a _wxagg.so built for
> wxPython 2.6 and have everything Just Work with 2.8. If mixing
> versions causes linking errors it won't be hard to fix in
> backend_wxagg.py.
If we have a pure python wxagg
John Hunter wrote:
> If we have a pure python wxagg implementation that supports blitting,
> eg your Just Work with 2.8 changes, let's not bother building the 2.6
> extension code at all,
I think this is the way to go. Even with 2.6, it's a pain to get MPL to
find the right libs, etc, if there is
On 5/31/07, Christopher Barker <[EMAIL PROTECTED]> wrote:
> John Hunter wrote:
> > If we have a pure python wxagg implementation that supports blitting,
> > eg your Just Work with 2.8 changes, let's not bother building the 2.6
> > extension code at all,
>
> I think this is the way to go. Even with
12 matches
Mail list logo
