On Wed, Jul 23, 2008 at 6:46 AM, David Huard <[EMAIL PROTECTED]> wrote:
> I think we should stick to what has been agreed and announced months ago.
> It's called honouring our commitments and the project's image depends on it.
>
> If the inconvenience of these API changes is worth the trouble, a 1.
I think we should stick to what has been agreed and announced months ago.
It's called honouring our commitments and the project's image depends on it.
If the inconvenience of these API changes is worth the trouble, a 1.1.2 release
could be considered.
My two cents.
David
2008/7/22 Joe Harringto
Hi Jarrod,
I'm just catching up on my numpy lists and I caught this; sorry for
the late reply!
> Another issue that we should address is whether it is OK to postpone
> the planned API changes to histogram and median. A couple of people
> have mentioned to me that they would like to delay the API
On Sun, Jul 13, 2008 at 1:51 AM, Jarrod Millman <[EMAIL PROTECTED]> wrote:
> Here is the schedule for 1.2.0:
> - 8/05/08 tag the 1.1.1rc1 release and prepare packages
> - 8/12/08 tag the 1.1.1rc2 release and prepare packages
> - 8/23/08 tag the 1.1.1 release and prepare packages
> -
The NumPy 1.2.0 release date (8/24/08) is rapidly approaching and we
need everyone's help. David Cournapeau has volunteered to take the
lead on coordinating this release.
The main focus of this release is on improved documentation and a new
testing framework based on nose with only a few new feat
