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
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`
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:
>
> ```
>
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
>
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
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
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.
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.
&
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 (
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 going to
>
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
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!
___
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
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
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
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
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
>
ops 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 like is t
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
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
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
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
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,
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
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
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.
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
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
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
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
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
ual/design comments, please post them on this thread.
Cheers,
Ralf
=
NEP 56 — Array API standard support in NumPy's main namespace
=
:Author: Ralf Gommers
:Author: Mateusz Sokó
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 it's
(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 :
>>
>>
-- 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
(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 pkgconfig
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
:Status: Draft
:Type: Standards Trac
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
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
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
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
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
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
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 <
>
k. 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-api-c
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
is
>> 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 Chuck!
>
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
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
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:
On Fri, Aug 18, 2023 at 10:59 AM Ronald van Elburg <
r.a.j.van.elb...@hetnet.nl> wrote:
> I was trying to get a feel for how often the work around occurs. I found
> three clear examples in Scipy and one unclear case. One case in holoviews.
> Two in numpy. One from soundappraisal's code base.
>
On Wed, Aug 16, 2023 at 5:01 AM Andrew Nelson wrote:
>
> On Wed, 16 Aug 2023 at 10:51, Andrew Nelson wrote:
>
>> There's a scipy issue on this that discusses how to reduce usage,
>> https://github.com/scipy/scipy/issues/19006.
>>
>> Main points:
>>
>> - at the moment CI is run on PR and on
On Tue, Aug 15, 2023 at 4:19 PM Charles R Harris
wrote:
> Hi All,
>
> This is a heads up that we have already exceeded our allotment of free
> time on Cirrus CI. They are giving us a pass this month, but next month
> they will start enforcing the limits. That will impact both our testing and
>
On Mon, Aug 14, 2023 at 1:16 PM Doug Turnbull
wrote:
> Hey all
>
> First time trying to build / test numpy main branch, so I'm probably doing
> something wrong.
>
> I brought down main and everything built on the first try. However I'm
> getting test failures related to meson.
>
> Specifically
Hey all,
We've landed some major changes in `main` this week, so I thought it's a
good idea to keep everyone in the loop.
First the good news: we now have full SIMD support in the Meson builds on
`main`! This was a huge amount of work by Sayed, so I'd like to say thank
you to him for doing all
On Mon, Aug 7, 2023 at 1:40 AM Andrew Nelson wrote:
> The array-api documentation (
> https://data-apis.org/array-api/latest/API_specification/generated/array_api.asarray.html#array_api.asarray)
> for `asarray` has a copy keyword, the numpy version doesn't. Is there a
> plan to add such a
On Mon, Jul 31, 2023 at 6:53 PM Charles R Harris
wrote:
> Hi All,
>
> The 1.26.x maintenance branch has been created. The 1.26.x branch is a
> continuation of the 1.25.x branch and serves to mark the change from our
> distutils based builds to the meson builds needed to support the upcoming
>
Hi all,
This email is about two 2.0 release related topics:
1. Advice/guidance for downstream library authors and end users
2. Strategy for development work around public API changes that will be
breaking backwards compatibility.
I also just created https://github.com/numpy/numpy/issues/24300 as
On Fri, Jul 14, 2023 at 10:59 PM Charles R Harris
wrote:
> Hi All,
>
> We plan to release NumPy 1.26 soon after the release of the Python
> 3.12.0rc1 release, which is currently scheduled for July 31, just a bit
> more than two weeks off. What I'd like to do is
>
Thanks for getting the ball
On Tue, Jul 11, 2023 at 2:38 PM James Webber wrote:
> Hello there! First time posting here and I apologize if this discussion is
> not new. I couldn't find it in a search.
>
> I've been contributing a bit to the sparse project (
> https://github.com/pydata/sparse) and I was working on
On Mon, Jun 26, 2023 at 6:57 AM Kai Striega wrote:
> Hi Stefan,
>
> I'm interested in going that direction, or rather, getting the functions
> out of NumPy. I'm not sure if it's feasible to rip these functions out of
> NumPy itself – or how much work it would require. Last week I spent some
>
On Fri, Jun 2, 2023 at 1:51 PM Ronald van Elburg
wrote:
> Aha, the unnecessary copy mentioned in the
> https://dbs.ifi.uni-heidelberg.de/files/Team/eschubert/publications/SSDBM18-covariance-authorcopy.pdf.
> paper is a copy of the input. Here it is about discarding a valuable output
> (the mean)
On Wed, May 31, 2023 at 4:19 PM Charles R Harris
wrote:
>
>
> On Wed, May 31, 2023 at 8:05 AM Robert Kern wrote:
>
>> I would much, much rather have the special functions in the `np.*`
>> namespace be more accurate than fast on all platforms. These would not
>> have been on my list for general
On Wed, May 31, 2023 at 12:28 PM Chris Sidebottom
wrote:
> Matthew Brett wrote:
> > Hi,
> > On Wed, May 31, 2023 at 8:40 AM Matti Picus matti.pi...@gmail.com wrote:
> > > On 31/5/23 09:33, Jerome Kieffer wrote:
> > > Hi Sebastian,
> > > I had a quick look at the PR and it looks like you
On Tue, May 23, 2023 at 2:26 PM asyropoulos--- via NumPy-Discussion <
numpy-discussion@python.org> wrote:
> Hello,
>
> I am using Python 3.10.0 on OpenIndiana and yesterday I tried to install
> numpy in my system. The command
>
> /opt/gnu/python/bin/python3.10 -m pip install --user numpy
>
>
Hi all,
Stéfan and I wrote a NEP about cleaning up the Python API for the NumPy 2.0
release. It was first presented at the NumPy 2.0 developer meeting last
month, and more review comments came in on
https://github.com/numpy/numpy/pull/23537. It seems about ready to propose
for wider review here
ers".
So you are still using the old version of the library if you did not do
that. This is not entirely trivial to do now; I expect we'll see a PR to
enable the new libraries quite soon.
Cheers,
Ralf
>
> Best,
> Jerry
>
>
> On Thu, Mar 23, 2023 at 3:52 AM Ralf Gommers
> w
Hi all,
As part of this meeting we have reserved a 30 minute slot for lightning
talks. Those can be for topics that are on our tentative roadmap already
(see https://github.com/orgs/numpy/projects/9/views/1), or topics that
you'd like to add to that roadmap and would like to drive and pitch to
On Mon, Mar 20, 2023 at 9:09 PM Ralf Gommers wrote:
>
> So my proposal is to drop all the Docker Hub and Gitpod related code and
> docs. I have already discussed this with Tania Allard, who did most of the
> heavy lifting on the initial creation of the Gitpod machinery (for Sc
On Thu, Mar 23, 2023 at 10:43 AM Clemens Brunner
wrote:
> Thanks Ralf, this sounds great! Just making sure I understand, this means
> that for macOS 13, we have to enable Accelerate by building NumPy from
> source.
Indeed. Either that, or use a packaging system that's more capable in this
On Thu, Mar 23, 2023 at 1:55 AM Clemens Brunner
wrote:
> Hello!
>
> I recently got a new MacBook Pro with an M2 Pro CPU (ARM64). When I ran
> some numerical computations (ICA to be precise), I was surprised how slow
> it was - way slower than e.g. my almost 10 year old Intel Mac. It turns out
>
On Tue, Mar 21, 2023 at 12:20 PM Klaus Zimmermann
wrote:
> Hi,
>
> this sounds all reasonable to me, and as mostly a lurker on this list my
> input shouldn't carry too much weight anyway.
>
> I wanted to point out one thing: Docker does continue to offer free
> access for Open Source projects,
Hi all,
We received a notification from Docker that there Free Team organization no
longer exists, and that we have until April 14 to upgrade to a paid tier.
We only use Docker to support Gitpod. Gitpod builds have been broken in
main for quite a while (see
On Thu, Mar 16, 2023 at 7:57 PM Sergio Callegari
wrote:
> I am trying to use the `clip` method to transform floats to integers with
> clipping. I was expecting to be able to do both the clipping and the type
> conversion at once, passing the `dtype` parameter to `clip`, together with
> a
e as well.
>
> Von meinem iPhone gesendet
>
> Am 10.03.2023 um 19:10 schrieb Stephan Hoyer :
>
>
> +1 for removing this environment variable. It was never intended to stick
> around this long.
>
> On Fri, Mar 10, 2023 at 6:48 AM Ralf Gommers
> wrote:
>
>&
Hi all,
In https://github.com/numpy/numpy/pull/23364 we touched on the
NUMPY_EXPERIMENTAL_ARRAY_FUNCTION environment variable. This was a
temporary feature during the introduction of `__array_function__` (see NEP
18), but we never removed it. I propose we do so now, since it is
cumbersome to have
On Tue, Mar 7, 2023 at 1:02 PM Sebastian Berg
wrote:
> On Tue, 2023-03-07 at 12:17 +0000, Ralf Gommers wrote:
> > On Mon, Mar 6, 2023 at 8:12 AM Sebastian Berg <
> > sebast...@sipsolutions.net>
> > wrote:
> >
> > > On Thu, 2023-03-02 at 15:20
On Mon, Mar 6, 2023 at 8:12 AM Sebastian Berg
wrote:
> On Thu, 2023-03-02 at 15:20 +0000, Ralf Gommers wrote:
> > Hi all,
> >
> > In https://github.com/numpy/numpy/pull/23314 I am deprecating four
> > functions: `product`, `cumproduct`, `alltrue`, `sometrue`. Th
Hi all,
In https://github.com/numpy/numpy/pull/23314 I am deprecating four
functions: `product`, `cumproduct`, `alltrue`, `sometrue`. These are all
aliases (for `prod`, `cumprod`, `all` and `any`), were already not part of
the API docs, and there was an open issue for deprecating them (
On Tue, Feb 14, 2023 at 9:08 PM Stefan van der Walt
wrote:
> On Tue, Feb 14, 2023, at 12:27, Ralf Gommers wrote:
>
> Okay, as long as we keep in mind that it should contain all these
> not-for-main-namespace functions/classes, it seems fine with me. We can
> live with two nam
On Mon, Feb 13, 2023 at 11:33 AM Sebastian Berg
wrote:
> On Sat, 2023-02-11 at 11:24 +0000, Ralf Gommers wrote:
> > On Fri, Feb 10, 2023 at 5:35 PM Nathan
> > wrote:
> >
>
>
> > > >
> > >
> > > Small bikeshed: the name np.type
On Fri, Feb 10, 2023 at 5:35 PM Nathan wrote:
>
>
> On Fri, Feb 10, 2023 at 3:31 AM Sebastian Berg
> wrote:
>
>> Hi all,
>>
>> I was wondering if we should introduce a new `np.types` namespace. The
>> main reason is that we have the DType classes, that most users don't
>> need to worry about.
On Mon, Jan 16, 2023 at 3:28 PM Mark Harfouche
wrote:
> I am trying to create a few different duck arrays that are backed by
> different files.
>
> Is there a standard test suite that we can inspire ourselves from that
> helps us assert:
>
> "Arrays should implement all these different functions
but hopefully not most as one needs to use
>smaller than default precision types to be affected.
>
> <#m_-4971028583323681657_A-thorough-cleanup-of-the-Python-API>A thorough
> cleanup of the Python API
> The NumPy API is quite messy, with many functions an
On Sun, Dec 25, 2022 at 12:20 AM wrote:
> Hello,
>
> I hope this is the right forum on which to post this, but if not please
> let me know.
>
> I'll be starting a PhD program in mathematics in the fall, and I'm looking
> for something to occupy part of my time until then.
>
> I've been
On Wed, Dec 21, 2022 at 12:04 PM Andrew Nelson wrote:
> On Wed, 21 Dec 2022 at 20:40, Matti Picus wrote:
>
>> Maybe we should have a scientific-python wide discussion of what
>> platforms we wish to support, like NEP 29 for python versions. The NEP
>> should include some mechanism for adding
On Mon, Dec 12, 2022 at 4:44 PM Sebastian Berg
wrote:
> On Wed, 2022-12-07 at 14:21 -0700, Aaron Meurer wrote:
> > Hi all.
> >
> > As discussed in today's community meeting, I plan to start working on
> > adding some useful functions to NumPy which are part of the array API
> > standard
On Wed, Dec 7, 2022 at 11:51 PM Ilhan Polat wrote:
>
> On matrix_transpose() :
> Every time this discussion brought up, there was a huge resistance to add
> more methods to array object or new functions (I have been involved in some
> of them on the pro .H side, links you have given and more in
beginner/average user, it will have few users right now, and as long as the
correspondence is mentioned in the docstring this should be discoverable
enough. I'd much prefer no alias, we already have way too many of those and
most of them are only noise at this point.
Cheers,
Ralf
> Thanks,
> Ganesh
Hi all,
I'm excited to be able to share this announcement on behalf of the NumPy
Steering Council. We have created a new program, the NumPy Fellowship
Program, and offered Sayed Adel the very first Developer in Residence role.
Sayed starts his 1 year tenure in that role today, and we are really
On Fri, Nov 25, 2022 at 9:55 PM Serge Guelton
wrote:
> On Fri, Nov 25, 2022 at 08:09:02PM +0100, Sebastian Berg wrote:
> > Thanks for bringing this up again. The Python method exists and it
> > seems like relatively basic functionality.
> >
> > Overall, I am slightly in favor of adding the
On Wed, Nov 30, 2022 at 7:10 PM Marko Pacak wrote:
> Hi Ralf, thx for replying to this.
>
> > I'd prefer to tell users to use `np.asarray()` on their inputs instead.
>
> How would you do that? Through a warning in the test suite? Or document it
> somewhere?
>
The docstring for array_equal
On Wed, Nov 30, 2022 at 10:24 AM Matti Picus wrote:
>
> On 30/11/22 05:47, Stefan van der Walt wrote:
> > On Tue, Nov 29, 2022, at 07:21, i...@markopacak.com wrote:
> >> The debate is whether np.testing.asset_equal should support
> >> collections.Sequence objects.
> > assert list(sequence1) ==
Hi all,
We have to do something about long double support. This is something I
wanted to propose a long time ago already, and moving build systems has
resurfaced the pain yet again.
This is not a full proposal yet, but the start of a discussion and gradual
plan of attack.
The problem
On Fri, Nov 11, 2022 at 2:47 PM Sebastian Berg
wrote:
> Hi all,
>
> I want to add a new exception or two. It is a longer story, that you
> can find at the bottom :).
>
> Lets create a namespace for custom errors! I don't want to propose new
> exceptions that just get dumped in to the main
On Fri, Nov 11, 2022 at 10:07 PM Stefan van der Walt
wrote:
> On Fri, Nov 11, 2022, at 06:03, Evgeni Burovski wrote:
> > before: any thoughts to change it to e.g. tempita templating?
>
> With the "e.g." maybe being jinja2. tempita works well, but hasn't been
> worked on since 2013.
>
It
On Fri, Nov 11, 2022 at 1:52 PM Sebastian Berg
wrote:
> On Fri, 2022-11-11 at 12:27 +0100, Ralf Gommers wrote:
> > Hi all,
> >
> > With distutils now removed from the stdlib in the Python 3.12 release
> > cycle, the clock is ticking a bit for dealing with our
Hi all,
With distutils now removed from the stdlib in the Python 3.12 release
cycle, the clock is ticking a bit for dealing with our build system
situation. With SciPy's move to Meson now basically complete - there are
always loose ends & improvements, but the 1.9 releases have gone well -
it's
On Wed, Nov 2, 2022 at 9:30 AM 腾刘 <27rabbi...@gmail.com> wrote:
> Hi everyone! I 'm here again.
>
> Recently I 'm trying to understand the C code with output-debug method,
> inserting many print statements. I was doing well with it until one day: I
> changed a file called loops_utils.h.src
On Fri, Oct 28, 2022 at 10:57 AM Sebastian Berg
wrote:
> Hi all,
>
> As mentioned earlier, I would like to propose changing the
> representation of scalars in NumPy. Discussion and ideas on changes
> are much appreciated!
>
> The main change is to show scalars as:
>
> * `np.float64(3.0)`
1 - 100 of 641 matches
Mail list logo
