ANyone interested in Google Summer of Code this year? I think the real challenge is having folks with the time to really put into mentoring, but if folks want to do it  numpy could really benefit. Maybe as a python.org subproject? https://wiki.python.org/moin/SummerOfCode/2016 Deadlines are approaching  so I thought I'd ping the list and see if folks are interested. Chris  Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 5266959 voice 7600 Sand Point Way NE (206) 5266329 fax Seattle, WA 98115 (206) 5266317 main reception Chris.Barker@noaa.gov
sir actually i am interested very much . so can you help me about this or suggest some , so that i can contribute . Thanks & Regards, Smruti Ranjan Sahoo On Tue, Feb 9, 2016 at 1:58 AM, Chris Barker <chris.barker@noaa.gov> wrote:
ANyone interested in Google Summer of Code this year?
I think the real challenge is having folks with the time to really put into mentoring, but if folks want to do it  numpy could really benefit.
Maybe as a python.org subproject?
https://wiki.python.org/moin/SummerOfCode/2016
Deadlines are approaching  so I thought I'd ping the list and see if folks are interested.
Chris

Christopher Barker, Ph.D. Oceanographer
Emergency Response Division NOAA/NOS/OR&R (206) 5266959 voice 7600 Sand Point Way NE (206) 5266329 fax Seattle, WA 98115 (206) 5266317 main reception
Chris.Barker@noaa.gov
_______________________________________________ NumPyDiscussion mailing list NumPyDiscussion@scipy.org https://mail.scipy.org/mailman/listinfo/numpydiscussion
As you can see in the timeline: https://developers.google.com/opensource/gsoc/timeline We are now in the stage where mentoring organizations are getting their act together. So the question now is  are there folks that want to mentor for numpy projects? It can be rewarding, but it's a pretty big commitment as well, and, I suppose depending on the project, would require some good knowledge of the innards of numpy  there are not a lot of those folks out there that have that background. So to students, I suggest you keep an eye out, and engage a little later on in the process. That being said, if you have a idea for a numpy improvement you'd like to work on , by all means propose it and maybe you'll get a mentor or two excited. CHB On Mon, Feb 8, 2016 at 3:33 PM, SMRUTI RANJAN SAHOO <c99.smruti@gmail.com> wrote:
sir actually i am interested very much . so can you help me about this or suggest some , so that i can contribute .
Thanks & Regards, Smruti Ranjan Sahoo
On Tue, Feb 9, 2016 at 1:58 AM, Chris Barker <chris.barker@noaa.gov> wrote:
ANyone interested in Google Summer of Code this year?
I think the real challenge is having folks with the time to really put into mentoring, but if folks want to do it  numpy could really benefit.
Maybe as a python.org subproject?
https://wiki.python.org/moin/SummerOfCode/2016
Deadlines are approaching  so I thought I'd ping the list and see if folks are interested.
Chris

Christopher Barker, Ph.D. Oceanographer
Emergency Response Division NOAA/NOS/OR&R (206) 5266959 voice 7600 Sand Point Way NE (206) 5266329 fax Seattle, WA 98115 (206) 5266317 main reception
Chris.Barker@noaa.gov
_______________________________________________ NumPyDiscussion mailing list NumPyDiscussion@scipy.org https://mail.scipy.org/mailman/listinfo/numpydiscussion
_______________________________________________ NumPyDiscussion mailing list NumPyDiscussion@scipy.org https://mail.scipy.org/mailman/listinfo/numpydiscussion
 Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 5266959 voice 7600 Sand Point Way NE (206) 5266329 fax Seattle, WA 98115 (206) 5266317 main reception Chris.Barker@noaa.gov
