[Numpy-discussion] Status of the 1.7 release

Nathaniel Smith njs at pobox.com
Sun Dec 16 18:26:22 EST 2012

On 16 Dec 2012 23:01, "Charles R Harris" <charlesr.harris at gmail.com> wrote:
> On Sun, Dec 16, 2012 at 3:50 PM, Ondřej Čertík <ondrej.certik at gmail.com>
>> Thanks Ralf and Nathan,
>> I have put high priority on the issues that need to be fixed before the
>> There are now 4 issues:
>> I am working on the mingw one, as that one is the most difficult.
>> Ralf (or anyone else), do you know how to fix this one:
>> https://github.com/numpy/numpy/issues/438
>> I am not very familiar with this part of numpy, so maybe you know how
>> to document it well.
>> The sooner we can fix these 4 issues, the sooner we can release.
> I believe mingw was updated last month to a new compiler version. I don't
know what other changes there were, but it is possible that some problems
have been fixed.

It'd be worth checking in case it allows us to get off the (incredibly old)
GCC that we currently require on windows. But that's a long-term problem
that we probably shouldn't be messing with for 1.7 purposes. afaict all we
need to do for 1.7 is switch to using our current POSIX code on win32 as
well, instead of the (weird and broken) MS-specific API that we're
currently using. (Plus suppress some totally spurious warnings):

(Or I could be missing something, but I don't think any problems with that
solution have been discussed on the list anyway.)

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/numpy-discussion/attachments/20121216/e44ef060/attachment.html>

More information about the NumPy-Discussion mailing list