I'm available to crank out some builds. I'll keep my eyes peeled for the
new numpy.
- Charlie
On Wed, May 7, 2008 at 1:21 PM, John Hunter <[EMAIL PROTECTED]> wrote:
> On Wed, May 7, 2008 at 10:59 AM, Darren Dale <[EMAIL PROTECTED]>
> wrote:
>
> > I'm also in favor of a 0.98 release. Calling it
John Hunter wrote:
> On Wed, May 7, 2008 at 1:21 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
>
>> Getting out a 0.98 beta soon would help in getting it more widely
>> tested, but it would be nice if that first beta passed the basic checks
>> of working for all backend_driver tests on all the sta
On Wed, May 7, 2008 at 1:21 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
> Getting out a 0.98 beta soon would help in getting it more widely
> tested, but it would be nice if that first beta passed the basic checks
> of working for all backend_driver tests on all the standard backends.
> As of t
nderstand. Each artist with a
draw(self, renderer) method has been decorated.
I pulled out the start/stop rendering pair in QuadMesh. I presume
those two lines were all I needed to touch. I'll assume so unless I
hear otherwise.
Patch at:
http://deeplycloudy.com/patches/20080507-mpl-mixed-
John and Michael,
Thanks for your detailed feedback about the mpl design philosophy. I'm
not attached to my implementation details. I will scrap the
draw_raster list and move to implement get/set_rasterized on the
artists.
> > Doing this in the axes.draw method may not be the most natural p
Michael Droettboom wrote:
> I don't know if 0.98 has seen enough hammering to be a recommended
> stable release. (Just today, Matthias Michler pointed out a pretty
> significant bug with widgets related to the refactoring). I think a
> 0.98 release that is clearly labeled as beta would not be
On Wed, May 7, 2008 at 10:59 AM, Darren Dale <[EMAIL PROTECTED]> wrote:
> I'm also in favor of a 0.98 release. Calling it beta is fine, I just need
> something other than svn to which I can point my users.
I happy with both -- doing a 0.91.3 maintenance release and a
0.98.beta release. We don'
On Wednesday 07 May 2008 11:18:22 am Michael Droettboom wrote:
> I don't know if 0.98 has seen enough hammering to be a recommended
> stable release. (Just today, Matthias Michler pointed out a pretty
> significant bug with widgets related to the refactoring). I think a
> 0.98 release that is cle
Michael Droettboom wrote:
> I don't know if 0.98 has seen enough hammering to be a recommended
> stable release. (Just today, Matthias Michler pointed out a pretty
> significant bug with widgets related to the refactoring). I think a
> 0.98 release that is clearly labeled as beta would not be
I don't know if 0.98 has seen enough hammering to be a recommended
stable release. (Just today, Matthias Michler pointed out a pretty
significant bug with widgets related to the refactoring). I think a
0.98 release that is clearly labeled as beta would not be a bad thing to
get it in the hand
What do people think of releasing 0.98 after numpy 1.1 is released this
weekend?
The main reason I'd like to do this (instead of releasing another
0.91.x) is that the toolkits are broken in 0.91 - if matplotlib is
installed as an egg basemap (or any other toolkit) cannot be installed.
-Jeff
This is not a problem, I compile new nersions of differnet paclages
regularly.
I'll checkout the branch, many thanks !
Matthieu
2008/5/7 Michael Droettboom <[EMAIL PROTECTED]>:
> Unfortunately, the fix requires recompiling C code. If you're comfortable
> doing that, the easiest thing is just t
Unfortunately, the fix requires recompiling C code. If you're
comfortable doing that, the easiest thing is just to check out the svn
branch here:
http://matplotlib.svn.sf.net/svnroot/matplotlib/branches/v0_91_maint
But for those not doing that, I think a new release is in order, but I'm
not t
Eric Firing wrote:
> Manuel Metz wrote:
>> Hi,
>>while adding the step-histogram I learned about the change of
>> numpy.histogram. As MPL trunk relies in numpy 1.1, I think its a good
>> idea to switch to the new histogram, i.e. use "new=True". Indeed, this
>> is required to be able to allow
John Hunter schrieb:
> On Tue, May 6, 2008 at 8:49 AM, Gregor Thalhammer
> <[EMAIL PROTECTED]> wrote:
>
>
>> I also discovered this behaviour. It seems to be a Windows only specific
>> behaviour that only affects the bitmaps of the disabled (or grayed out)
>> toolbar buttons. A solution I found
>
>
> > 2) Use:
> > F.savefig(open(path, "w"), dpi=dpi)
> This is exactly what matplotlib the *Agg backends do on the 0.91.x
> maintenance branch and the trunk. Unfortunately, 0.91.2 (the latest
> release) still has this bug. This may be reason enough to push out a
> new maintenance release of 0.
16 matches
Mail list logo
