NumPy sprints at Scipy 2013, Austin: call for topics and hands to help

Hi there, I agreed to help organising NumPy sprints during the scipy 2013 conference in Austin. As some of you may know, Stéfan and me will present a tutorial on NumPy C code, so if we do our job correctly, we should have a few new people ready to help out during the sprints. It would be good to: - have some focus topics for improvements - know who is going to be there at the sprint to work on things and/or help newcomers Things I'd like to work on myself is looking into splitting things from multiarray, think about a better internal API for dtype registration/hooks (with the goal to remove any date dtype hardcoding in both multiarray and ufunc machinery), but I am sure others have more interesting ideas :) thanks, David

On Sat, May 25, 2013 at 8:23 AM, David Cournapeau <cournape@gmail.com>wrote:
Hi there,
I agreed to help organising NumPy sprints during the scipy 2013 conference in Austin.
As some of you may know, Stéfan and me will present a tutorial on NumPy C code, so if we do our job correctly, we should have a few new people ready to help out during the sprints.
It would be good to: - have some focus topics for improvements - know who is going to be there at the sprint to work on things and/or help newcomers
Things I'd like to work on myself is looking into splitting things from multiarray, think about a better internal API for dtype registration/hooks (with the goal to remove any date dtype hardcoding in both multiarray and ufunc machinery), but I am sure others have more interesting ideas :)
I'd like to get a 1.8 beta out or at least get to the point where we can make that leap. There is a lot of new stuff that needs to be tested, PR's to go through, and I have a suspicion that a memory allocation error might have crept in somewhere. Chuck

On Sat, May 25, 2013 at 4:19 PM, Charles R Harris <charlesr.harris@gmail.com> wrote:
On Sat, May 25, 2013 at 8:23 AM, David Cournapeau <cournape@gmail.com> wrote:
Hi there,
I agreed to help organising NumPy sprints during the scipy 2013 conference in Austin.
As some of you may know, Stéfan and me will present a tutorial on NumPy C code, so if we do our job correctly, we should have a few new people ready to help out during the sprints.
It would be good to: - have some focus topics for improvements - know who is going to be there at the sprint to work on things and/or help newcomers
Things I'd like to work on myself is looking into splitting things from multiarray, think about a better internal API for dtype registration/hooks (with the goal to remove any date dtype hardcoding in both multiarray and ufunc machinery), but I am sure others have more interesting ideas :)
I'd like to get a 1.8 beta out or at least get to the point where we can make that leap.
Sure, I am fine doing this in a branch post 1.8.x, I am not in a hurry.
There is a lot of new stuff that needs to be tested, PR's to go through, and I have a suspicion that a memory allocation error might have crept in somewhere.
Will you be there at the conference ? David

On Sat, May 25, 2013 at 9:51 AM, David Cournapeau <cournape@gmail.com>wrote:
On Sat, May 25, 2013 at 4:19 PM, Charles R Harris <charlesr.harris@gmail.com> wrote:
On Sat, May 25, 2013 at 8:23 AM, David Cournapeau <cournape@gmail.com> wrote:
Hi there,
I agreed to help organising NumPy sprints during the scipy 2013 conference in Austin.
As some of you may know, Stéfan and me will present a tutorial on NumPy C code, so if we do our job correctly, we should have a few new people ready to help out during the sprints.
It would be good to: - have some focus topics for improvements - know who is going to be there at the sprint to work on things and/or help newcomers
Things I'd like to work on myself is looking into splitting things from multiarray, think about a better internal API for dtype registration/hooks (with the goal to remove any date dtype hardcoding in both multiarray and ufunc machinery), but I am sure others have more interesting ideas :)
I'd like to get a 1.8 beta out or at least get to the point where we can make that leap.
Sure, I am fine doing this in a branch post 1.8.x, I am not in a hurry.
There is a lot of new stuff that needs to be tested, PR's to go through, and I have a suspicion that a memory allocation error might have crept in somewhere.
Will you be there at the conference ?
Yes. I'm not very good at sprinting though. I prefer to amble with a big screen, nice keyboard, and a cup of coffee ;) Chuck

