[Numpy-discussion] welcome Andrew Nelson to the NumPy maintainers team

Hi all, On behalf of the steering council, I am very happy to announce that Andrew is joining the Maintainers team. Andrew has been contributing to our CI setup in particular for the past year, and has contributed for example the Cirrus CI setup and the musllinux builds: https://github.com/numpy/n

[Numpy-discussion] Re: NEP 55 - Add a UTF-8 Variable-Width String DType to NumPy

On Tue, Aug 29, 2023 at 4:08 PM Nathan wrote: > The NEP was merged in draft form, see below. > > https://numpy.org/neps/nep-0055-string_dtype.html > This is a really nice NEP, thanks Nathan! I see that questions and constructive feedback is still coming in on GitHub, but for now it seems like ev

[Numpy-discussion] Re: reminder: put an upper bound on setuptools if you use numpy.distutils!

On Thu, Aug 31, 2023 at 6:39 PM Kevin Sheppard wrote: > > > On Sun, Aug 21, 2022 at 6:36 PM Ralf Gommers > wrote: > >> Hi all, >> >> After setuptools 65.0 was released a few days ago, all users of >> numpy.distutils had their builds broken. This is alread

[Numpy-discussion] Re: [SciPy-Dev] Re: NumPy 1.26.0rc1 released

in this >> release. The changelog doesn't capture the full extent of the work, special >> thanks to Ralf Gommers, Sayed Adel, Stéfan van der Walt, and Matti Picus >> who did much of the work in the main development branch. >> >> > Thanks for doing the release Chu

[Numpy-discussion] Proposal to accept NEP 52 (Python API cleanup for 2.0)

