Mailman 3 September 2015 - NumPy-Discussion

Numpy 1.10.0rc2 released
by Charles R Harris 29 Sep '15

29 Sep '15

Hi all, I'm pleased to announce the availability of Numpy 1.10.0rc12. Sources and 32 bit binary packages for Windows may be found at Sourceforge <https://sourceforge.net/projects/numpy/files/NumPy/1.10.0rc2/?upload_just_c…>. There have been a few fixes since rc1. If there are no more problems I hope to release the final in a week or so. Cheers Chuck

1 0

New version of "scipy lecture notes"
by Gael Varoquaux 28 Sep '15

28 Sep '15

Dear Pythonistas, We have just released a new version of the "scipy lecture notes": http://www.scipy-lectures.org/ These are a consistent set of materials to learn the core aspects of the scientific Python ecosystem, from beginner to expert. They are written and maintained by a set of volunteers and published under a CC-BY license. Highlights of the latest version includes: * a chapter giving a introduction to statistics in Python * a new layout with emphasis on readability including on small devices * fully doctesting for Python 2 and 3 compatibility We hope that you will find these notes useful, for you, your colleagues, or your students. Gaël

1 0

Including .f2py_f2cmap in numpy.distutils?
by Eric Hermes 28 Sep '15

28 Sep '15

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 double. I have the proper mapping set up in a .f2py_f2cmap in the source directory, but it does not seem to be copied to the build directory at compile time, and I cannot figure out how to make it get copied. Is there a simple way to do what I am trying to do? Alternatively, is there a way to specify the mapping in my setup.py scripts? Here's a github repo with the project: https://github.com/ehermes/ased3 Thanks, Eric Hermes

2 1

Fixing the dtype of np.full's return value
by Antony Lee 27 Sep '15

27 Sep '15

Hi all, The docstring of np.full indicates that the result of the dtype is `np.array(fill_value).dtype`, as long as the keyword argument `dtype` itself is not set. This is actually not the case: the current implementation always returns a float array when `dtype` is not set, see e.g. In [1]: np.full(1, 1) Out[1]: array([ 1.]) In [2]: np.full(1, None) Out[2]: array([ nan]) In [3]: np.full(1, None).dtype Out[3]: dtype('float64') In [4]: np.array(None) Out[4]: array(None, dtype=object) The note about return value of the dtype was actually explicitly discussed in https://github.com/numpy/numpy/pull/2875 but the tests failed to cover the case where the `dtype` argument is not passed. We could either change the docstring to match the current behavior, or fix the behavior to match what the docstring says (my preference). @njsmith mentioned in https://github.com/numpy/numpy/issues/6366 that this may be acceptable as a bug fix, as "it's a very new function so there probably aren't many people relying on it" (it was introduced in 1.8). I guess the options are: - Fix the behavior outright and squeeze this in 1.10 as a bugfix (my preference). - Emit a warning in 1.10, fix in 1.11. - Do nothing for 1.10, warn in 1.11, fix in 1.12 (at that point the argument of `np.full` being a very new function starts becoming invalid...). - Change the docstring. Thoughts? Antony

2 1

Numpy 1.10.0rc2 coming Monday, Sep 28.
by Charles R Harris 27 Sep '15

27 Sep '15

Hi All, Just a heads up. If you have encountered any unreported errors with rc1, please let us know. Chuck

1 0

Python needs goto
by Charles R Harris 25 Sep '15

25 Sep '15

At last, goto for python <https://github.com/snoack/python-goto>! Usage: from goto import with_goto @with_goto def range(start, stop): i = start result = [] label .begin if i == stop: goto .end result.append(i) i += 1 goto .begin label .end return result HT: LWN Chuck

10 18

"Numpy for Matlab Users" is missing
by Thomas Haslwanter 25 Sep '15

25 Sep '15

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

2 1

ANN: Numpy 1.10.0rc1 released.
by Charles R Harris 24 Sep '15

24 Sep '15

Hi all, I'm pleased to announce the availability of Numpy 1.10.0rc1. Sources and 32 bit binary packages for Windows may be found at Sourceforge <https://sourceforge.net/projects/numpy/files/NumPy/1.10.0rc1/?upload_just_c…>. Please test this out, as I would like to move to the final release as rapidly as possible and the lack of error reports from the beta has left me nervous. It's been quiet, too quiet. In the movies, we would all die in the next five minutes. Cheers Chuck

6 9

Re: [Numpy-discussion] Python needs goto
by R Schumacher 24 Sep '15

24 Sep '15