Is there a clean way of importing existing C code as a vectorized numpy func? Like, it would be awesome to use gdal in a vectorized way just with ctypes or something. Just something I've dreamed of that I thought I'd ask about in regards to the GSoC. Elliot On Feb 8, 2016 6:03 PM, "Chris Barker" <chris.barker@noaa.gov> wrote:
As you can see in the timeline:
https://developers.google.com/opensource/gsoc/timeline
We are now in the stage where mentoring organizations are getting their act together. So the question now is  are there folks that want to mentor for numpy projects? It can be rewarding, but it's a pretty big commitment as well, and, I suppose depending on the project, would require some good knowledge of the innards of numpy  there are not a lot of those folks out there that have that background.
So to students, I suggest you keep an eye out, and engage a little later on in the process.
That being said, if you have a idea for a numpy improvement you'd like to work on , by all means propose it and maybe you'll get a mentor or two excited.
CHB
On Mon, Feb 8, 2016 at 3:33 PM, SMRUTI RANJAN SAHOO <c99.smruti@gmail.com> wrote:
sir actually i am interested very much . so can you help me about this or suggest some , so that i can contribute .
Thanks & Regards, Smruti Ranjan Sahoo
On Tue, Feb 9, 2016 at 1:58 AM, Chris Barker <chris.barker@noaa.gov> wrote:
ANyone interested in Google Summer of Code this year?
I think the real challenge is having folks with the time to really put into mentoring, but if folks want to do it  numpy could really benefit.
Maybe as a python.org subproject?
https://wiki.python.org/moin/SummerOfCode/2016
Deadlines are approaching  so I thought I'd ping the list and see if folks are interested.
Chris

Christopher Barker, Ph.D. Oceanographer
Emergency Response Division NOAA/NOS/OR&R (206) 5266959 voice 7600 Sand Point Way NE (206) 5266329 fax Seattle, WA 98115 (206) 5266317 main reception
Chris.Barker@noaa.gov
_______________________________________________ NumPyDiscussion mailing list NumPyDiscussion@scipy.org https://mail.scipy.org/mailman/listinfo/numpydiscussion
_______________________________________________ NumPyDiscussion mailing list NumPyDiscussion@scipy.org https://mail.scipy.org/mailman/listinfo/numpydiscussion

