Hi Matthew,
On Tue, Jun 26, 2012 at 7:07 PM, Matthew Brett wrote:
> Hi,
>
> On Tue, Jun 26, 2012 at 6:00 PM, Fernando Perez wrote:
>> On Tue, Jun 26, 2012 at 5:40 PM, Ondřej Čertík
>> wrote:
>>> Do you use anything else besides Travis CI?
>>
>> Yes, we use both Shining Panda and Travis CI:
>>
Hi Fernando,
On Tue, Jun 26, 2012 at 6:00 PM, Fernando Perez wrote:
> On Tue, Jun 26, 2012 at 5:40 PM, Ondřej Čertík
> wrote:
>> Do you use anything else besides Travis CI?
>
> Yes, we use both Shining Panda and Travis CI:
>
> https://jenkins.shiningpanda.com/ipython/
With NumPy, I am still th
On Tue, Jun 26, 2012 at 11:02 PM, Travis Oliphant wrote:
> I just want to speak up for the people who are affected by API breakage who
> are not as vocal on this list.
Certainly! And indeed I bet you that's a community underrepresented
here: those of us who are on this list are likely to be up
Damn it, N is inverted and I noticed it now after posting. Sorry about
that, here is correct one:
from numpy import arange, ones
import matplotlib.pyplot as plt
from mpl_toolkits.mplot3d import Axes3D
fig = plt.figure()
ax = fig.add_subplot(111, projection
I do understand the issues around ABI breakage. I just want to speak up for
the people who are affected by API breakage who are not as vocal on this list.
I believe we should have similar frustration and concern at talk of API
breakage as there is about talk of ABI breakage.
-Travis
On Ju
On Tue, Jun 26, 2012 at 10:25 PM, Ralf Gommers
wrote:
>
> On Tue, Jun 26, 2012 at 5:33 AM, Travis Oliphant
> wrote:
> ...
>>
>> What should have happened in this case, in my mind, is that NumPy 1.4.0
>> should have been 1.5.0 and advertised that there was a break in the ABI and
>> that all extens
Travis, apologies in advance if the tone of this message is too strong -
please take it as a sign of how frustrating I find the discussion on this
point.
On Tue, Jun 26, 2012 at 5:33 AM, Travis Oliphant wrote:
...
> What should have happened in this case, in my mind, is that NumPy 1.4.0
> should
In my enthusiasm of finding someone to help with the release of NumPy 1.7 and
my desire to get something released by the SciPy conference, I was hasty and
didn't gather enough feedback from others about the release of NumPy 1.7. I'm
sorry about that.
I would like to get NumPy 1.7 out the door
Hi,
On Tue, Jun 26, 2012 at 8:13 PM, Travis Oliphant wrote:
>> For the main repos we use buildbot and test on:
>>
>> Ubuntu Maverick 32-bit
>> Debian sid 64-bit
>> OSX 10.4 PPC
>> OSX 10.5 Intel
>> Debian wheezy PPC
>> Debian squeeze ARM (a Raspberry PI no less)
>> WIndows XP 32 bit
>> SPARC (cou
> For the main repos we use buildbot and test on:
>
> Ubuntu Maverick 32-bit
> Debian sid 64-bit
> OSX 10.4 PPC
> OSX 10.5 Intel
> Debian wheezy PPC
> Debian squeeze ARM (a Raspberry PI no less)
> WIndows XP 32 bit
> SPARC (courtesy of our friends at NeuroDebian)
>
> http://nipy.bic.berkeley.edu/
Hi,
On Tue, Jun 26, 2012 at 5:04 PM, Charles R Harris
wrote:
>
>
> On Tue, Jun 26, 2012 at 5:46 PM, Matthew Brett
> wrote:
>>
>> Hi,
>>
>> On Tue, Jun 26, 2012 at 4:39 PM, Benjamin Root wrote:
>> >
>> >
>> > On Tuesday, June 26, 2012, Charles R Harris wrote:
>> >>
>> >>
>> >>
>> >> On Tue, Jun
Hi,
On Tue, Jun 26, 2012 at 6:00 PM, Fernando Perez wrote:
> On Tue, Jun 26, 2012 at 5:40 PM, Ondřej Čertík
> wrote:
>> Do you use anything else besides Travis CI?
>
> Yes, we use both Shining Panda and Travis CI:
>
> https://jenkins.shiningpanda.com/ipython/
> http://travis-ci.org/#!/ipython/i
| From: Rebekah Pratt
| Date: Jun 25 23:59:59 2012 -0400
|
| Hey, greetings from orlando! How has re entry to texas been? Our
| holiday is going well, although a little fast. The whole disney
| experience is cooler than I was expecting. We are all a bit tired
| out though, and adah moody as
On Tue, Jun 26, 2012 at 5:40 PM, Ondřej Čertík wrote:
> Do you use anything else besides Travis CI?
Yes, we use both Shining Panda and Travis CI:
https://jenkins.shiningpanda.com/ipython/
http://travis-ci.org/#!/ipython/ipython
The SP setup is more complete, including Mac and Windows bots.
> I
On Tue, Jun 26, 2012 at 4:59 PM, Fernando Perez wrote:
> On Tue, Jun 26, 2012 at 1:10 PM, Travis Oliphant wrote:
>> One issues is the one that Sage identified about the array interface
>> regression as noted by Jason. Any other regressions from 1.5.x need to be
>> addressed as well. We'll h
On Tue, Jun 26, 2012 at 8:15 PM, Skipper Seabold wrote:
> On Tue, Jun 26, 2012 at 7:59 PM, Fernando Perez wrote:
>> On Tue, Jun 26, 2012 at 1:10 PM, Travis Oliphant wrote:
>>> One issues is the one that Sage identified about the array interface
>>> regression as noted by Jason. Any other regr
On Tue, Jun 26, 2012 at 7:59 PM, Fernando Perez wrote:
> On Tue, Jun 26, 2012 at 1:10 PM, Travis Oliphant wrote:
>> One issues is the one that Sage identified about the array interface
>> regression as noted by Jason. Any other regressions from 1.5.x need to be
>> addressed as well. We'll h
On Tue, Jun 26, 2012 at 5:46 PM, Matthew Brett wrote:
> Hi,
>
> On Tue, Jun 26, 2012 at 4:39 PM, Benjamin Root wrote:
> >
> >
> > On Tuesday, June 26, 2012, Charles R Harris wrote:
> >>
> >>
> >>
> >> On Tue, Jun 26, 2012 at 3:42 PM, Matthew Brett >
> >> wrote:
> >>
> >> Hi,
> >>
> >> On Mon, Ju
On Tue, Jun 26, 2012 at 1:10 PM, Travis Oliphant wrote:
> One issues is the one that Sage identified about the array interface
> regression as noted by Jason. Any other regressions from 1.5.x need to be
> addressed as well. We'll have to decide on a case-by-case basis if there
> are issues t
On Tuesday, June 26, 2012, Thouis (Ray) Jones wrote:
> On Tue, Jun 26, 2012 at 10:11 PM, Jason Grout
> > wrote:
> > On 6/26/12 3:06 PM, Dag Sverre Seljebotn wrote:
> >> Something the Sage project does very well is meeting often in person
> >
> > Another thing we have that has improved the mailing
Hi,
On Tue, Jun 26, 2012 at 4:39 PM, Benjamin Root wrote:
>
>
> On Tuesday, June 26, 2012, Charles R Harris wrote:
>>
>>
>>
>> On Tue, Jun 26, 2012 at 3:42 PM, Matthew Brett
>> wrote:
>>
>> Hi,
>>
>> On Mon, Jun 18, 2012 at 3:50 PM, Matthew Brett
>> wrote:
>> > Hi,
>> >
>> > On Sun, Jun 17, 201
On Tuesday, June 26, 2012, Charles R Harris wrote:
>
>
> On Tue, Jun 26, 2012 at 3:42 PM, Matthew Brett wrote:
>
> Hi,
>
> On Mon, Jun 18, 2012 at 3:50 PM, Matthew Brett
> wrote:
> > Hi,
> >
> > On Sun, Jun 17, 2012 at 7:22 PM, Charles R Harris
> > wrote:
> >>
> >>
> >> On Sat, Jun 16, 2012 at 2
>On Sat, Jun 16, 2012 at 4:39 PM, Nathaniel Smith wrote:
>> On Sat, Jun 16, 2012 at 9:03 PM, Matthew Brett
>> wrote:
>>> Hi,
>>>
>>> On Sat, Jun 16, 2012 at 10:40 AM, Nathaniel Smith wrote:
On Fri, Jun 15, 2012 at 4:10 AM, Charles R Harris
wrote:
>
>
> On Thu, Jun 14, 201
On Tue, Jun 26, 2012 at 3:42 PM, Matthew Brett wrote:
> Hi,
>
> On Mon, Jun 18, 2012 at 3:50 PM, Matthew Brett
> wrote:
> > Hi,
> >
> > On Sun, Jun 17, 2012 at 7:22 PM, Charles R Harris
> > wrote:
> >>
> >>
> >> On Sat, Jun 16, 2012 at 2:33 PM, Matthew Brett >
> >> wrote:
> >>>
> >>> Hi,
> >>>
I want to support multiple types in the index_increment function that I've
written here:
https://github.com/jsalvatier/numpy/blob/master/numpy/core/src/multiarray/mapping.c
I need to check that the first argument's type can support addition, cast
the dataptr to the appropriate type and do the addi
Hi,
On Mon, Jun 18, 2012 at 3:50 PM, Matthew Brett wrote:
> Hi,
>
> On Sun, Jun 17, 2012 at 7:22 PM, Charles R Harris
> wrote:
>>
>>
>> On Sat, Jun 16, 2012 at 2:33 PM, Matthew Brett
>> wrote:
>>>
>>> Hi,
>>>
>>> On Sat, Jun 16, 2012 at 8:03 PM, Matthew Brett
>>> wrote:
>>> > Hi,
>>> >
>>> > O
On Tue, Jun 26, 2012 at 9:34 PM, Travis Oliphant wrote:
> I think we need to update this document:
> http://projects.scipy.org/numpy/wiki/ApiDeprecation
>
Sounds fine to me to make the period for removal longer, or even to by
default aim to not remove deprecated API's at all in minor release (unl
On 26 June 2012 22:39, John Hunter wrote:
> On Tue, Jun 26, 2012 at 3:27 PM, Thouis (Ray) Jones wrote:
>> +1 !
>>
>> Speaking as someone trying to get started in contributing to numpy, I
>> find this discussion extremely off-putting. It's childish,
>> meaningless, and spiteful, and I think it's d
On 06/26/2012 10:35 PM, Dag Sverre Seljebotn wrote:
> On 06/26/2012 05:02 PM, Travis Oliphant wrote:
(I have not read the whole cython discussion yet)
>>>
>>> So here's the summary. It's rather complicated but also incredibly neat
>>> :-) And technical details can be hidden behind a tight
On 6/26/12 3:31 PM, Travis Oliphant wrote:
> Thank you for the reminder. I was already called out for not stopping.
> Thanks, Dag. A flame-list might indeed be a good idea at this point if
> there is further need for "clearing the air"
>
Also, having it set up before it is needed is part
On Tue, Jun 26, 2012 at 3:27 PM, Thouis (Ray) Jones wrote:
> +1 !
>
> Speaking as someone trying to get started in contributing to numpy, I
> find this discussion extremely off-putting. It's childish,
> meaningless, and spiteful, and I think it's doing more harm than any
> possible good that coul
On 06/26/2012 05:02 PM, Travis Oliphant wrote:
>>>
>>> (I have not read the whole cython discussion yet)
>>
>> So here's the summary. It's rather complicated but also incredibly neat
>> :-) And technical details can be hidden behind a tight API.
>
> Could you provide a bit more context for this lis
On Jun 26, 2012, at 3:27 PM, Thouis (Ray) Jones wrote:
> On Tue, Jun 26, 2012 at 10:11 PM, Jason Grout
> wrote:
>> On 6/26/12 3:06 PM, Dag Sverre Seljebotn wrote:
>>> Something the Sage project does very well is meeting often in person
>>
>> Another thing we have that has improved the mailing l
On Tue, Jun 26, 2012 at 10:10 PM, Travis Oliphant wrote:
>
>> Unfortunately, I think there are issues we are just now seeing with code
>> that was released in 1.6.x, and there are many people who have not moved
>> forward to 1.6.x yet.
>>
>
> Some examples would be nice. A lot of people did move a
On Tue, Jun 26, 2012 at 10:11 PM, Jason Grout
wrote:
> On 6/26/12 3:06 PM, Dag Sverre Seljebotn wrote:
>> Something the Sage project does very well is meeting often in person
>
> Another thing we have that has improved the mailing list climate is a
> "sage-flame" list [1]
+1 !
Speaking as someon
On 6/26/12 3:06 PM, Dag Sverre Seljebotn wrote:
> Something the Sage project does very well is meeting often in person
Another thing we have that has improved the mailing list climate is a
"sage-flame" list [1] that serves as a venting release valve for anyone
to post *anything* at all. There h
>
> Unfortunately, I think there are issues we are just now seeing with code that
> was released in 1.6.x, and there are many people who have not moved forward
> to 1.6.x yet.
>
> Some examples would be nice. A lot of people did move already. And I haven't
> seen reports of those that tr
On Tue, Jun 26, 2012 at 1:51 PM, Travis Oliphant wrote:
>
> Exactly.
>
>
>> I don't
>> feel responsible for this issue (except I maybe should have pushed
>> more strongly about datetime being included),
>
>
> I think you left out a 'not'. I don't mean to imply that you were in
> anyway the blame.
On 06/26/2012 09:51 PM, Travis Oliphant wrote:
>>
>> Exactly.
>>
>> I don't
>> feel responsible for this issue (except I maybe should have pushed
>> more strongly about datetime being included),
>>
>>
>> I think you left out a 'not'. I don't mean to imply that you were in
>> anyway the
On 6/26/12 2:48 PM, Ralf Gommers wrote:
> Unfortunately, I think there are issues we are just now seeing with
> code that was released in 1.6.x, and there are many people who have
> not moved forward to 1.6.x yet.
>
>
> Some examples would be nice.
I'll bite. Here's an issue that pre
>
> Exactly.
>
> I don't
> feel responsible for this issue (except I maybe should have pushed
> more strongly about datetime being included),
>
> I think you left out a 'not'. I don't mean to imply that you were in anyway
> the blame. And you have been pretty adamant about not allowing late me
On Tue, Jun 26, 2012 at 9:20 PM, Travis Oliphant wrote:
>
> On Jun 26, 2012, at 2:10 PM, Ralf Gommers wrote:
>
>
>
> On Tue, Jun 26, 2012 at 5:43 PM, Travis Oliphant wrote:
>
>>
>> Hey all,
>>
>> After some more investigation, I'm not optimistic that we will be able to
>> get a 1.7 release out bef
I think we need to update this document:
http://projects.scipy.org/numpy/wiki/ApiDeprecation
I don't think this characterizes the opinion of all involved in NumPy
development (it is certainly not the way I view our commitment to users).
Incidentally, in the migration from Trac we should move
On Jun 26, 2012, at 2:10 PM, Ralf Gommers wrote:
>
>
> On Tue, Jun 26, 2012 at 5:43 PM, Travis Oliphant wrote:
>
> Hey all,
>
> After some more investigation, I'm not optimistic that we will be able to get
> a 1.7 release out before SciPy. I would like to get a beta release out by
> SciP
On Jun 26, 2012, at 1:34 PM, Frédéric Bastien wrote:
> Hi,
>
> I think he was referring that making NUMPY_ARRAY_OBJECT[...] syntax
> support the operation that you said is hard. But having a separate
> function do it is less complicated as you said.
Yes. That's precisely what I meant. Thank y
On Tue, Jun 26, 2012 at 5:43 PM, Travis Oliphant wrote:
>
> Hey all,
>
> After some more investigation, I'm not optimistic that we will be able to
> get a 1.7 release out before SciPy. I would like to get a beta release
> out by SciPy (or even an rc1 release). But, given the number of code
> c
Hi All,
my question might have got lost due to the intense activity around
the 1.7 release. Now that it has quietened down, would appreciate any
help regarding my confusion about how index arrays work
(especially when broadcasted).
-- srean
On Mon, Jun 25, 2012 at 5:29 PM, srean wrote:
> From
Right, that makes sense. Thanks.
On Tue, Jun 26, 2012 at 11:34 AM, Frédéric Bastien wrote:
> Hi,
>
> I think he was referring that making NUMPY_ARRAY_OBJECT[...] syntax
> support the operation that you said is hard. But having a separate
> function do it is less complicated as you said.
>
> Fred
Hi,
I think he was referring that making NUMPY_ARRAY_OBJECT[...] syntax
support the operation that you said is hard. But having a separate
function do it is less complicated as you said.
Fred
On Tue, Jun 26, 2012 at 1:27 PM, John Salvatier
wrote:
> Can you clarify why it would be super hard? I
Can you clarify why it would be super hard? I just reused the code for
advanced indexing (a modification of PyArray_SetMap). Am I missing
something crucial?
On Tue, Jun 26, 2012 at 9:57 AM, Travis Oliphant wrote:
>
> On Jun 26, 2012, at 11:46 AM, John Salvatier wrote:
>
> Hello,
>
> If you incr
On Tue, Jun 26, 2012 at 10:48 AM, David Cournapeau wrote:
> On Tue, Jun 26, 2012 at 5:24 PM, Travis Oliphant
> wrote:
> >
> >> Let us note that that problem was due to Travis convincing David to
> >> include the Datetime work in the release against David's own best
> judgement.
> >> The result wa
>
> Or, we could raise funds for NumFOCUS by selling tickets for a brawl between
> the two at SciPy2012...
>
> I kid, I kid!
Thanks for the humor. Unfortunately, I would be no match physically with
someone used to the cold of Logan :-)
-Travis
_
On Jun 26, 2012, at 11:46 AM, John Salvatier wrote:
> Hello,
>
> If you increment an array using advanced indexing and have repeated indexes,
> the array doesn't get repeatedly incremented,
> http://comments.gmane.org/gmane.comp.python.numeric.general/50291. I wrote a
> C function that does
>
> I think Chuck alludes to the fact that I was rather reserved about
> merging datetime before *anyone* knew about breaking the ABI. I don't
> feel responsible for this issue (except I maybe should have pushed
> more strongly about datetime being included), but I am also not
> interested in maki
On Tue, Jun 26, 2012 at 12:48 PM, David Cournapeau wrote:
> On Tue, Jun 26, 2012 at 5:24 PM, Travis Oliphant
> wrote:
> >
> >> Let us note that that problem was due to Travis convincing David to
> >> include the Datetime work in the release against David's own best
> judgement.
> >> The result wa
On Tue, Jun 26, 2012 at 5:24 PM, Travis Oliphant wrote:
>
>> Let us note that that problem was due to Travis convincing David to
>> include the Datetime work in the release against David's own best judgement.
>> The result was a delay of several months until Ralf could get up to speed
>> and get 1
Hello,
If you increment an array using advanced indexing and have repeated
indexes, the array doesn't get repeatedly incremented,
http://comments.gmane.org/gmane.comp.python.numeric.general/50291. I wrote
a C function that does incrementing with repeated indexes correctly. The
branch is here (http
On Jun 26, 2012, at 11:29 AM, Thouis (Ray) Jones wrote:
> On Tue, Jun 26, 2012 at 5:33 PM, Charles R Harris
> wrote:
>> Calling this and that 'gratuitous' is already damaging to the community.
>> Them's fightin' words. If you didn't want a fight you could have simply
>> pointed out a path forwar
On Tue, Jun 26, 2012 at 5:33 PM, Charles R Harris
wrote:
> Calling this and that 'gratuitous' is already damaging to the community.
> Them's fightin' words. If you didn't want a fight you could have simply
> pointed out a path forward.
I disagree. If a change is gratuitous, and someone call's it
>> Let us note that that problem was due to Travis convincing David to include
>> the Datetime work in the release against David's own best judgement. The
>> result was a delay of several months until Ralf could get up to speed and
>> get 1.4.1 out. Let us also note that poly1d is actually not
Hey all,
After some more investigation, I'm not optimistic that we will be able to get a
1.7 release out before SciPy. I would like to get a beta release out by SciPy
(or even an rc1 release). But, given the number of code changes and
differences between 1.5.x and 1.7, I think we will nee
On Tue, Jun 26, 2012 at 8:52 AM, Travis Oliphant wrote:
>
> On Jun 26, 2012, at 9:00 AM, Charles R Harris wrote:
>
>
>
> On Mon, Jun 25, 2012 at 9:10 PM, Ondřej Čertík wrote:
>
>> On Mon, Jun 25, 2012 at 7:38 PM, Fernando Perez
>> wrote:
>> > On Mon, Jun 25, 2012 at 6:39 PM, Travis Oliphant
>> w
>>
>> (I have not read the whole cython discussion yet)
>
> So here's the summary. It's rather complicated but also incredibly neat
> :-) And technical details can be hidden behind a tight API.
Could you provide a bit more context for this list. I think this is an
important technology conc
On Jun 26, 2012, at 9:00 AM, Charles R Harris wrote:
>
>
> On Mon, Jun 25, 2012 at 9:10 PM, Ondřej Čertík
> wrote:
> On Mon, Jun 25, 2012 at 7:38 PM, Fernando Perez wrote:
> > On Mon, Jun 25, 2012 at 6:39 PM, Travis Oliphant
> > wrote:
> >>
> >> On Jun 25, 2012, at 7:21 PM, Fernando Perez
On Tue, Jun 26, 2012 at 2:40 PM, Dag Sverre Seljebotn
wrote:
> On 06/26/2012 01:48 PM, David Cournapeau wrote:
>> Hi,
>>
>> I am just continuing the discussion around ABI/API, the technical side
>> of things that is, as this is unrelated to 1.7.x. release.
>>
>> On Tue, Jun 26, 2012 at 11:41 AM, D
On 06/26/2012 04:08 PM, Dag Sverre Seljebotn wrote:
> On 06/26/2012 01:48 PM, David Cournapeau wrote:
>> Hi,
>>
>> I am just continuing the discussion around ABI/API, the technical side
>> of things that is, as this is unrelated to 1.7.x. release.
>>
>> On Tue, Jun 26, 2012 at 11:41 AM, Dag Sverre
On 06/26/2012 01:48 PM, David Cournapeau wrote:
> Hi,
>
> I am just continuing the discussion around ABI/API, the technical side
> of things that is, as this is unrelated to 1.7.x. release.
>
> On Tue, Jun 26, 2012 at 11:41 AM, Dag Sverre Seljebotn
> wrote:
>> On 06/26/2012 11:58 AM, David Courna
On Mon, Jun 25, 2012 at 9:10 PM, Ondřej Čertík wrote:
> On Mon, Jun 25, 2012 at 7:38 PM, Fernando Perez
> wrote:
> > On Mon, Jun 25, 2012 at 6:39 PM, Travis Oliphant
> wrote:
> >>
> >> On Jun 25, 2012, at 7:21 PM, Fernando Perez wrote:
> >
> >>
> >> For context, consider that for many years, the
On 06/26/2012 01:48 PM, David Cournapeau wrote:
> Hi,
>
> I am just continuing the discussion around ABI/API, the technical side
> of things that is, as this is unrelated to 1.7.x. release.
>
> On Tue, Jun 26, 2012 at 11:41 AM, Dag Sverre Seljebotn
> wrote:
>> On 06/26/2012 11:58 AM, David Courna
It would be really awesome to have a script like this to generate the logo.
That's pretty amazing. Would you be able to tweak it up a bit and then we
could take a poll here? Perhaps we change the logo to a variation of what
your script produces.
Can you export a PNG?
-Travis
On Jun
Hi,
I am just continuing the discussion around ABI/API, the technical side
of things that is, as this is unrelated to 1.7.x. release.
On Tue, Jun 26, 2012 at 11:41 AM, Dag Sverre Seljebotn
wrote:
> On 06/26/2012 11:58 AM, David Cournapeau wrote:
>> On Tue, Jun 26, 2012 at 10:27 AM, Dag Sverre Se
On 06/26/2012 11:58 AM, David Cournapeau wrote:
> On Tue, Jun 26, 2012 at 10:27 AM, Dag Sverre Seljebotn
> wrote:
>> On 06/26/2012 05:35 AM, David Cournapeau wrote:
>>> On Tue, Jun 26, 2012 at 4:10 AM, Ondřej Čertík
>>> wrote:
>>>
My understanding is that Travis is simply trying to
On Tue, Jun 26, 2012 at 10:27 AM, Dag Sverre Seljebotn
wrote:
> On 06/26/2012 05:35 AM, David Cournapeau wrote:
>> On Tue, Jun 26, 2012 at 4:10 AM, Ondřej Čertík
>> wrote:
>>
>>>
>>> My understanding is that Travis is simply trying to stress "We have to
>>> think about the implications of our ch
On 06/26/2012 05:35 AM, David Cournapeau wrote:
> On Tue, Jun 26, 2012 at 4:10 AM, Ondřej Čertík
> wrote:
>
>>
>> My understanding is that Travis is simply trying to stress "We have to
>> think about the implications of our changes on existing users." and
>> also that little changes (with the bes
On Thu, Jun 21, 2012 at 3:11 AM, Travis Oliphant wrote:
> Hey all,
>
> I made a branch called with_maskna and then merged Nathaniel's PR which
> removes the mask_na support from master. I then applied a patch to fix the
> boolean indexing problem reported by Ralf.
>
> I then created a NumPy 1.7
75 matches
Mail list logo
