I am not at my computer so I can't check the maintenace branch
changelog, but I know there have been a few bugfixes. Do any of them
look significant? How many downloads have we seen on the maintenance
branch vs the 98 trunk. My guess is there are not that many users and
we could skip a c
I just committed the change. Although the change is trivial, I didn't
tested it in the numpy 1.2 or the svn version.
-JJ
On Sun, Dec 7, 2008 at 3:24 PM, John Hunter <[EMAIL PROTECTED]> wrote:
> I think the version check is a good idea, so people won't get the annoying
> warning. Could you add t
Unfortunately, today is a crazy day for me so I can't test until late
tonight at the earliest. But Charlie, I do think we should hold the
release until we resolve this. We should be able to fix and test this
by tomorrow afternoon so perhaps Monday night for the release if
everything is in
Is there any need for a maintenance release?
On Thu, Dec 4, 2008 at 1:53 PM, John Hunter <[EMAIL PROTECTED]> wrote:
> On Thu, Dec 4, 2008 at 12:38 PM, Charlie Moad <[EMAIL PROTECTED]> wrote:
>> Works for me. Let's aim for Saturday night so we have Sunday to test
>> it out. Doable?
>
> Great -- e
I think the version check is a good idea, so people won't get the
annoying warning. Could you add this?
Sent from my iPhone
On Dec 7, 2008, at 2:22 PM, "Jae-Joon Lee" <[EMAIL PROTECTED]> wrote:
> I'm currently using numpy 1.1.1 and np.histogram behave differently
> depending on the "new" valu
I'm currently using numpy 1.1.1 and np.histogram behave differently
depending on the "new" value.
ubuntu interpid and debian sid has numpy 1.1.1.1 and I presume that
this different behavior is still there.
So, as far as we're going to support numpy 1.1 and later, we may
better not to drop the "new"
John,
I can't reproduce the error on my intel macbook.
Anyhow, it seems to me a bug in the code and bugs in numpy.
(I'm using numpy version 1.1.1, and I'm not sure these bugs are fixed
in newer numpy. )
Can you try the patch below and see if this fix your problem?
-JJ
Index: lib/matplotlib/sca
I held off on the release to hear back on this. Should we proceed
this evening if there is no response?
On Sat, Dec 6, 2008 at 5:09 PM, John Hunter <[EMAIL PROTECTED]> wrote:
> There appears to be a bug in the 3rd subplot of symlog_demo.py because
> the ticker is generating an OverflowError on my