Christopher Barker, Ph.D. Oceanographer
Emergency Response Division NOAA/NOS/OR&R (206) 5266959 voice 7600 Sand Point Way NE (206) 5266329 fax Seattle, WA 98115 (206) 5266317 main reception
Chris.Barker@noaa.gov
_______________________________________________ NumPyDiscussion mailing list NumPyDiscussion@scipy.org https://mail.scipy.org/mailman/listinfo/numpydiscussion
On Tue, Feb 9, 2016 at 1:02 AM, Chris Barker <chris.barker@noaa.gov> wrote:
As you can see in the timeline:
https://developers.google.com/opensource/gsoc/timeline
We are now in the stage where mentoring organizations are getting their act together. So the question now is  are there folks that want to mentor for numpy projects? It can be rewarding, but it's a pretty big commitment as well, and, I suppose depending on the project, would require some good knowledge of the innards of numpy  there are not a lot of those folks out there that have that background.
Note that we have always done a combined numpy/scipy ideas page and submission. For really good students numpy may be the right challenge, but in general scipy is easier to get started on. So we have difficult project ideas for both, but easy/intermediate ones will most likely be for scipy.
So to students, I suggest you keep an eye out, and engage a little later on in the process.
That being said, if you have a idea for a numpy improvement you'd like to work on , by all means propose it and maybe you'll get a mentor or two excited.
CHB
On Mon, Feb 8, 2016 at 3:33 PM, SMRUTI RANJAN SAHOO <c99.smruti@gmail.com> wrote:
sir actually i am interested very much . so can you help me about this or suggest some , so that i can contribute .
Hi Smruti, I suggest you look at the numpy or scipy issues on Github, and start with one labeled "easyfix".
Thanks & Regards, Smruti Ranjan Sahoo
On Tue, Feb 9, 2016 at 1:58 AM, Chris Barker <chris.barker@noaa.gov> wrote:
I think the real challenge is having folks with the time to really put into mentoring, but if folks want to do it  numpy could really benefit.
Maybe as a python.org subproject?
Under the PSF umbrella has always worked very well, both in terms of communication quality and of getting the amount of slots we wanted, so yes.
https://wiki.python.org/moin/SummerOfCode/2016
Deadlines are approaching  so I thought I'd ping the list and see if folks are interested. ANyone interested in Google Summer of Code this year?
Yes, last year we had quite a productive GSoC, so I had planned to organize it along the same lines again (with an updated ideas page of course). Are you maybe interested in coorganizing or mentoring Chris? Updating the ideas page, proposal reviewing and interviewing students via video calls can be timeconsuming, and mentoring definitely is, so the more the merrier. Cheers, Ralf
Thanks Ralf, Note that we have always done a combined numpy/scipy ideas page and
submission. For really good students numpy may be the right challenge, but in general scipy is easier to get started on.
yup  good idea. Is there a page ready to go, or do we need to get one up? (I don't even know where to put it...)
Under the PSF umbrella has always worked very well, both in terms of communication quality and of getting the amount of slots we wanted, so yes.
hmm, looking here: https://wiki.python.org/moin/SummerOfCode/2016#Suborgs it seems it's time to get started. and I _think_ our ideas page can go on that Wiki.
Are you maybe interested in coorganizing or mentoring Chris? Updating the ideas page, proposal reviewing and interviewing students via video calls can be timeconsuming, and mentoring definitely is, so the more the merrier.
I would love to help  though I don't think I can commit to being a fullon mentor. If we get a couple people to agree to mentor, then we can get ourselves setup up with the PSF. Chris  Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 5266959 voice 7600 Sand Point Way NE (206) 5266329 fax Seattle, WA 98115 (206) 5266317 main reception Chris.Barker@noaa.gov
On Wed, Feb 10, 2016 at 11:48 PM, Chris Barker <chris.barker@noaa.gov> wrote:
Thanks Ralf,
Note that we have always done a combined numpy/scipy ideas page and
submission. For really good students numpy may be the right challenge, but in general scipy is easier to get started on.
yup  good idea. Is there a page ready to go, or do we need to get one up? (I don't even know where to put it...)
This is last year's page: https://github.com/scipy/scipy/wiki/GSoC2015projectideas Some ideas have been worked on, others are still relevant. Let's copy this page to 2016 and start editing it and adding new ideas. I'll start right now actually.
Under the PSF umbrella has always worked very well, both in terms of communication quality and of getting the amount of slots we wanted, so yes.
hmm, looking here:
https://wiki.python.org/moin/SummerOfCode/2016#Suborgs
it seems it's time to get started. and I _think_ our ideas page can go on that Wiki.
Are you maybe interested in coorganizing or mentoring Chris? Updating the ideas page, proposal reviewing and interviewing students via video calls can be timeconsuming, and mentoring definitely is, so the more the merrier.
I would love to help  though I don't think I can commit to being a fullon mentor.
If we get a couple people to agree to mentor,
That's always the tricky part. We normally let people indicate whether they're interested in mentoring for specific project ideas on the ideas page.
then we can get ourselves setup up with the PSF. <https://mail.scipy.org/mailman/listinfo/numpydiscussion>
That's the easiest part, takes one email and one wiki page edit:) Ralf
On Wed, Feb 10, 2016 at 11:55 PM, Ralf Gommers <ralf.gommers@gmail.com> wrote:
On Wed, Feb 10, 2016 at 11:48 PM, Chris Barker <chris.barker@noaa.gov> wrote:
Thanks Ralf,
Note that we have always done a combined numpy/scipy ideas page and
submission. For really good students numpy may be the right challenge, but in general scipy is easier to get started on.
yup  good idea. Is there a page ready to go, or do we need to get one up? (I don't even know where to put it...)
This is last year's page: https://github.com/scipy/scipy/wiki/GSoC2015projectideas
Some ideas have been worked on, others are still relevant. Let's copy this page to 2016 and start editing it and adding new ideas. I'll start right now actually.
OK first version: https://github.com/scipy/scipy/wiki/GSoC2016projectideas I kept some of the ideas from last year, but removed all potential mentors as the same people may not be available this year  please readd yourselves where needed. And to everyone who has a good idea, and preferably is willing to mentor for that idea: please add it to that page. Ralf
Under the PSF umbrella has always worked very well, both in terms of communication quality and of getting the amount of slots we wanted, so yes.
hmm, looking here:
https://wiki.python.org/moin/SummerOfCode/2016#Suborgs
it seems it's time to get started. and I _think_ our ideas page can go on that Wiki.
Are you maybe interested in coorganizing or mentoring Chris? Updating the ideas page, proposal reviewing and interviewing students via video calls can be timeconsuming, and mentoring definitely is, so the more the merrier.
I would love to help  though I don't think I can commit to being a fullon mentor.
If we get a couple people to agree to mentor,
That's always the tricky part. We normally let people indicate whether they're interested in mentoring for specific project ideas on the ideas page.
then we can get ourselves setup up with the PSF. <https://mail.scipy.org/mailman/listinfo/numpydiscussion>
That's the easiest part, takes one email and one wiki page edit:)
Ralf
On Wed, Feb 10, 2016 at 3:02 PM, Ralf Gommers <ralf.gommers@gmail.com> wrote:
OK first version: https://github.com/scipy/scipy/wiki/GSoC2016projectideas I kept some of the ideas from last year, but removed all potential mentors as the same people may not be available this year  please readd yourselves where needed.
And to everyone who has a good idea, and preferably is willing to mentor for that idea: please add it to that page.
Ralf
I removed the "Improve Numpy datetime functionality" project, since the relevant improvements have mostly already made it into NumPy 1.11. We might consider adding "improve duck typing for numpy arrays" if any GSOC students are true masochists ;). I could potentially be a mentor for this one, though of course Nathaniel is the obvious choice. Stephan
We might consider adding "improve duck typing for numpy arrays"
care to elaborate on that one? I know it come up on here that it would be good to have some code in numpy itself that made it easier to make arraylike objects (I.e. do indexing the same way) Is that what you mean? CHB  Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 5266959 voice 7600 Sand Point Way NE (206) 5266329 fax Seattle, WA 98115 (206) 5266317 main reception Chris.Barker@noaa.gov
On Wed, Feb 10, 2016 at 4:22 PM, Chris Barker <chris.barker@noaa.gov> wrote:
We might consider adding "improve duck typing for numpy arrays"
care to elaborate on that one?
I know it come up on here that it would be good to have some code in numpy itself that made it easier to make arraylike objects (I.e. do indexing the same way) Is that what you mean?
I was thinking particularly of improving the compatibility of numpy functions (e.g., concatenate) with nonnumpy arraylike objects, but now that you mention it utilities to make it easier to make arraylike objects could also be a good thing. In any case, I've now elaborated on my thought into a full project idea on the Wiki: https://github.com/scipy/scipy/wiki/GSoC2016projectideas#improvedduckty... Arguably, this might be too difficult for most GSoC students  the API design questions here are quite contentious. But given that "Pythonic dtypes" is up there as a GSoC proposal still it's in good company. Cheers, Stephan
[This is a complete tangent, and so I apologize in advance.] We are considering applying to GSOC for Bokeh. However, I have zero experience with GSOC, but nonzero questions (e.g. go it alone, vs apply through PSF... I think?) If anyone with experience from the mentoring organization side of things wouldn't mind a quick chat (or a few emails) to answer questions, share your experience, or offer advice, please drop me a line directly. Thanks, Bryan
On Feb 17, 2016, at 1:14 AM, Stephan Hoyer <shoyer@gmail.com> wrote:
On Wed, Feb 10, 2016 at 4:22 PM, Chris Barker <chris.barker@noaa.gov> wrote: We might consider adding "improve duck typing for numpy arrays"
care to elaborate on that one?
I know it come up on here that it would be good to have some code in numpy itself that made it easier to make arraylike objects (I.e. do indexing the same way) Is that what you mean?
I was thinking particularly of improving the compatibility of numpy functions (e.g., concatenate) with nonnumpy arraylike objects, but now that you mention it utilities to make it easier to make arraylike objects could also be a good thing.
In any case, I've now elaborated on my thought into a full project idea on the Wiki: https://github.com/scipy/scipy/wiki/GSoC2016projectideas#improvedduckty...
Arguably, this might be too difficult for most GSoC students  the API design questions here are quite contentious. But given that "Pythonic dtypes" is up there as a GSoC proposal still it's in good company.
Cheers, Stephan
_______________________________________________ NumPyDiscussion mailing list NumPyDiscussion@scipy.org https://mail.scipy.org/mailman/listinfo/numpydiscussion
Apparetnly, NumFocus is applyign to be a GSoC Umbrella org as well: https://github.com/numfocus/gsoc Not sure why one might choose NumFocus vs PSF... Chris On Wed, Feb 17, 2016 at 6:05 AM, Bryan Van de Ven <bryanv@continuum.io> wrote:
[This is a complete tangent, and so I apologize in advance.]
We are considering applying to GSOC for Bokeh. However, I have zero experience with GSOC, but nonzero questions (e.g. go it alone, vs apply through PSF... I think?) If anyone with experience from the mentoring organization side of things wouldn't mind a quick chat (or a few emails) to answer questions, share your experience, or offer advice, please drop me a line directly.
Thanks,
Bryan
On Feb 17, 2016, at 1:14 AM, Stephan Hoyer <shoyer@gmail.com> wrote:
On Wed, Feb 10, 2016 at 4:22 PM, Chris Barker <chris.barker@noaa.gov> wrote: We might consider adding "improve duck typing for numpy arrays"
care to elaborate on that one?
I know it come up on here that it would be good to have some code in numpy itself that made it easier to make arraylike objects (I.e. do indexing the same way) Is that what you mean?
I was thinking particularly of improving the compatibility of numpy functions (e.g., concatenate) with nonnumpy arraylike objects, but now that you mention it utilities to make it easier to make arraylike objects could also be a good thing.
In any case, I've now elaborated on my thought into a full project idea on the Wiki:
https://github.com/scipy/scipy/wiki/GSoC2016projectideas#improvedduckty...
Arguably, this might be too difficult for most GSoC students  the API
design questions here are quite contentious. But given that "Pythonic dtypes" is up there as a GSoC proposal still it's in good company.
Cheers, Stephan
_______________________________________________ NumPyDiscussion mailing list NumPyDiscussion@scipy.org https://mail.scipy.org/mailman/listinfo/numpydiscussion
_______________________________________________ NumPyDiscussion mailing list NumPyDiscussion@scipy.org https://mail.scipy.org/mailman/listinfo/numpydiscussion
 Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 5266959 voice 7600 Sand Point Way NE (206) 5266329 fax Seattle, WA 98115 (206) 5266317 main reception Chris.Barker@noaa.gov
On Wed, Feb 17, 2016 at 12:57 PM, Chris Barker <chris.barker@noaa.gov> wrote:
Apparetnly, NumFocus is applyign to be a GSoC Umbrella org as well:
https://github.com/numfocus/gsoc
Not sure why one might choose NumFocus vs PSF...
No reason to choose, you can get students from both orgs.
Chris
On Wed, Feb 17, 2016 at 6:05 AM, Bryan Van de Ven <bryanv@continuum.io> wrote:
[This is a complete tangent, and so I apologize in advance.]
We are considering applying to GSOC for Bokeh. However, I have zero experience with GSOC, but nonzero questions (e.g. go it alone, vs apply through PSF... I think?) If anyone with experience from the mentoring organization side of things wouldn't mind a quick chat (or a few emails) to answer questions, share your experience, or offer advice, please drop me a line directly.
Thanks,
Bryan
On Feb 17, 2016, at 1:14 AM, Stephan Hoyer <shoyer@gmail.com> wrote:
On Wed, Feb 10, 2016 at 4:22 PM, Chris Barker <chris.barker@noaa.gov> wrote: We might consider adding "improve duck typing for numpy arrays"
care to elaborate on that one?
I know it come up on here that it would be good to have some code in numpy itself that made it easier to make arraylike objects (I.e. do indexing the same way) Is that what you mean?
I was thinking particularly of improving the compatibility of numpy functions (e.g., concatenate) with nonnumpy arraylike objects, but now that you mention it utilities to make it easier to make arraylike objects could also be a good thing.
In any case, I've now elaborated on my thought into a full project idea on the Wiki:
https://github.com/scipy/scipy/wiki/GSoC2016projectideas#improvedduckty...
Arguably, this might be too difficult for most GSoC students  the API
design questions here are quite contentious. But given that "Pythonic dtypes" is up there as a GSoC proposal still it's in good company.
Cheers, Stephan
_______________________________________________ NumPyDiscussion mailing list NumPyDiscussion@scipy.org https://mail.scipy.org/mailman/listinfo/numpydiscussion
_______________________________________________ NumPyDiscussion mailing list NumPyDiscussion@scipy.org https://mail.scipy.org/mailman/listinfo/numpydiscussion

Christopher Barker, Ph.D. Oceanographer
Emergency Response Division NOAA/NOS/OR&R (206) 5266959 voice 7600 Sand Point Way NE (206) 5266329 fax Seattle, WA 98115 (206) 5266317 main reception
Chris.Barker@noaa.gov
_______________________________________________ NumPyDiscussion mailing list NumPyDiscussion@scipy.org https://mail.scipy.org/mailman/listinfo/numpydiscussion
On Wed, Feb 10, 2016 at 11:55 PM, Ralf Gommers <ralf.gommers@gmail.com> wrote:
<snip>
This is last year's page: https://github.com/scipy/scipy/wiki/GSoC2015projectideas
Some ideas have been worked on, others are still relevant. Let's copy this page to 2016 and start editing it and adding new ideas. I'll start right now actually.
OK first version: https://github.com/scipy/scipy/wiki/GSoC2016projectideas I kept some of the ideas from last year, but removed all potential mentors as the same people may not be available this year  please readd yourselves where needed.
Thanks Ralf for doing it! Just a quick note on delisted projects. While I do not disagree with removing the projects on splines and special functions, this IMO does not mean we won't consider proposals on either of these topics if someone wants to write one. For instance, if Josh or Ted want to frame their work on hypergeometric functions as a GSoC project, I'm sure we're going to at least consider these. Evgeni
Thu, 11 Feb 2016 00:02:52 +0100, Ralf Gommers kirjoitti: [clip]
OK first version: https://github.com/scipy/scipy/wiki/GSoC2016projectideas I kept some of the ideas from last year, but removed all potential mentors as the same people may not be available this year  please readd yourselves where needed.
And to everyone who has a good idea, and preferably is willing to mentor for that idea: please add it to that page.
I probably don't have bandwidth for mentoring, but as the Numpy suggestions seem to be mostly "hard" problems, we can add another one: ## Dealing with overlapping input/output data Numpy operations where output arrays overlap with input arrays can produce unexpected results. A simple example is ``` x = np.arange(100*100).reshape(100,100) x += x.T # < undefined result! ``` The task is to change Numpy so that the results here become similar to as if the input arrays overlapping with output were separate (here: `x += x.T.copy()`). The challenge here lies in doing this without sacrificing too much performance or memory efficiency. Initial steps toward solving this problem were taken in https://github.com/numpy/numpy/pull/6166 where a simplest available algorithm for detecting if arrays overlap was added. However, this is not yet utilized in ufuncs. An initial attempt to sketch what should be done is at https://github.com/numpy/numpy/issues/6272 and issues referenced therein.
On Fr, 20160304 at 21:20 +0000, Pauli Virtanen wrote:
Thu, 11 Feb 2016 00:02:52 +0100, Ralf Gommers kirjoitti: [clip]
OK first version: https://github.com/scipy/scipy/wiki/GSoC2016projectideas I kept some of the ideas from last year, but removed all potential mentors as the same people may not be available this year  please readd yourselves where needed.
And to everyone who has a good idea, and preferably is willing to mentor for that idea: please add it to that page.
I probably don't have bandwidth for mentoring, but as the Numpy suggestions seem to be mostly "hard" problems, we can add another one:
## Dealing with overlapping input/output data
Numpy operations where output arrays overlap with input arrays can produce unexpected results. A simple example is ``` x = np.arange(100*100).reshape(100,100) x += x.T # < undefined result! ``` The task is to change Numpy so that the results here become similar to as if the input arrays overlapping with output were separate (here: `x += x.T.copy()`). The challenge here lies in doing this without sacrificing too much performance or memory efficiency.
Initial steps toward solving this problem were taken in https://github.com/numpy/numpy/pull/6166 where a simplest available algorithm for detecting if arrays overlap was added. However, this is not yet utilized in ufuncs. An initial attempt to sketch what should be done is at https://github.com/numpy/numpy/issues/6272 and issues referenced therein.
Since I like the idea, I copy pasted it into the GSoC project ideas wiki.  Sebastian
_______________________________________________ NumPyDiscussion mailing list NumPyDiscussion@scipy.org https://mail.scipy.org/mailman/listinfo/numpydiscussion
participants (10)

Andy Ray Terrel

Bryan Van de Ven

Chris Barker

Elliot Hallmark

Evgeni Burovski

Pauli Virtanen

Ralf Gommers

Sebastian Berg

SMRUTI RANJAN SAHOO

Stephan Hoyer