On Fri, Sep 7, 2012 at 7:54 AM, Ralf Gommers wrote:
>
>
> On Wed, Sep 5, 2012 at 7:06 AM, Travis Oliphant wrote:
>>
>> The framework for catching errors relies on hardware flags getting set and
>> our C code making the right calls to detect those flags.
>>
>> This has usually worked correctly in
I've recently opened a couple of pull requests that fix bugs with
MaskedArray - these are pretty straightforward, so would it be
possible to consider them in time for 1.7?
https://github.com/numpy/numpy/pull/2703
https://github.com/numpy/numpy/pull/2733
Thanks!
Tom
__
On 11/14/2012 10:10 AM, Peter Cock wrote:
> Changing title to reflect the fact this thread is now about using
> the Microsoft compiler rather than mingw32 as in the old thread.
>
> On Sat, Nov 10, 2012 at 11:04 PM, Peter Cock
> wrote:
>> On Sat, Nov 10, 2012 at 5:47 PM, Ralf Gommers wrote:
>>>
>
Changing title to reflect the fact this thread is now about using
the Microsoft compiler rather than mingw32 as in the old thread.
On Sat, Nov 10, 2012 at 11:04 PM, Peter Cock wrote:
> On Sat, Nov 10, 2012 at 5:47 PM, Ralf Gommers wrote:
>>
>>
>>
>> On Tue, Nov 6, 2012 at 6:49 PM, Peter Cock
>>
> Hi all,
>
> Having looked at the README.txt and INSTALL.txt files on the
> branch, I see no mention of which Python 3.x versions are supported:
>
> https://github.com/numpy/numpy/blob/maintenance/1.7.x/README.txt
> https://github.com/numpy/numpy/blob/maintenance/1.7.x/INSTALL.txt
>
> Is NumPy 1.7
On Wed, Nov 14, 2012 at 4:24 AM, Ondřej Čertík wrote:
> On Mon, Nov 12, 2012 at 2:27 PM, Ondřej Čertík
> wrote:
> [...]
> > Here is a list of issues that need to be fixed before the release:
> >
> > https://github.com/numpy/numpy/issues?milestone=3&state=open
> >
> > If anyone wants to help, we j