An older non-decorator implementation, with examples (slower) http://entrian.com/goto/ At 04:25 AM 9/24/2015, you wrote: >Hello. > >Can you give an example where GOTO is useful ? >LeÂ 24 sept. 2015 07:24, "Charles R Harris" ><<mailto:charlesr.harris@gmail.com>charlesr.harris(a)gmail.com> a Ã©critÂ : >At last, <https://github.com/snoack/python-goto>goto for python! > >Usage: >from goto import with_goto > > >@with_goto > >def range(start, stop): > > i = start > > result = [] > > > label .begin > > if i == stop: > > goto .end > > > result.append(i) > > i += 1 > > goto .begin > > > label .end > > return result > >HT: LWN > >Chuck > >_______________________________________________ >NumPy-Discussion mailing list ><mailto:NumPy-Discussion@scipy.org>NumPy-Discussion(a)scipy.org >https://mail.scipy.org/mailman/listinfo/numpy-discussion > >_______________________________________________ >NumPy-Discussion mailing list >NumPy-Discussion(a)scipy.org >https://mail.scipy.org/mailman/listinfo/numpy-discussion

1 0

Re: [Numpy-discussion] "Become an Open Source Contributor" workshop
by Scott Collis 24 Sep '15

24 Sep '15

Hey Jamie, List, Having just come back from a conference where our toolkit, Py-ART [1] has picked up a nice following of people keen to contribute I was wondering if you will be opening this up via a google hangout or similar? I would love to advertise this to our users. We all want more contributors and a big roadblock is understanding the fork and pull request system of GitHub We did run a course that had some GitGub etc here: https://github.com/scollis/SusSoPrac You are welcome to use anything liberally! Cheers, Scott On 9/23/15 4:39 PM, numpy-discussion-request(a)scipy.org wrote: > Send NumPy-Discussion mailing list submissions to > numpy-discussion(a)scipy.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mail.scipy.org/mailman/listinfo/numpy-discussion > or, via email, send a message with subject or body 'help' to > numpy-discussion-request(a)scipy.org > > You can reach the person managing the list at > numpy-discussion-owner(a)scipy.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of NumPy-Discussion digest..." > > > Today's Topics: > > 1. "Become an Open Source Contributor" workshop > (Jaime Fern?ndez del R?o) > 2. Re: composition of the steering council (was Re: Governance > model request) (Travis Oliphant) > 3. Re: Governance model request (Stefan van der Walt) > 4. Re: Governance model request (Matthew Brett) > 5. Re: composition of the steering council (was Re: Governance > model request) (Chris Barker) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 23 Sep 2015 14:06:08 -0700 > From: Jaime Fern?ndez del R?o <jaime.frio(a)gmail.com> > To: SciPy Developers List <scipy-dev(a)scipy.org>, Discussion of > Numerical Python <numpy-discussion(a)scipy.org> > Subject: [Numpy-discussion] "Become an Open Source Contributor" > workshop > Message-ID: > <CAPOWHWnk7mNm64_FuQkV5KCX=vxAyctBh7P1X7KbcaMgohSAOg(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Apologies for the cross-posting. > > The Data Science Student Society of the University of California San Diego, > or DS3 @ UCSD as they like to call themselves, will be holding biweekly > Python themed workshops starting this fall. On the week of October 19th, > they will be having yours truly doing a "Become an Open Source Contributor" > piece. It will be a shortish event, 60-90 minutes, so my idea was to cover > the following: > > 1. (15 min) An introduction to the Python data science landscape. > 2. (30 min) An overview of the GitHub workflow that most (all?) of the > projects follow. > 3. (30-45 min) A hands on session, where we would make sure everyone > gets set up in GitHub, and forks and clones their favorite project. Time > and participant willingness permitting, I would like to take advantage of > my commit bits, and have some of the participants submit a simple PR, e.g. > fixing a documentation typo, to NumPy or SciPy, and hit the green button > right there, so that they get to leave as knighted FOSS contributors. > > And this is what I am hoping to get from you, the community: > > 1. If anyone in the area would like to get involved, please contact me. > I have recruited a couple of volunteers from PySanDiego, but could use more > help. > 2. I'm also hoping to get some help, especially with the introductory > part. Given that the crowd will mostly be university students and some > faculty, it would be great if someone who actually knew what they were > talking about could deliver a short, 10 minute talk, on Python, data > science, and academia. I'm sure we could arrange it to have someone join > by video conference. > 3. If you have organized anything similar in the past, and have material > that I could use to, ahem, draw inspiration from, or recommendations to > make, or whatever, I'd love to hear from you. > > Thanks for reading! > > Jaime >

1 0