Hi all, A lot of work has been happening to implement NEP 52 ( https://numpy.org/neps/nep-0052-python-api-cleanup.html) over the past 1.5 months - mostly work by Mateusz Sokol, and review effort of Sebastian, Nathan and myself. The majority of API changes have been made. There's more to do of cour

[Numpy-discussion] Re: Proposal to accept NEP 52 (Python API cleanup for 2.0)

h work. That is explained in the PR that updates the NEP (https://github.com/numpy/numpy/pull/24620). Cheers, Ralf > On 15 Sep 2023, at 21:12, Ralf Gommers wrote: > > Hi all, > > A lot of work has been happening to implement NEP 52 ( > https://numpy.org/neps/nep-0052-python-

[Numpy-discussion] Re: NEP 55 - Add a UTF-8 Variable-Width String DType to NumPy

On Wed, Sep 20, 2023 at 8:26 AM Warren Weckesser wrote: > > > On Fri, Sep 15, 2023 at 3:18 PM Warren Weckesser < > warren.weckes...@gmail.com> wrote: > > > > > > > > On Mon, Sep 11, 2023 at 12:25 PM Nathan > wrote: > >> > >> > >> > >> On Sun, Sep 3, 2023 at 10:54 AM Warren Weckesser < > warren.w

[Numpy-discussion] Re: Assessment of the difficulty in porting CPU architecture for numpy

Hi Xuanbao, On Thu, Nov 16, 2023 at 2:59 PM xuanbao via NumPy-Discussion < numpy-discussion@python.org> wrote: > Hello everyone! I am working on implementing a tool to assess the > complexity of CPU architecture porting. It primarily focuses on RISC-V > architecture porting. In fact, the tool may

[Numpy-discussion] Re: Meson - C extension - Finding numpy includes in virtual env

On Sun, Nov 26, 2023 at 9:06 PM Nathan wrote: > I want to caution about using `pip install -e .` to get a development > install of numpy. This will work fine working on numpy itself, but won’t be > useful if you need to use the development version of numpy to build another > library. This doesn’t

[Numpy-discussion] Re: Telling meson build which CBLAS/LAPACK (LAPACKE?) to use via pkgconfig module

On Mon, Nov 27, 2023 at 2:10 PM Dr. Thomas Orgis < thomas.or...@uni-hamburg.de> wrote: > Hi, > > I'm involved in packaging NumPy for http://pkgsrc.org/. We install a > set of possible BLAS/CBLAS/LAPACK/LAPACKE packages side-by-side in the > same prefix. This includes multiple variants of OpenBLAS

[Numpy-discussion] Re: Telling meson build which CBLAS/LAPACK (LAPACKE?) to use via pkgconfig module

On Mon, Nov 27, 2023 at 6:51 PM Dr. Thomas Orgis < thomas.or...@uni-hamburg.de> wrote: > Am Mon, 27 Nov 2023 14:58:45 +0100 > schrieb Ralf Gommers : > > > The NumPy build does not know anything about this. It will just build, > and > > it will simply call the Open

[Numpy-discussion] Re: Telling meson build which CBLAS/LAPACK (LAPACKE?) to use via pkgconfig module

On Wed, Dec 6, 2023 at 1:32 AM Dr. Thomas Orgis wrote: > Am Sun, 3 Dec 2023 19:54:10 +0100 > schrieb "Dr. Thomas Orgis" : > > > > You have to go through a "build frontend" to produce a wheel, which > then > > > gets installed/repackaged for your distro. > > > > This is obviously happening in pkgs

[Numpy-discussion] updated 2.0-dev nightlies, including macOS Accelerate wheels

Hi all, We had some issues with nightlies, the macOS, Linux aarch64 and PyPy ones were about a month out of date. That is fixed now, new nightlies for all supported platforms are up on https://anaconda.org/scientific-python-nightly-wheels/numpy. Note that a lot changed in `main` over the last mon

[Numpy-discussion] NEP 54 - SIMD infrastructure evolution to C++ and adopting Google Highway

odule ). Cheers, Ralf full text of the NEP: === NEP 54 — SIMD infrastructure evolution: adopting Google Highway when moving to C++? === :Author: Sayed Adel, Jan Wassenberg, Matti Picus, Ralf Gommers, Chris Sidebottom :

[Numpy-discussion] Fwd: incomplete BLAS/CBLAS linking (Telling meson build which CBLAS/LAPACK (LAPACKE?) to use via pkgconfig module)

(I took this off-list unintentionally, so I'm forward each email to the list now) -- Forwarded message - From: Ralf Gommers Date: Thu, Dec 28, 2023 at 8:51 PM Subject: Re: incomplete BLAS/CBLAS linking (Telling meson build which CBLAS/LAPACK (LAPACKE?) to use via pkgc

[Numpy-discussion] Fwd: incomplete BLAS/CBLAS linking (Telling meson build which CBLAS/LAPACK (LAPACKE?) to use via pkgconfig module)

-- Forwarded message - From: Dr. Thomas Orgis Date: Fri, Dec 29, 2023 at 12:00 AM Subject: Re: incomplete BLAS/CBLAS linking (Telling meson build which CBLAS/LAPACK (LAPACKE?) to use via pkgconfig module) To: Ralf Gommers Am Thu, 28 Dec 2023 20:51:27 +0100 schrieb Ralf Gommers

[Numpy-discussion] Re: incomplete BLAS/CBLAS linking (Telling meson build which CBLAS/LAPACK (LAPACKE?) to use via pkgconfig module)

(re-sending to list) On Fri, Dec 29, 2023 at 11:34 AM Ralf Gommers wrote: > > > On Fri, Dec 29, 2023 at 12:00 AM Dr. Thomas Orgis < > thomas.or...@uni-hamburg.de> wrote: > >> Am Thu, 28 Dec 2023 20:51:27 +0100 >> schrieb Ralf Gommers : >> >>

[Numpy-discussion] Re: incomplete BLAS/CBLAS linking (Telling meson build which CBLAS/LAPACK (LAPACKE?) to use via pkgconfig module)

On Sat, Dec 30, 2023 at 1:57 PM Dr. Thomas Orgis < thomas.or...@uni-hamburg.de> wrote: > > Am Fri, 29 Dec 2023 11:34:04 +0100 > schrieb Ralf Gommers : > > > If the library name is libcblas.so it will still be found. If it's also a > > nonstandard name, then yes

[Numpy-discussion] NEP 56: array API standard support in the main numpy namespace

nt conceptual/design comments, please post them on this thread. Cheers, Ralf = NEP 56 — Array API standard support in NumPy's main namespace ========= :Author: Ralf Gommers :Autho

[Numpy-discussion] Re: Proposal to accept NEP 55: Add a UTF-8 variable-width string DType to NumPy

On Wed, Jan 24, 2024 at 10:43 AM Sebastian Berg wrote: > On Mon, 2024-01-22 at 17:08 -0700, Nathan wrote: > > Hi all, > > > > I propose we accept NEP 55 and merge PR #25347 implementing the NEP > > in time > > for the NumPy 2.0 RC: > > > I really like this work and I think it is a big improvement

[Numpy-discussion] welcome Raghuveer, Chris, Mateusz and Matt to the NumPy maintainers team

Hi all, We've got four new NumPy maintainers! Welcome to the team, and congratulations to: - Raghuveer Devulapalli (https://github.com/r-devulap) - Chris Sidebottom (https://github.com/mousius) - Mateusz Sokół (https://github.com/mtsokol/) - Matt Haberland (https://github.com/mdhaber) Raghuveer

[Numpy-discussion] Re: donation from the Bloomberg FOSS Contributor Fund

On Wed, Jan 31, 2024 at 1:34 PM Inessa Pawson wrote: > The NumPy Steering Council is excited to announce that we have received a > $10k grant from the Bloomberg FOSS Contributor Fund. We appreciate > Bloomberg’s commitment to sustaining critical digital infrastructure and > thank all the Bloomber

[Numpy-discussion] Re: ENH: Introducing a pipe Method for Numpy arrays

On Fri, Feb 16, 2024 at 12:40 AM Marten van Kerkwijk wrote: > > From my experience, calling methods is generally faster than > > functions. I figure it is due to having less overhead figuring out the > > input. Maybe it is not significant for large data, but it does make a > > difference even whe

[Numpy-discussion] Re: Numpy wheels: who maintains the builds and who pays for it?

On Thu, Feb 22, 2024 at 7:03 PM wrote: > Hi folks, > > My name is Sean and I'm the author of several GIS packages using Numpy: > Fiona, Rasterio, and Shapely. Hi Sean, thanks for this very good question, and for all your work on GIS packages. > I've followed Numpy's trail when it comes to whe

[Numpy-discussion] Re: Need help in numpy building from source on windows.

On Mon, Feb 26, 2024 at 3:26 PM rajoraganesh--- via NumPy-Discussion < numpy-discussion@python.org> wrote: > detailed proble can be found at - > https://stackoverflow.com/questions/78059816/issues-in-buildingnumpy-from-source-on-windows Quick answers: 1. Please don't build 1.26.0, but 1.26.4. Th

[Numpy-discussion] Re: JSON format for multi-dimensional data

On Sun, Feb 25, 2024 at 12:34 AM wrote: > > > Perhaps, like the Pandas package, it should live outside NumPy for a > > while until some wider consensus could emerge. > > Regarding this initial remark, this is indeed a possible option but it > depends on the answer to the question: > > - does Nu

[Numpy-discussion] Re: builing numpy on windows

On Wed, Feb 28, 2024 at 6:54 AM Ganesh Rajora via NumPy-Discussion < numpy-discussion@python.org> wrote: > Hi Team, > > I am Ganesh working for an MNC here in India and I am working on > customised Python where I build set of python modules with python. > > I do not install them directly from web

[Numpy-discussion] Re: JSON format for multi-dimensional data

On Tue, Feb 27, 2024 at 3:45 PM wrote: > Thanks Ralf, > > This answers my question about the absence of I/O Numpy format. > > There are three other points related to this format proposal: > > - integration of a semantic level above the number / character formats as > for datetime (e.g. units, poi

[Numpy-discussion] Re: Improved 2DFFT Approach

On Wed, Feb 28, 2024 at 6:59 AM camrymanjr--- via NumPy-Discussion < numpy-discussion@python.org> wrote: > Good day! > > My name is Alexander Levin. > > My colleague and I did a project on optimisation of two-dimensional > Fourier transform algorithm six months ago. We took your implementation of

[Numpy-discussion] Updating NEP statuses, and accepting NEP 56

Hi all, Each NEP has a status, which should be indicative of the state that the proposal is in, and that determines in what category it's shown on https://numpy.org/neps/. We have been neglecting to update status on a fair number of NEPs for a long time. I thought I'd fix that - see https://github

[Numpy-discussion] Re: numpy 2.0.x has been branched.

On Sat, Mar 9, 2024 at 2:03 AM Oscar Benjamin wrote: > On Sat, 9 Mar 2024 at 00:44, Charles R Harris > wrote: > > > > About a month from now. > > What will happen about a month from now? It might seem obvious to you > but I can interpret this in different ways. > > To be clear numpy 2.0 is expec

[Numpy-discussion] Re: Automatic Clipping of array to upper / lower bounds of dtype

On Sat, Mar 9, 2024 at 11:23 PM Dom Grigonis wrote: > Hello, > > Can't find answer to this anywhere. > > What I would like is to automatically clip the values if they breach the > bounds. > > I have done a simple clipping, and overwritten __iadd__, __isub__, > __setitem__, … > > But I am wanderin

[Numpy-discussion] Re: Automatic Clipping of array to upper / lower bounds of dtype

oops each) Ralf > > Regards, > dg > > > On 10 Mar 2024, at 09:59, Ralf Gommers wrote: > > > > On Sat, Mar 9, 2024 at 11:23 PM Dom Grigonis > wrote: > >> Hello, >> >> Can't find answer to this anywhere. >> >> What I would

[Numpy-discussion] Re: Which generation of s390x CPU and how to change it?

On Mon, Mar 25, 2024 at 2:24 PM Matěj Cepl wrote: > Hello, > > As a maintainer of Python packages for openSUSE/SUSE, > I would like to ask for help with our bug > https://bugzilla.suse.com/1221902. It seems to us that the latest > version of NumPy suddenly requires z15 CPU generation, although >

[Numpy-discussion] Re: numpy 2.0.x has been branched.

On Tue, Mar 26, 2024 at 1:20 AM Charles R Harris wrote: > > > On Mon, Mar 25, 2024 at 5:54 PM Oscar Benjamin > wrote: > >> On Sat, 9 Mar 2024 at 10:16, Ralf Gommers wrote: >> > >> > On Sat, Mar 9, 2024 at 2:03 AM Oscar Benjamin < >> oscar.j.benj

[Numpy-discussion] Re: numpy 2.0.x has been branched.

On Fri, Mar 29, 2024 at 2:07 PM Peter Hawkins wrote: > It looks like the pybind11 release is now done ( > https://github.com/pybind/pybind11/releases/tag/v2.12.0)? Any more > blockers? > No more blockers - CI is running on the last backport that we need I believe, so it's very close. Hours to ma

[Numpy-discussion] Re: Moving the weekly traige/community meetings

On Mon, Apr 8, 2024 at 5:37 PM Nathan wrote: > That time work for me, I have a conflict with the old time an hour earlier > than the current time so hopefully that works for everyone. > One hour later works for me too. Cheers, Ralf On Sun, Apr 7, 2024 at 8:34 PM Matti Picus wrote: > >> Could

[Numpy-discussion] Re: Making show_runtime and show_config enable file output

On Mon, Apr 8, 2024 at 9:42 PM Matan Addam wrote: > Hello, > > I find the information printed by the above mentioned functions to be > useful for understanding performance context on installed machines, as well > as variability across machines when troubleshooting. How would the > maintainers vie

[Numpy-discussion] Re: Making show_runtime and show_config enable file output

On Wed, Apr 10, 2024 at 4:18 PM Ganesh Kathiresan wrote: > Thanks for the input, I have raised a PR: > https://github.com/numpy/numpy/pull/26255. I'll address the UT issues > soon. Let me know if this is what was required. > Thanks Ganesh! ___ NumPy-Di

[Numpy-discussion] Re: Please consider dropping Python 3.9 support for Numpy 2.0

On Mon, May 6, 2024 at 10:42 PM Oscar Benjamin wrote: > On Mon, 6 May 2024 at 19:59, Aaron Meurer wrote: > > > > On Mon, May 6, 2024 at 6:34 AM Mark Harfouche > wrote: > > > > > > I'm asking that you let Python 3.9 support disappear with 1.26, and > not "drop a final version" before you decide

[Numpy-discussion] Re: Please consider dropping Python 3.9 support for Numpy 2.0

On Mon, May 6, 2024 at 11:43 PM Aaron Meurer wrote: > On Mon, May 6, 2024 at 3:05 PM Ralf Gommers > wrote: > > > > > So, I think I'm in favor of dropping Python 3.9 support after all to > prevent problems. It is late in the game, but I do see that we're goin

[Numpy-discussion] Re: Please consider dropping Python 3.9 support for Numpy 2.0

On Tue, May 7, 2024 at 7:48 AM Juan Nunez-Iglesias wrote: > On Tue, 7 May 2024, at 7:04 AM, Ralf Gommers wrote: > > This problem could have been avoided by proper use of upper bounds. > Scikit-image 0.22 not including a `numpy<2.0` upper bound is a bug in > scikit-image (

[Numpy-discussion] Re: Please consider dropping Python 3.9 support for Numpy 2.0

On Tue, May 7, 2024 at 11:44 AM Gael Varoquaux < gael.varoqu...@normalesup.org> wrote: > On Tue, May 07, 2024 at 11:31:02AM +0200, Ralf Gommers wrote: > > make `pip install scikit-image==0.22` work if that version of > scikit-image depends on an unconstrained numpy version. >

[Numpy-discussion] Re: Please consider dropping Python 3.9 support for Numpy 2.0

On Thu, May 9, 2024 at 12:28 AM Thomas Caswell wrote: > I think the spirit of NEP 29 is to pick your supported Python's when you > pick a target release date and you should then stick to it (to avoid "we > delayed so long we are over a cliff" decisions like this one). > That's true I believe.

[Numpy-discussion] Re: Please consider dropping Python 3.9 support for Numpy 2.0

On Fri, May 10, 2024 at 11:28 PM Brigitta Sipőcz < b.sipocz+numpyl...@gmail.com> wrote: > Hi, > > Is there any way to know if other large libraries hasn't set an upper pin > in their last release but since then dropped python version support? > This should be doable with either the PyPI JSON API

[Numpy-discussion] Re: Please consider dropping Python 3.9 support for Numpy 2.0

On Sun, May 12, 2024 at 8:39 PM Gael Varoquaux < gael.varoqu...@normalesup.org> wrote: > On Fri, May 10, 2024 at 04:42:49PM +0200, Ralf Gommers wrote: > > It gets ever-easier to install new Python versions, with > pyenv/conda/etc. The "my single Python install comes fr

[Numpy-discussion] Re: Build NumPy with Debugging Symbols with Meson

On Wed, May 15, 2024 at 10:56 PM Robert McLeod wrote: > Hi everyone, > > Is there a gist or similar guide anywhere on the steps required to build > NumPy with debugging symbols on the Windows platform using the new Meson > build system? It seems a bit difficult because NumPy seems to expect a > `

[Numpy-discussion] Re: ERROR: Module "features" does not exist

On Thu, May 16, 2024 at 2:18 PM Thomas Mansencal wrote: > Hello, > > We have a custom and unusual build environment that is making things a bit > difficult to transition from the old Setuptools based build process to > Meson. I'm currently blocked at the CPU feature set detection: > > ``` > [task

[Numpy-discussion] ANN: NumPy 2.0 release date: 16 June 2024

Hi all, In yesterday's community meeting we discussed the 2.0 release schedule, and concluded that we are far enough along to pick a date for the final 2.0 release. That date will be June 16 (barring any major last-minute blockers appearing of course). A quick timeline: - `maintenance/2.0.x` bran

[Numpy-discussion] updating the NumPy roadmap

Hi all, Now that the dust has settled on what we're including in the NumPy 2.0 release, it felt like a good time to update the project roadmap. After a few discussions with other maintainers I opened https://github.com/numpy/numpy/pull/26505. Part of it is a regular maintenance update: remove what

[Numpy-discussion] Re: Policy on AI-generated code

On Thu, Jul 4, 2024 at 12:55 PM Matthew Brett wrote: > Sorry - reposting from my subscribed address: > > Hi, > > Sorry to top-post! But - I wanted to bring the discussion back to > licensing. I have great sympathy for the ecological and code-quality > concerns, but licensing is a separate quest

[Numpy-discussion] Re: Policy on AI-generated code

On Thu, Jul 4, 2024 at 1:34 PM Matthew Brett wrote: > Hi, > > On Thu, Jul 4, 2024 at 12:20 PM Ralf Gommers > wrote: > > > > > > > > On Thu, Jul 4, 2024 at 12:55 PM Matthew Brett > wrote: > >> > >> Sorry - reposting from my subscribed add

[Numpy-discussion] Re: Policy on AI-generated code

On Thu, Jul 4, 2024 at 5:08 PM Matthew Brett wrote: > Hi, > > On Thu, Jul 4, 2024 at 3:41 PM Ralf Gommers > wrote: > > > > > > > > On Thu, Jul 4, 2024 at 1:34 PM Matthew Brett > wrote: > >> > >> Hi, > >> > >> On Thu, Ju

[Numpy-discussion] Re: Policy on AI-generated code

On Thu, Jul 4, 2024 at 8:42 PM Matthew Brett wrote: > Hi, > > On Thu, Jul 4, 2024 at 6:44 PM Ralf Gommers > wrote: > > > > > > > > On Thu, Jul 4, 2024 at 5:08 PM Matthew Brett > wrote: > >> > >> Hi, > >> > >> On Thu, J

[Numpy-discussion] Re: Windows 11 arm64 wheel

On Thu, Jul 11, 2024 at 2:20 PM Andrew Nelson wrote: > > > On Thu, Jul 11, 2024, 22:08 slobodan.miletic--- via NumPy-Discussion < > numpy-discussion@python.org> wrote: > >> Hi, >> >> I am writing on behalf of my team from Endava company. Our task is to >> work with opensource community, and setup

[Numpy-discussion] Re: PR - can I get a new review?

On Mon, Jul 22, 2024 at 3:36 AM Jake S. wrote: > Hi all, it's been a couple of months, so I'm asking for a review again > of my typing PR. Original > reviewer requested a useful additional feature, but hasn't been able to > provide feedback since then.

[Numpy-discussion] Re: Musllinux image bump to 1_2

On Sun, Aug 11, 2024 at 1:29 PM Andrew Nelson wrote: > Dear list, > PR https://github.com/numpy/numpy/pull/27088 contains changes to bump the > musllinux image to 1_2 from 1_1. This is because the 1_1 image is end of > life (https://github.com/pypa/manylinux/issues/1629) > > At the moment the int

[Numpy-discussion] Re: Windows 11 arm64 wheel

On Mon, Aug 12, 2024 at 12:23 PM Matti Picus wrote: > On 12/08/2024 11:55, slobodan.miletic--- via NumPy-Discussion wrote: > > > As the bug fix is merged we are starting the investigation on the CI job. > > I have a few questions about this: > > 1) Are there some additional instructions for makin

[Numpy-discussion] mailing list moved

Hi all, This mailing list moved, it's now numpy-discussion@python.org. Please update the stored address in the contacts list of your email client - messages sent to @scipy.org will not arrive anymore. Cheers, Ralf ___ NumPy-Discussion mailing list NumP

Re: [Numpy-discussion] migration of all scipy.org mailing lists

On Fri, Mar 24, 2017 at 9:57 PM, Ralf Gommers wrote: > On Fri, Mar 24, 2017 at 12:27 AM, Neal Becker wrote: > >> Ralf Gommers wrote: >> >> > On Thu, Mar 23, 2017 at 12:18 AM, Neal Becker >> wrote: >> > >> >> Has anyone taken care of notif

[Numpy-discussion] Fwd: [numfocus] Grants up to $3k available to NumFOCUS projects (sponsored & affiliated)

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 som

Re: [Numpy-discussion] Fwd: [numfocus] Grants up to $3k available to NumFOCUS projects (sponsored & affiliated)

ng 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 m

Re: [Numpy-discussion] migration of all scipy.org mailing lists

On Tue, Mar 28, 2017 at 8:22 AM, Pauli Virtanen wrote: > Sun, 26 Mar 2017 21:05:47 +1300, Ralf Gommers kirjoitti: > [clip] > > The move is complete, and I have updated the mailing list addresses at: > > - http://scipy.org/scipylib/mailing-lists.html (done) > > -

Re: [Numpy-discussion] migration of all scipy.org mailing lists

On Tue, Mar 28, 2017 at 8:50 AM, Ralf Gommers wrote: > > > On Tue, Mar 28, 2017 at 8:22 AM, Pauli Virtanen wrote: > >> Sun, 26 Mar 2017 21:05:47 +1300, Ralf Gommers kirjoitti: >> [clip] >> > The move is complete, and I have updated the mailing list addresses at:

Re: [Numpy-discussion] Fwd: SciPy2017 Sprints FinAid for sprint leaders/core devs

On Thu, Mar 30, 2017 at 10:55 AM, Stefan van der Walt wrote: > On Wed, Mar 29, 2017, at 13:01, Charles R Harris wrote: > > On Tue, Mar 28, 2017 at 5:16 PM, Nathaniel Smith wrote: > > In case anyone is interested in helping run a NumPy sprint at SciPy this > year: > > > I haven't found numpy spri

Re: [Numpy-discussion] Fwd: SciPy2017 Sprints FinAid for sprint leaders/core devs

On Fri, Mar 31, 2017 at 11:59 AM, Sebastian Berg wrote: > On Thu, 2017-03-30 at 22:46 +1300, Ralf Gommers wrote: > > > > > > > Agreed, and I would call that productive. Getting even one new > > maintainer involved is worth organizing multiple sprints for. &

Re: [Numpy-discussion] Fwd: [numfocus] Grants up to $3k available to NumFOCUS projects (sponsored & affiliated)

On Mon, Mar 27, 2017 at 11:42 PM, Ralf Gommers wrote: > > > On Mon, Mar 27, 2017 at 11:33 PM, Julian Taylor < > jtaylor.deb...@googlemail.com> wrote: > >> I have two ideas under one big important topic: make numpy python3 >> compatible. >> >> The f

Re: [Numpy-discussion] Fwd: [numfocus] Grants up to $3k available to NumFOCUS projects (sponsored & affiliated)

On Mon, Apr 3, 2017 at 11:28 PM, Julian Taylor < jtaylor.deb...@googlemail.com> 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.gomm...@gm

Re: [Numpy-discussion] Long term plans for dropping Python 2.7

On Sat, Apr 15, 2017 at 5:19 PM, Nathaniel Smith wrote: > On Fri, Apr 14, 2017 at 5:19 PM, Charles R Harris > wrote: > > Hi All, > > > > It may be early to discuss dropping support for Python 2.7, but there is > a > > disturbance in the force that suggests that it might be worth looking > > forw

Re: [Numpy-discussion] Long term plans for dropping Python 2.7

On Sat, Apr 15, 2017 at 7:02 PM, Nathaniel Smith wrote: > On Fri, Apr 14, 2017 at 10:47 PM, Ralf Gommers > wrote: > > > > > > On Sat, Apr 15, 2017 at 5:19 PM, Nathaniel Smith wrote: > [...] > >> From numpy's perspective, I feel like the most important

Re: [Numpy-discussion] Relaxed stride checking fixup

On Thu, Apr 20, 2017 at 6:28 AM, Charles R Harris wrote: > Hi All, > > Currently numpy master has a bogus stride that will cause an error when > downstream projects misuse it. That is done in order to help smoke out > errors. Previously that bogus stride has been fixed up for releases, but > that

Re: [Numpy-discussion] np.diff on boolean arrays now raises

On Thu, Jun 15, 2017 at 7:08 PM, Jaime Fernández del Río < jaime.f...@gmail.com> wrote: > There is an ongoing discussion on github: > > https://github.com/numpy/numpy/issues/9251 > > In 1.13 np.diff has started raising on boolean arrays, since subtraction > of boolean arrays is now deprecated. >

[Numpy-discussion] ANN: SciPy 0.19.1 release

== SciPy 0.19.1 is a bug-fix release with no new features compared to 0.19.0. The most important change is a fix for a severe memory leak in ``integrate.quad``. Authors === * Evgeni Burovski * Patrick Callier + * Yu Feng * Ralf Gommers * Ilhan Polat * Eric Quintero * Scott Sievert

Re: [Numpy-discussion] proposed changes to array printing in 1.14

On Sat, Jul 1, 2017 at 7:04 AM, CJ Carey wrote: > Is it feasible/desirable to provide a doctest runner that ignores > whitespace? > Yes, and yes. Due to doctest being in the stdlib that is going to take forever to have any effect though; a separate our-sane-doctest module would be the way to shi

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

On Fri, Jun 30, 2017 at 6:50 AM, Pauli Virtanen wrote: > Charles R Harris kirjoitti 29.06.2017 klo 20:45: > > Here's a random idea: how about building a NumPy gallery? > > scikit-{image,learn} has it, and while those projects may have more > > visual datasets, I can imagine something

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

> Matplotlib >> > > and a few other projects have migrated their docs over to use >> > > it. >> > > >> > > https://sphinx-gallery.readthedocs.io/en/latest/ >> > > <https://sphinx-gallery.readthedocs.io/en/latest/> >> > > >

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

rd. Ralf > Peter > > On Wed, Jul 5, 2017 at 10:43 AM, Ralf Gommers > wrote: > > > > Better platform test coverage would be a useful topic if someone is > willing > > to work on that. NumPy needs OS X testing enabled on TravisCI, SciPy > needs > > O

Re: [Numpy-discussion] pytest and degrees of separation.

On Wed, Jul 12, 2017 at 11:06 AM, Chris Barker wrote: > > > On Tue, Jul 11, 2017 at 5:04 PM, Thomas Caswell > wrote: > >> Going with option 2 is probably the best option so that you can use >> pytest fixtures and parameterization. >> > > I agree -- those are worth a lot! > Maybe I'm dense, but

Re: [Numpy-discussion] pytest and degrees of separation.

On Thu, Jul 13, 2017 at 8:14 AM, Pauli Virtanen wrote: > Charles R Harris kirjoitti 12.07.2017 klo 13:53: > > In practice, that would generally be true, but the nose testing tools > > were 1, all nose imports were buried in functions that ran during > > testing. Whether or not that was by intent

[Numpy-discussion] Fwd: [NumFOCUS Projects] Important: 2017 NumFOCUS Summit & Sustainability Workshop

Hi all, This is a public service announcement: for the first time NumFOCUS is organising a sustainability workshop, details below. NumPy is able to send two representatives; the NumPy steering committee chose Chuck and Nathaniel. I'll be present as well as NumFOCUS board member. Last year there wa

[Numpy-discussion] NumPy steering councils members

Hi all, It has been well over a year since we put together the governance structure and steering council ( https://docs.scipy.org/doc/numpy-dev/dev/governance/people.html#governance-people). We haven't reviewed the people on the steering council in that time. Based on the criteria for membership I

Re: [Numpy-discussion] F2PY problems with PGI compilers

On Sat, Aug 5, 2017 at 7:24 AM, Jeff Layton wrote: > Good afternoon! > > I'm trying to build a Python module using F2PY on a simple Fortran code > using the PGI 17.4 community compilers. > > I'm using Conda 4.3.21 with Python 2.7.13 and F2PY 2. The command line I'm > using is, > > > f2py --compil

Re: [Numpy-discussion] F2PY problems with PGI compilers

On Mon, Aug 14, 2017 at 7:24 AM, Jeff Layton wrote: > +SciPy list > > > > On Sat, Aug 5, 2017 at 7:24 AM, Jeff Layton wrote: > >> Good afternoon! >> >> I'm trying to build a Python module using F2PY on a simple Fortran code >> using the PGI 17.4 community compilers. >> >> I'm using Conda 4.3.21

Re: [Numpy-discussion] F2PY problems with PGI compilers

On Tue, Aug 15, 2017 at 2:19 AM, Jeff Layton wrote: > On 08/14/2017 03:51 AM, Ralf Gommers wrote: > > > > > >> >> >> I'm definitely at a lose here. I have no idea how to make F2PY work with >> the PGI compilers. I'm beginning to think F2PY is c

Re: [Numpy-discussion] NumPy default citation

On Wed, Sep 6, 2017 at 8:29 AM, Stefan van der Walt wrote: > On Tue, Sep 5, 2017, at 13:25, Charles R Harris wrote: > > > On Tue, Sep 5, 2017 at 12:36 PM, Stefan van der Walt > wrote: > > Shall we add a citation to Travis's "Guide to NumPy (2nd ed.)" on both > > > What is the citation for? > > >

Re: [Numpy-discussion] Dropping support for Accelerate

On Sat, Jul 22, 2017 at 10:50 PM, Ilhan Polat wrote: > A few months ago, I had the innocent intention to wrap LDLt decomposition > routines of LAPACK into SciPy but then I am made aware that the minimum > required version of LAPACK/BLAS was due to Accelerate framework. Since then > I've been foll

[Numpy-discussion] ANN: SciPy 1.0 beta release

Hi all, I'm excited to be able to announce the availability of the first beta release of Scipy 1.0. This is a big release, and a version number that has been 16 years in the making. It contains a few more deprecations and backwards incompatible changes than an average release. Therefore please do

Re: [Numpy-discussion] ANN: SciPy 1.0 beta release

17, 2017 at 10:48 AM Ilhan Polat wrote: > >> Well also thank you Ralf, for going through all those issues one by one >> from all kinds of topics. Must be really painstakingly tedious. >> >> >> On Sun, Sep 17, 2017 at 12:48 PM, Ralf Gommers >> wrote: >>

Re: [Numpy-discussion] ANN: SciPy 1.0 beta release

On Sun, Sep 17, 2017 at 10:48 PM, Ralf Gommers wrote: > Hi all, > > I'm excited to be able to announce the availability of the first beta > release of Scipy 1.0. This is a big release, and a version number that > has been 16 years in the making. It contains a few m

Re: [Numpy-discussion] [SciPy-User] ANN: SciPy 1.0 beta release

On Mon, Sep 18, 2017 at 10:36 PM, Matthew Brett wrote: > Hi, > > On Mon, Sep 18, 2017 at 11:14 AM, Ralf Gommers > wrote: > > > > > > On Mon, Sep 18, 2017 at 10:11 PM, Matthew Brett > > > wrote: > >> > >> Hi, > >> > >&

Re: [Numpy-discussion] Proposal - change to OpenBLAS for Windows wheels

On Tue, Sep 26, 2017 at 6:48 AM, Nathaniel Smith wrote: > Makes sense to me. > > On Sep 25, 2017 05:54, "Matthew Brett" wrote: > >> Hi, >> >> I suggest we switch from ATLAS to OpenBLAS for our Windows wheels: >> >> * OpenBLAS is much faster, at least when Tony Kelman tested it last year >> [1];

[Numpy-discussion] ANN: first SciPy 1.0.0 release candidate

Hi all, I'm excited to be able to announce the availability of the first release candidate of Scipy 1.0. This is a big release, and a version number that has been 16 years in the making. It contains a few more deprecations and backwards incompatible changes than an average release. Therefore pleas

Re: [Numpy-discussion] Sustainability

On Thu, Oct 5, 2017 at 4:03 AM, Benjamin Root wrote: > One thing that concerns me is trying to keep up with demand. Our tools > have become extremely popular, but it is very difficult for maintainers to > keep up with this demand. So, we seem to have a tendency to "tribalize", in > a sense, focus

Re: [Numpy-discussion] [SciPy-Dev] Sustainability

On Fri, Oct 6, 2017 at 8:24 AM, Pauli Virtanen wrote: > to, 2017-10-05 kello 00:08 +0200, Ilhan Polat kirjoitti: > [clip] > > 2. Feature completeness of basic modules. > > I think those judgments can be subjective, but it is true many things > have been organically grown, and this becomes even mo

[Numpy-discussion] ANN: second SciPy 1.0.0 release candidate

Hi all, I'm excited to be able to announce the availability of the second (and hopefully last) release candidate of Scipy 1.0. This is a big release, and a version number that has been 16 years in the making. It contains a few more deprecations and backwards incompatible changes than an average re

Re: [Numpy-discussion] numpy grant update

On Thu, Oct 19, 2017 at 10:02 AM, Charles R Harris < charlesr.har...@gmail.com> wrote: > > > On Wed, Oct 18, 2017 at 11:24 PM, Nathaniel Smith wrote: > >> Hi all, >> >> I wanted to give everyone an update on what's going on with the NumPy >> grant [1]. As you may have noticed, things have been mo

[Numpy-discussion] SciPy 1.0 released!

grown. I stopped being able to participate actively in developing the SciPy library around 2010. Fortunately, at that time, Pauli Virtanen and Ralf Gommers picked up the pace of development supported by dozens of other key contributors such as David Cournapeau, Evgeni Burovski, Josef Perktold, an

Re: [Numpy-discussion] NumPy 1.14 branch.

On Sat, Nov 4, 2017 at 3:56 PM, Charles R Harris wrote: > Hi All, > > I'd like to branch NumPy 1.14 soon. > Sounds good. Before doing so, I'd like to make sure at a minimum that > > 1) Changes in array print formatting are done. > 2) Proposed deprecations have been make. > > If there are other

Re: [Numpy-discussion] Proposal of timeline for dropping Python 2.7 support

On Mon, Nov 6, 2017 at 7:25 AM, Charles R Harris wrote: > Hi All, > > Thought I'd toss this out there. I'm tending towards better sooner than > later in dropping Python 2.7 support as we are starting to run up against > places where we would like to use Python 3 features. That is particularly > t

Re: [Numpy-discussion] Proposal of timeline for dropping Python 2.7 support

On Thu, Nov 9, 2017 at 12:15 PM, Nathaniel Smith wrote: > On Nov 8, 2017 16:51, "Matthew Brett" wrote: > > Hi, > > On Wed, Nov 8, 2017 at 7:08 PM, Julian Taylor > wrote: > > On 06.11.2017 11:10, Ralf Gommers wrote: > >> > >> &

  1   2   3   4   5   6   7   8   >