On Thu, Apr 9, 2009 at 8:18 PM, Adam Mercer wrote:
> On Thu, Apr 9, 2009 at 13:46, Michael Droettboom wrote:
> > I did a lot of the initial fixes for Python 2.6 within the first week of
> the
> > 2.6.0 release -- they were mostly of the warning/style nature. I've been
> > running it on 2.6 on a
On Thu, Apr 9, 2009 at 13:46, Michael Droettboom wrote:
> I did a lot of the initial fixes for Python 2.6 within the first week of the
> 2.6.0 release -- they were mostly of the warning/style nature. I've been
> running it on 2.6 on and off ever since, so it should be ok. But let us
> know if yo
I did a lot of the initial fixes for Python 2.6 within the first week of
the 2.6.0 release -- they were mostly of the warning/style nature. I've
been running it on 2.6 on and off ever since, so it should be ok. But
let us know if you find anything.
Cheers,
Mike
Adam Mercer wrote:
> On Sun, A
On Sun, Apr 5, 2009 at 16:01, David Moore wrote:
> I've had matplotlib running fine on Python 2.6 since shortly after the Python
> 2.6 release. I run Arch Linux. Are you perhaps looking for Windows builds?
> Or does your distro not have matplotlib compiled for Python 2.6 yet?
No, I'm looking t
On Sunday 05 April 2009 18:49:46 Adam Mercer wrote:
> Hi
>
> Now that numpy-1.3.0 has been released what is the timescale for a
> python-2.6 compatible release of matplotlib and matplotlib-basemap? Or
> should the current release work OK?
>
> Cheers
>
> Adam
>
I've had matplotlib running fine on Py
Hi
Now that numpy-1.3.0 has been released what is the timescale for a
python-2.6 compatible release of matplotlib and matplotlib-basemap? Or
should the current release work OK?
Cheers
Adam
--
___
matplotlib SVN trunk appears to be running backend_driver.py fine under
Python-2.6 with Numpy SVN and TkAgg backend.
I had to make a handful of changes to remove deprecation warnings, none
of which changes our "still supporting Python 2.4" policy. One change
was required to pytz, which I've co
