Mailman 3 July 2019 - NumPy-Discussion

Shippable builds are broken - I filed an issue with them
by Matti Picus 04 Jul '19

04 Jul '19

For the past few days shippable (arm builds) CI has been failing. I opened an issue with them https://github.com/Shippable/support/issues/4882

1 0

uarray update: API changes, overhead and comparison to __array_function__
by Hameer Abbasi 03 Jul '19

03 Jul '19

Hello all, I just wrote a blog post on uarray and how it compares against NumPy’s __array_function__ protocol. Give it a read here: https://labs.quansight.org/blog/2019/07/uarray-update-api-changes-overhead-… Best Regards, Hameer Abbasi

1 0

Problem with absolute value
by Nicolas Rougier 03 Jul '19

03 Jul '19

Hi, I’m a bit surprised with the following code: >>> import numpy as np >>> np.seterr(all='warn') >>> Z = np.array([-128], dtype=np.byte) >>> print(np.abs(Z)) [-128] Obviously, it does not return the absolute value and I get no warning. Is it something expected ? (numpy 1.16.4, python 3.7.3) Nicolas

4 5

Top level release index page
by Matti Picus 03 Jul '19

03 Jul '19

In PR 13886 I reworked the way the link to the release notes is generated. The current page is http://www.numpy.org/devdocs/release.html and the new page is https://8001-908607-gh.circle-artifacts.com/0/home/circleci/repo/doc/build/… I don't like the "wall of text" in the current page. On the other hand, it is nice to use CTRL-F to search the page itself for answers to questions like "what release deprecated indexing by float", which is why I left the level-of-detail at 3 (1 - release, 2 - sections, 3 - item header). Should the level-of-detail be reduced to only single links to the release document? An alternative would be to render the contents as a collapsible list, which would require some javascript. Matti

3 2

NumPy Community Meeting Wednesday, July 3
by Sebastian Berg 02 Jul '19

02 Jul '19

Hi all, There will be a NumPy Community meeting Wednesday July 3 at 11 am Pacific Time. Everyone is invited to join in and edit the work-in- progress meeting notes: https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg Best wishes Sebastian _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion(a)python.org https://mail.python.org/mailman/listinfo/numpy-discussion

1 0

ANN: SfePy 2019.2
by Robert Cimrman 02 Jul '19

02 Jul '19

I am pleased to announce release 2019.2 of SfePy. Description ----------- SfePy (simple finite elements in Python) is a software for solving systems of coupled partial differential equations by the finite element method or by the isogeometric analysis (limited support). It is distributed under the new BSD license. Home page: http://sfepy.org Mailing list: https://mail.python.org/mm3/mailman3/lists/sfepy.python.org/ Git (source) repository, issue tracker: https://github.com/sfepy/sfepy Highlights of this release -------------------------- - improved support for time-dependent homogenization problems, - Python 3.7 compatibility For full release notes see [1]. Cheers, Robert Cimrman [1] http://docs.sfepy.org/doc/release_notes.html#id1 --- Contributors to this release in alphabetical order: Robert Cimrman Jan Heczko Lubos Kejzlar Vladimir Lukes

1 0

PyPI NumPy account changes
by Ralf Gommers 30 Jun '19

30 Jun '19

Hi all, PyPI now has taken 2FA (two-factor authentication) in production, which is a useful security measure I think. Also, Tidelift is able to measure which accounts have 2FA enabled. I had a look at our PyPI account, and there were many owners of it. This isn't great from a security perspective. There are two roles on PyPI: maintainer, and owner. Maintainers can upload, owners can add other people and delete the whole account. The old PyPI added anyone as owner by default, that's why we had so many. I already did some cleanup, removing people who having uploaded a release in 8+ years and/or were never a NumPy maintainer. I propose to clean this up a little further. We don't need more than 3-4 owners (for enough redundancy), converting the rest to maintainer or removing them would be better. Ideally everyone would also enable 2FA. Given who now has access, I propose as owners Charles Harris, Matthew Brett and myself. The other people who have access are fairly unlikely to do another release in the near to medium future (or ever), except probably Matti. So I propose that I make them maintainers now, and then send them an email whether they want to keep access or not. Does that sound okay? Cheers, Ralf

1 0