Hi, I would like to release 0.7.1 relatively soon. There are a few low-hanging fruits, and here is a proposed schedule. Since no new features are added for 0.7.1, I don't think we really need a beta: - RC: 11th May (Monday) - Release: 18th May (Monday) My own interests are: - distribute a 0.7.1 binary for python 2.6 on windows and maybe mac os x. - make sure 0.7.1 is a universal build on mac os x (it is broken ATM). - fix some major segfaults/memleak in scipy.signal.lfilter, some of which were regressions compared to 0.6.0 So if you have some things (only bugs/doc enhancements, no new features), please backport them ASAP, cheers, David
On Fri, Apr 17, 2009 at 02:22:14PM +0900, David Cournapeau wrote:
I would like to release 0.7.1 relatively soon. There are a few low-hanging fruits, and here is a proposed schedule. Since no new features are added for 0.7.1, I don't think we really need a beta:
- RC: 11th May (Monday) - Release: 18th May (Monday)
My own interests are: - distribute a 0.7.1 binary for python 2.6 on windows and maybe mac os x. - make sure 0.7.1 is a universal build on mac os x (it is broken ATM). - fix some major segfaults/memleak in scipy.signal.lfilter, some of which were regressions compared to 0.6.0
Any chance matlab reader gets fixed? http://projects.scipy.org/scipy/ticket/885 Cheers, Gaël
Hi Gael 2009/4/17 Gael Varoquaux <gael.varoquaux@normalesup.org>:
Any chance matlab reader gets fixed?
If you can provide a test case, I'll add it today. Cheers Stéfan
On Fri, Apr 17, 2009 at 11:49:27AM +0200, Stéfan van der Walt wrote:
2009/4/17 Gael Varoquaux <gael.varoquaux@normalesup.org>:
Any chance matlab reader gets fixed?
If you can provide a test case, I'll add it today.
Not really, the corresponding file is big, and I don't know how to extract the part that triggers the bug. I was hoping the maintainer of this package of scipy (Matthew?) would know simply by looking at the fix how to create a test. Gaël
participants (3)
-
David Cournapeau
-
Gael Varoquaux
-
Stéfan van der Walt