On Tue, Jul 28, 2009 at 05:14, Jeff Whitaker wrote:
> Chris: This usually happens when you build mix different versions of
> geos, i.e. build with the 3.1 lib but the 2.2.3 headers, or link with
> the 3.1 shared lib and then have it pick up the 2.2.3 shared lib at run
> time. Do you have two ver
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
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
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
--
___
On Mon, Feb 9, 2009 at 17:08, Jayson Barr wrote:
> I agree with JDH.
Likewise.
> Unfortunately, work has been exceptionally hectic so I haven't begun
> the patch (if you don't count the hack job I did to install it for
> myself).
Same here, I'm really busy with work and don't have much time to
On Wed, Feb 4, 2009 at 17:08, Jayson Barr wrote:
> 2). If the Tk/Tcl libraries were installed from source instead of
> using the binaries you suggested installing, then it will just use the
> wrong system Framework anyway. I bet people using macports and other
> unix-like package managers on ma
