[Numpy-discussion] [Numpy-svn] r5198 - trunk/numpy/f2py

Pearu Peterson pearu@cens.ioc...
Tue May 20 05:50:05 CDT 2008

On Tue, May 20, 2008 1:36 pm, Jarrod Millman wrote:
> On Mon, May 19, 2008 at 10:29 PM, Pearu Peterson <pearu@cens.ioc.ee>
> wrote:
>> On Tue, May 20, 2008 1:26 am, Robert Kern wrote:
>>> Is this an important bugfix? If not, can you hold off until 1.1.0 is
>>> released?
>> The patch fixes a long existing and unreported bug in f2py - I think
>> the bug was introduced when Python defined min and max functions.
>> I learned about the bug when reading a manuscript about f2py. Such bugs
>> should not end up in a paper demonstrating f2py inability to process
>> certain features as it would have not been designed to do so. So, I'd
>> consider
>> the bugfix important.
> I have been struggling to try and get a stable release out since
> February and every time I think that the release is almost ready some
> piece of code changes that requires me to delay.  While overall the
> code has continuously improved over this period, I think it is time to
> get these improvements to our users.
> That said, I am willing to leave this change on the trunk, but please
> refrain from making any more changes until we release 1.1.0.  I know
> it can be frustrating, but, I believe, this is the first time I have
> asked the community to not make commits to the trunk since I started
> handling releases almost a year ago.  The freeze has only been in
> effect since Saturday and will last less than one week in total.  I
> would have preferred if you could have made this change during any one
> of the other 51 weeks of the year.

Please, go ahead. I'll not commit non-critical changes until the trunk
is open again.


More information about the Numpy-discussion mailing list