On Sat, May 25, 2013 at 12:37 PM, Charles R Harris < charlesr.harris@gmail.com> wrote:
On Sat, May 25, 2013 at 9:51 AM, David Cournapeau <cournape@gmail.com>wrote:
On Sat, May 25, 2013 at 4:19 PM, Charles R Harris <charlesr.harris@gmail.com> wrote:
On Sat, May 25, 2013 at 8:23 AM, David Cournapeau <cournape@gmail.com> wrote:
Hi there,
I agreed to help organising NumPy sprints during the scipy 2013 conference in Austin.
As some of you may know, Stéfan and me will present a tutorial on NumPy C code, so if we do our job correctly, we should have a few new people ready to help out during the sprints.
It would be good to: - have some focus topics for improvements - know who is going to be there at the sprint to work on things and/or help newcomers
Things I'd like to work on myself is looking into splitting things from multiarray, think about a better internal API for dtype registration/hooks (with the goal to remove any date dtype hardcoding in both multiarray and ufunc machinery), but I am sure others have more interesting ideas :)
I'd like to get a 1.8 beta out or at least get to the point where we can make that leap.
Sure, I am fine doing this in a branch post 1.8.x, I am not in a hurry.
There is a lot of new stuff that needs to be tested, PR's to go through, and I have a suspicion that a memory allocation error might have crept in somewhere.
Will you be there at the conference ?
Yes. I'm not very good at sprinting though. I prefer to amble with a big screen, nice keyboard, and a cup of coffee ;)
Chuck
Oh, I am sure we could get you set up with a projector screen and a nice bluetooth keyboard... Now, I think you just hit on something with the coffee. I don't recall previous sprints having coffee available. Ben Root

On Sat, May 25, 2013 at 6:59 PM, Benjamin Root <ben.root@ou.edu> wrote:
On Sat, May 25, 2013 at 12:37 PM, Charles R Harris < charlesr.harris@gmail.com> wrote:
On Sat, May 25, 2013 at 9:51 AM, David Cournapeau <cournape@gmail.com>wrote:
On Sat, May 25, 2013 at 4:19 PM, Charles R Harris <charlesr.harris@gmail.com> wrote:
On Sat, May 25, 2013 at 8:23 AM, David Cournapeau <cournape@gmail.com> wrote:
Hi there,
I agreed to help organising NumPy sprints during the scipy 2013 conference in Austin.
As some of you may know, Stéfan and me will present a tutorial on NumPy C code, so if we do our job correctly, we should have a few new people ready to help out during the sprints.
It would be good to: - have some focus topics for improvements - know who is going to be there at the sprint to work on things and/or help newcomers
Things I'd like to work on myself is looking into splitting things from multiarray, think about a better internal API for dtype registration/hooks (with the goal to remove any date dtype hardcoding in both multiarray and ufunc machinery), but I am sure others have more interesting ideas :)
I'd like to get a 1.8 beta out or at least get to the point where we
can
make that leap.
Sure, I am fine doing this in a branch post 1.8.x, I am not in a hurry.
There is a lot of new stuff that needs to be tested, PR's to go through, and I have a suspicion that a memory allocation error might have crept in somewhere.
Will you be there at the conference ?
Yes. I'm not very good at sprinting though. I prefer to amble with a big screen, nice keyboard, and a cup of coffee ;)
Chuck
Oh, I am sure we could get you set up with a projector screen and a nice bluetooth keyboard... Now, I think you just hit on something with the coffee. I don't recall previous sprints having coffee available.
Arrggghhhh, everyone would see my lousy code. I'd be exposed as the naked emporer I am ;) Chuck

Hi David, On 25 May 2013 15:23, David Cournapeau <cournape@gmail.com> wrote:
As some of you may know, Stéfan and me will present a tutorial on NumPy C code, so if we do our job correctly, we should have a few new people ready to help out during the sprints.
Is there any chance you'll be repeating this at EuroSciPy? Things I'd like to work on myself is looking into splitting things
from multiarray, think about a better internal API for dtype registration/hooks (with the goal to remove any date dtype hardcoding in both multiarray and ufunc machinery), but I am sure others have more interesting ideas :)
I'm not able to get to SciPy so I understand if my vote of support doesn't count ;-), but I'm very interested in the work on the dtype API. And if it was on the radar for EuroSciPy there's a good chance I'd be able to help out. (The combination of a NumPy C tutorial and dtype API work would make a pretty compelling case for my managers.) Regards, Richard
participants (4)
-
Benjamin Root
-
Charles R Harris
-
David Cournapeau
-
Richard Hattersley