On Mon, Apr 23, 2012 at 9:57 PM, Nathaniel Smith wrote:
> On Mon, Apr 23, 2012 at 6:18 PM, Ralf Gommers
> wrote:
> >
> >
> > On Mon, Apr 23, 2012 at 12:15 AM, Nathaniel Smith wrote:
> >>
> >> We need to decide what to do with the NA masking code currently in
> >> master, vis-a-vis the 1.7 relea
On Mon, Apr 23, 2012 at 9:16 PM, Chris Barker wrote:
> On Mon, Apr 23, 2012 at 12:57 PM, Nathaniel Smith wrote:
>> Right, this part is specifically about ABI compatibility, not API
>> compatibility -- segfaults would only occur for extension libraries
>> that were compiled against one version of
On Mon, Apr 23, 2012 at 12:57 PM, Nathaniel Smith wrote:
> Right, this part is specifically about ABI compatibility, not API
> compatibility -- segfaults would only occur for extension libraries
> that were compiled against one version of numpy and then used with a
> different version.
Which make
On Mon, Apr 23, 2012 at 6:18 PM, Ralf Gommers
wrote:
>
>
> On Mon, Apr 23, 2012 at 12:15 AM, Nathaniel Smith wrote:
>>
>> We need to decide what to do with the NA masking code currently in
>> master, vis-a-vis the 1.7 release. While this code is great at what it
>> is, we don't actually have cons
On Mon, Apr 23, 2012 at 12:15 AM, Nathaniel Smith wrote:
> We need to decide what to do with the NA masking code currently in
> master, vis-a-vis the 1.7 release. While this code is great at what it
> is, we don't actually have consensus yet that it's the best way to
> give our users what they wa
On Sun, Apr 22, 2012 at 6:26 PM, Charles R Harris wrote:
>
>
> On Sun, Apr 22, 2012 at 4:15 PM, Nathaniel Smith wrote:
>
>> We need to decide what to do with the NA masking code currently in
>> master, vis-a-vis the 1.7 release. While this code is great at what it
>> is, we don't actually have c
On Sun, Apr 22, 2012 at 4:15 PM, Nathaniel Smith wrote:
> We need to decide what to do with the NA masking code currently in
> master, vis-a-vis the 1.7 release. While this code is great at what it
> is, we don't actually have consensus yet that it's the best way to
> give our users what they wan
We need to decide what to do with the NA masking code currently in
master, vis-a-vis the 1.7 release. While this code is great at what it
is, we don't actually have consensus yet that it's the best way to
give our users what they want/need -- or even an appropriate way. So
we need to figure out how
