On Mon, Mar 27, 2017 at 11:33 PM, Julian Taylor < jtaylor.debian@googlemail.com> wrote:

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

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

On 27.03.2017 10:41, Ralf Gommers wrote:

...

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 http://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* mailto: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 mailto:numfocus@googlegroups.com, devs@numfocus.org mailto: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 mailto:info@numfocus.org

Best, Gina

On Thu, Mar 16, 2017 at 1:13 PM, Bob Carpenter mailto:carp@alias-i.com> wrote:

Is there a format you're expecting for proposals?

Are applications limited to one per project?

Hard to imagine a project won't have something to do with $3K, so I imagine you'll get applications from all of the projects if the proposals take less than an hour or two to put together.

- Bob

> On Mar 16, 2017, at 12:14 PM, Gina Helfrich mailto:gina@numfocus.org> wrote: > > Call for Proposals - Small Development Grants > > NumFOCUS is asking for proposals from its sponsored and affiliated projects for targeted small development projects with a clear benefit to those projects. This call is motivated by the success of our 2016 end-of-year fundraising drive; we want to direct the donated funds to our projects in a way that has impact and visibility to donors and the wider community. > > There are no restrictions on what the funding can be used for. Whether it’s code development, documentation work, an educational, sustainability or diversity initiative, or yet something else, we trust the projects themselves to understand what they need and explain that need in the proposal. > > Available Funding: > • Up to $3,000 per proposal > • Allocated funding is $9,000; depending on the number and quality of proposals this may be adjusted up or down. > > Eligibility: > • Proposals must be approved by the leadership of a NumFOCUS sponsored or affiliated project. > • Proposed work must have a clear outcome, achievable within 2017. > • The call is open to applicants from any nationality and can be performed at any university, institute or business worldwide (US export laws permitting). > > Timeline: > • Mid-March 2017: Call for Proposals released > • 3 April 2017: deadline for proposal submissions > • 17 April: successful proposals announced > > -- > Dr. Gina Helfrich > Communications Director, NumFOCUS > gina@numfocus.org mailto:gina@numfocus.org > 512-222-5449 tel:512-222-5449 > > > > > -- > 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 mailto:numfocus%2Bunsubscribe@googlegroups.com. > For more options, visit https://groups.google.com/d/optout < https://groups.google.com/d/optout>.

-- 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 mailto:numfocus%2Bunsubscribe@googlegroups.com. For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout.

-- Dr. Gina Helfrich Communications Director, NumFOCUS gina@numfocus.org mailto:gina@numfocus.org 512-222-5449 tel:(512)%20222-5449

http://www.numfocus.org https://twitter.com/NumFOCUShttps://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 mailto:numfocus+unsubscribe@googlegroups.com. For more options, visit https://groups.google.com/d/optout https://groups.google.com/d/optout.

_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion

_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion

On Mar 31, 2017 1:15 AM, "Ralf Gommers" wrote: On Mon, Mar 27, 2017 at 11:42 PM, Ralf Gommers wrote:

On Mon, Mar 27, 2017 at 11:33 PM, Julian Taylor < jtaylor.debian@googlemail.com> wrote:

...

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

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?

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

On Fri, Mar 31, 2017 at 8:07 AM, Julian Taylor < jtaylor.debian@googlemail.com> wrote:

On 31.03.2017 15:51, Nathaniel Smith wrote:

...

On Mar 31, 2017 1:15 AM, "Ralf Gommers" mailto:ralf.gommers@gmail.com> wrote:

On Mon, Mar 27, 2017 at 11:42 PM, Ralf Gommers mailto:ralf.gommers@gmail.com> wrote:

On Mon, Mar 27, 2017 at 11:33 PM, Julian Taylor mailto:jtaylor.debian@googlemail.com> wrote:

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 https://github.com/numpy/numpy/pull/4208

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?

More thoughts on this anyone? Or preferences for this idea or the numpy.org http://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

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.

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

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

wrote:

On 31.03.2017 16:07, Julian Taylor wrote:

...

On 31.03.2017 15:51, Nathaniel Smith wrote:

...

On Mar 31, 2017 1:15 AM, "Ralf Gommers" mailto:ralf.gommers@gmail.com> wrote:

On Mon, Mar 27, 2017 at 11:42 PM, Ralf Gommers mailto:ralf.gommers@gmail.com> wrote:

On Mon, Mar 27, 2017 at 11:33 PM, Julian Taylor mailto:jtaylor.debian@googlemail.com> wrote:

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 https://github.com/numpy/numpy/pull/4208

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?

More thoughts on this anyone? Or preferences for this idea or the numpy.org http://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

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.

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-file-in-to-a-numpy-array-tt35992.html#a36003 # loadtxt https://github.com/numpy/numpy/pull/4208 # genfromtxt http://numpy-discussion.10968.n7.nabble.com/genfromtxt- universal-newline-support-td37816.html https://github.com/dhomeier/numpy/commit/995ec93 _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion

-- Renato Fabbri GNU/Linux User #479299 labmacambira.sourceforge.net

On Mon, Mar 27, 2017 at 3:33 AM, Julian Taylor < jtaylor.debian@googlemail.com> wrote:

- 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.

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