Re: [Numpy-discussion] Python needs goto

goto! and comefrom! Together with exceptions, threads, lambda, super, generators, and coroutines, all we're lacking is call-with-current-continuation for the full list of impenetrable control-flow constructs. Oh, and lisp-style resumable exception handling. (Suggested syntax: drop(exception,

Re: [Numpy-discussion] Python needs goto

> On Sep 25, 2015, at 1:53 AM, Alexander Eberspächer > wrote: > > On 24.09.2015 21:12, Charles R Harris wrote: > >> I find Cleve Moler's old Fortran version of Brent's zero finding >> algorithm using gotos clearer than the structured versions you can find >> in

Re: [Numpy-discussion] Python needs goto

Very funny !  Le 25 sept. 2015 07:53, "Alexander Eberspächer" a écrit : > On 24.09.2015 21:12, Charles R Harris wrote: > > > I find Cleve Moler's old Fortran version of Brent's zero finding > > algorithm using gotos clearer than the structured versions you can find

Re: [Numpy-discussion] Python needs goto

On Fri, Sep 25, 2015 at 10:27 AM, Anne Archibald wrote: > goto! and comefrom! Together with exceptions, threads, lambda, super, > generators, and coroutines, all we're lacking is > call-with-current-continuation for the full list of impenetrable > control-flow constructs.

Re: [Numpy-discussion] Python needs goto

On Sep 25, 2015 11:06 AM, "Charles R Harris" wrote: > > > > On Fri, Sep 25, 2015 at 10:27 AM, Anne Archibald wrote: >> >> goto! and comefrom! Together with exceptions, threads, lambda, super, generators, and coroutines, all we're lacking is

Re: [Numpy-discussion] "Numpy for Matlab Users" is missing

The wiki is down, presumably as part of this: https://github.com/numpy/numpy/issues/6325 On Sep 25, 2015 1:22 PM, "Thomas Haslwanter" wrote: > Does anybody know what happened to the following links on the NumPy > homepage (http://www.numpy.org/): > > >-

Re: [Numpy-discussion] Python needs goto

On Fri, Sep 25, 2015 at 3:02 PM, Nathaniel Smith wrote: > > The coroutines in 3.5 are just syntactic sugar around features that were > added in *2*.5 (yield expressions and yield from), so no need to wait :-). > They fall far short of arbitrary continuations, though. >

[Numpy-discussion] "Numpy for Matlab Users" is missing

Does anybody know what happened to the following links on the NumPy homepage (http://www.numpy.org/): - http://wiki.scipy.org/Wiki/NumPy_for_Matlab_Users - http://www.numpy.org/ - http://wiki.scipy.org/Numpy_Functions_by_Category They have not been available for some time now ...

[Numpy-discussion] Including .f2py_f2cmap in numpy.distutils?

Hello, I am attempting to set up a numpy.distutils setup.py for a small python program that uses a Fortran module. Currently, the setup is able to compile and install the program seemingly successfully, but the f2py script erroneously maps the data types I am using to float, rather than

Re: [Numpy-discussion] Python needs goto

Ow! Ow! Ow! I am just a meteorologist that has an obsession with looking up unfamiliar technology terms. I need a Tylenol... Ben Root On Fri, Sep 25, 2015 at 12:27 PM, Anne Archibald wrote: > goto! and comefrom! Together with exceptions, threads, lambda, super, >

Re: [Numpy-discussion] Python needs goto

On Fri, Sep 25, 2015 at 2:39 PM, Ryan May wrote: > > On Fri, Sep 25, 2015 at 3:02 PM, Nathaniel Smith wrote: >> >> The coroutines in 3.5 are just syntactic sugar around features that were >> added in *2*.5 (yield expressions and yield from), so no need to wait

Re: [Numpy-discussion] composition of the steering council (was Re: Governance model request)

On Fri, Sep 25, 2015 at 7:25 AM, Marten van Kerkwijk wrote: [...] > > p.s. Independently of rules, I don't see how Travis would not qualify even > from current work, given that he has just committed to actively try to > improve/generalize dtype. Just to clarify what's

Re: [Numpy-discussion] composition of the steering council (was Re: Governance model request)

On Thu, Sep 24, 2015 at 10:45 AM, David Cournapeau wrote: > > On Thu, Sep 24, 2015 at 10:45 AM, Sebastian Berg > wrote: >> [...] >> About using the commit log to seed, I think there are some old term >> contributers (David Cournapeau maybe?), who

Re: [Numpy-discussion] composition of the steering council (was Re: Governance model request)

[Travis: sorry for writing all this referring to you in third person -- I guess it might feel a bit awkward to read! You're certainly part of the intended audience, but then it felt even more awkward trying to write in second person... this is clearly a bug in English.] Hi all, On Wed, Sep 23,

Re: [Numpy-discussion] composition of the steering council (was Re: Governance model request)

To respond to the devils advocate: Creating this organizational framework is a one time boot-strapping event. You could use wording like "The initial council will include those who have made significant contributions to numpy in the past and want to be on it" or "The initial council will be

Re: [Numpy-discussion] composition of the steering council (was Re: Governance model request)

Hi Nathaniel, Piping in again from the outside: being on council would certainly seem to be a job not a privilege, and I suspect it will be hard enough to find people willing to actually put in work to worry about restricting membership overly. Given this, my suggestion would be to have a

Re: [Numpy-discussion] composition of the steering council (was Re: Governance model request)

On Mi, 2015-09-23 at 19:48 -0500, Travis Oliphant wrote: > > > On Wed, Sep 23, 2015 at 6:19 PM, Charles R Harris > wrote: > > > On Wed, Sep 23, 2015 at 3:42 PM, Chris Barker > wrote: > On Wed,