Fwd: [numfocus] Grants up to $3k available to NumFOCUS projects (sponsored & affiliated)
![](https://secure.gravatar.com/avatar/5f88830d19f9c83e2ddfd913496c5025.jpg?s=120&d=mm&r=g)
Hi all, For those who did not see the call on the NumFOCUS list, the below may be of interest. I also have a proposal idea: a redesign of numpy.org. Our website is very poor, both in terms of content and design. If a good designer spends 40 hours on it, that should be enough to change it into something nice (or at least not embarassing). What do you think? Other ideas? Cheers, Ralf ---------- Forwarded message ---------- From: Gina Helfrich <gina@numfocus.org> Date: Fri, Mar 17, 2017 at 10:51 AM Subject: Re: [numfocus] Grants up to $3k available to NumFOCUS projects (sponsored & affiliated) To: numfocus@googlegroups.com, devs@numfocus.org There is no specific template, but proposals should be kept under 2 pages. Maximum 1 submission per project. Required elements of the proposal are: - title - project description - benefit to project/community - project team - and budget Submit proposals to info@numfocus.org Best, Gina On Thu, Mar 16, 2017 at 1:13 PM, Bob Carpenter <carp@alias-i.com> wrote:
-- Dr. Gina Helfrich Communications Director, NumFOCUS gina@numfocus.org 512-222-5449 <(512)%20222-5449> <http://www.numfocus.org> <https://twitter.com/NumFOCUS> <https://www.facebook.com/NumFOCUS/> -- You received this message because you are subscribed to the Google Groups "NumFOCUS" group. To unsubscribe from this group and stop receiving emails from it, send an email to numfocus+unsubscribe@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
![](https://secure.gravatar.com/avatar/c0da24f75f763b6bac90b519064f30b3.jpg?s=120&d=mm&r=g)
I have two ideas under one big important topic: make numpy python3 compatible. The first fits pretty well with the grant size and nobody wants to do it for free: - fix our text IO functions under python3 and support multiple encodings, not only latin1. Reasonably simple to do, slap encoding arguments on the functions, generate test cases and somehow keep backward compatibility. Some prelimary unfinished work is in https://github.com/numpy/numpy/pull/4208 - add ascii/latin1 dtype to support a compact python3 string array, deprecate 's' dtype which has different meaning in python2 and 3 This one is probably too big for 3k though. On 27.03.2017 10:41, Ralf Gommers wrote:
![](https://secure.gravatar.com/avatar/5f88830d19f9c83e2ddfd913496c5025.jpg?s=120&d=mm&r=g)
On Mon, Mar 27, 2017 at 11:33 PM, Julian Taylor < jtaylor.debian@googlemail.com> wrote:
I like that idea, it's a recurring pain point. Are you interested to work on it, or are you thinking to advertise the idea here to see if anyone steps up? - add ascii/latin1 dtype to support a compact python3 string array,
deprecate 's' dtype which has different meaning in python2 and 3 This one is probably too big for 3k though.
Agreed, that won't fit in such a small grant. Ralf
![](https://secure.gravatar.com/avatar/5f88830d19f9c83e2ddfd913496c5025.jpg?s=120&d=mm&r=g)
On Mon, Mar 27, 2017 at 11:42 PM, Ralf Gommers <ralf.gommers@gmail.com> wrote:
More thoughts on this anyone? Or preferences for this idea or the numpy.org one? Submission deadline is April 3rd and we can only put in one proposal this time, so we need to (a) make a choice between these ideas, and (b) write up a proposal. If there's not enough replies to this so the choice is clear cut, I will send out a poll to the core devs. Ralf
![](https://secure.gravatar.com/avatar/97c543aca1ac7bbcfb5279d0300c8330.jpg?s=120&d=mm&r=g)
On Mar 31, 2017 1:15 AM, "Ralf Gommers" <ralf.gommers@gmail.com> wrote: On Mon, Mar 27, 2017 at 11:42 PM, Ralf Gommers <ralf.gommers@gmail.com> wrote:
More thoughts on this anyone? Or preferences for this idea or the numpy.org one? Submission deadline is April 3rd and we can only put in one proposal this time, so we need to (a) make a choice between these ideas, and (b) write up a proposal. If there's not enough replies to this so the choice is clear cut, I will send out a poll to the core devs. Do we have anyone interested in doing the work in either case? That seems like the most important consideration to me... -n
![](https://secure.gravatar.com/avatar/c0da24f75f763b6bac90b519064f30b3.jpg?s=120&d=mm&r=g)
On 31.03.2017 15:51, Nathaniel Smith wrote:
I could do the textio thing if no one shows up for numpy.org. I can probably check again what is required in the next few days and write a proposal. The change will need reviewing in the end too, should that be compensated too? It feels weird if not.
![](https://secure.gravatar.com/avatar/96dd777e397ab128fedab46af97a3a4a.jpg?s=120&d=mm&r=g)
On Fri, Mar 31, 2017 at 8:07 AM, Julian Taylor < jtaylor.debian@googlemail.com> wrote:
Note that we would also like to bring over the text input implementation from pandas. There was general agreement back when we met in (2015?) that that would be desirable, but it has never come to pass. Chuck
![](https://secure.gravatar.com/avatar/c0da24f75f763b6bac90b519064f30b3.jpg?s=120&d=mm&r=g)
On 31.03.2017 16:07, Julian Taylor wrote:
I have decided to not do it, as it is more or less just a bugfix and I currently do not feel capable of doing with added completion pressure. But I have collected some of related issues and discussions: https://github.com/numpy/numpy/issues/4600 https://github.com/numpy/numpy/issues/3184 http://numpy-discussion.10968.n7.nabble.com/using-loadtxt-to-load-a-text-fil... # loadtxt https://github.com/numpy/numpy/pull/4208 # genfromtxt http://numpy-discussion.10968.n7.nabble.com/genfromtxt-universal-newline-sup... https://github.com/dhomeier/numpy/commit/995ec93
![](https://secure.gravatar.com/avatar/422d1e676b8b2434ccd73b49c234537f.jpg?s=120&d=mm&r=g)
maybe OT, but is has become recurrent to me for already some years to make a very simple module for obtaining arrays related to musical elements. All here: https://github.com/ttm/dissertacao scripts/ have Python/Numpy has implementions of the musical elements. dissertacaoCorrigida.pdf holds a thorough description of the framework. I idealize it as a module inside Numpy but I understand it might be reasonable to do it as a Scipy kit. I handed my doctorate a few days ago and might be willing to put some time into this. PS. long time no post. Hello! On Mon, Apr 3, 2017 at 8:28 AM, Julian Taylor <jtaylor.debian@googlemail.com
wrote:
-- Renato Fabbri GNU/Linux User #479299 labmacambira.sourceforge.net
![](https://secure.gravatar.com/avatar/5f88830d19f9c83e2ddfd913496c5025.jpg?s=120&d=mm&r=g)
On Mon, Apr 3, 2017 at 11:28 PM, Julian Taylor < jtaylor.debian@googlemail.com> wrote:
Fair enough. Had a plan, but my weekend went a bit different than planned so couldn't follow up on it.
Good call Julian. I struggled with the same thing - had a designer to do the numpy.org work, but that still needed someone to do the content, review, etc. Decided not to try to take that on, because I'm already struggling to keep up.
But I have collected some of related issues and discussions:
Thanks, I'm sure that'll be of use at some point. Ralf
![](https://secure.gravatar.com/avatar/5dde29b54a3f1b76b2541d0a4a9b232c.jpg?s=120&d=mm&r=g)
On Mon, Mar 27, 2017 at 3:33 AM, Julian Taylor < jtaylor.debian@googlemail.com> wrote:
probably -- but not THAT big -- it seems pretty straightforward to me. The bigger challenge is deciding what to do -- the bikeshedding -- and the backward incompatibility issues. IIRC, when this came up on the list, there was nothing like consensus on exactly what to do and how to do it. -CHB -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker@noaa.gov
![](https://secure.gravatar.com/avatar/c0da24f75f763b6bac90b519064f30b3.jpg?s=120&d=mm&r=g)
I have two ideas under one big important topic: make numpy python3 compatible. The first fits pretty well with the grant size and nobody wants to do it for free: - fix our text IO functions under python3 and support multiple encodings, not only latin1. Reasonably simple to do, slap encoding arguments on the functions, generate test cases and somehow keep backward compatibility. Some prelimary unfinished work is in https://github.com/numpy/numpy/pull/4208 - add ascii/latin1 dtype to support a compact python3 string array, deprecate 's' dtype which has different meaning in python2 and 3 This one is probably too big for 3k though. On 27.03.2017 10:41, Ralf Gommers wrote:
![](https://secure.gravatar.com/avatar/5f88830d19f9c83e2ddfd913496c5025.jpg?s=120&d=mm&r=g)
On Mon, Mar 27, 2017 at 11:33 PM, Julian Taylor < jtaylor.debian@googlemail.com> wrote:
I like that idea, it's a recurring pain point. Are you interested to work on it, or are you thinking to advertise the idea here to see if anyone steps up? - add ascii/latin1 dtype to support a compact python3 string array,
deprecate 's' dtype which has different meaning in python2 and 3 This one is probably too big for 3k though.
Agreed, that won't fit in such a small grant. Ralf
![](https://secure.gravatar.com/avatar/5f88830d19f9c83e2ddfd913496c5025.jpg?s=120&d=mm&r=g)
On Mon, Mar 27, 2017 at 11:42 PM, Ralf Gommers <ralf.gommers@gmail.com> wrote:
More thoughts on this anyone? Or preferences for this idea or the numpy.org one? Submission deadline is April 3rd and we can only put in one proposal this time, so we need to (a) make a choice between these ideas, and (b) write up a proposal. If there's not enough replies to this so the choice is clear cut, I will send out a poll to the core devs. Ralf
![](https://secure.gravatar.com/avatar/97c543aca1ac7bbcfb5279d0300c8330.jpg?s=120&d=mm&r=g)
On Mar 31, 2017 1:15 AM, "Ralf Gommers" <ralf.gommers@gmail.com> wrote: On Mon, Mar 27, 2017 at 11:42 PM, Ralf Gommers <ralf.gommers@gmail.com> wrote:
More thoughts on this anyone? Or preferences for this idea or the numpy.org one? Submission deadline is April 3rd and we can only put in one proposal this time, so we need to (a) make a choice between these ideas, and (b) write up a proposal. If there's not enough replies to this so the choice is clear cut, I will send out a poll to the core devs. Do we have anyone interested in doing the work in either case? That seems like the most important consideration to me... -n
![](https://secure.gravatar.com/avatar/c0da24f75f763b6bac90b519064f30b3.jpg?s=120&d=mm&r=g)
On 31.03.2017 15:51, Nathaniel Smith wrote:
I could do the textio thing if no one shows up for numpy.org. I can probably check again what is required in the next few days and write a proposal. The change will need reviewing in the end too, should that be compensated too? It feels weird if not.
![](https://secure.gravatar.com/avatar/96dd777e397ab128fedab46af97a3a4a.jpg?s=120&d=mm&r=g)
On Fri, Mar 31, 2017 at 8:07 AM, Julian Taylor < jtaylor.debian@googlemail.com> wrote:
Note that we would also like to bring over the text input implementation from pandas. There was general agreement back when we met in (2015?) that that would be desirable, but it has never come to pass. Chuck
![](https://secure.gravatar.com/avatar/c0da24f75f763b6bac90b519064f30b3.jpg?s=120&d=mm&r=g)
On 31.03.2017 16:07, Julian Taylor wrote:
I have decided to not do it, as it is more or less just a bugfix and I currently do not feel capable of doing with added completion pressure. But I have collected some of related issues and discussions: https://github.com/numpy/numpy/issues/4600 https://github.com/numpy/numpy/issues/3184 http://numpy-discussion.10968.n7.nabble.com/using-loadtxt-to-load-a-text-fil... # loadtxt https://github.com/numpy/numpy/pull/4208 # genfromtxt http://numpy-discussion.10968.n7.nabble.com/genfromtxt-universal-newline-sup... https://github.com/dhomeier/numpy/commit/995ec93
![](https://secure.gravatar.com/avatar/422d1e676b8b2434ccd73b49c234537f.jpg?s=120&d=mm&r=g)
maybe OT, but is has become recurrent to me for already some years to make a very simple module for obtaining arrays related to musical elements. All here: https://github.com/ttm/dissertacao scripts/ have Python/Numpy has implementions of the musical elements. dissertacaoCorrigida.pdf holds a thorough description of the framework. I idealize it as a module inside Numpy but I understand it might be reasonable to do it as a Scipy kit. I handed my doctorate a few days ago and might be willing to put some time into this. PS. long time no post. Hello! On Mon, Apr 3, 2017 at 8:28 AM, Julian Taylor <jtaylor.debian@googlemail.com
wrote:
-- Renato Fabbri GNU/Linux User #479299 labmacambira.sourceforge.net
![](https://secure.gravatar.com/avatar/5f88830d19f9c83e2ddfd913496c5025.jpg?s=120&d=mm&r=g)
On Mon, Apr 3, 2017 at 11:28 PM, Julian Taylor < jtaylor.debian@googlemail.com> wrote:
Fair enough. Had a plan, but my weekend went a bit different than planned so couldn't follow up on it.
Good call Julian. I struggled with the same thing - had a designer to do the numpy.org work, but that still needed someone to do the content, review, etc. Decided not to try to take that on, because I'm already struggling to keep up.
But I have collected some of related issues and discussions:
Thanks, I'm sure that'll be of use at some point. Ralf
![](https://secure.gravatar.com/avatar/5dde29b54a3f1b76b2541d0a4a9b232c.jpg?s=120&d=mm&r=g)
On Mon, Mar 27, 2017 at 3:33 AM, Julian Taylor < jtaylor.debian@googlemail.com> wrote:
probably -- but not THAT big -- it seems pretty straightforward to me. The bigger challenge is deciding what to do -- the bikeshedding -- and the backward incompatibility issues. IIRC, when this came up on the list, there was nothing like consensus on exactly what to do and how to do it. -CHB -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chris.Barker@noaa.gov
participants (6)
-
Charles R Harris
-
Chris Barker
-
Julian Taylor
-
Nathaniel Smith
-
Ralf Gommers
-
Renato Fabbri