On Sat, Oct 12, 2024 at 6:23 PM Marten van Kerkwijk
wrote:
> Hi Dan, others,
>
> Great news that the sparse array implementation is getting there!
> The continued existence of np.matrix has in large part been because of
> sparse matrices, so in some sense the decision depends also on what
> happe
On Tue, Sep 3, 2024 at 7:53 PM Peter Cock via NumPy-Discussion <
[email protected]> wrote:
> If I recall correctly, people were building against the Numpy 2.0.0
> release candidates in particular. In hindsight keeping those on PyPI might
> have been better. A formal NEP/SPEC seems a good
On Sat, Oct 19, 2024 at 2:18 PM Dan Schult wrote:
> This is quite helpful. Thanks!
>
> Github search:
> I'm not surprised that many github hits are like homework problems. The
> big resistance to removing np.matrix early on (~2008) came from educators
> who wanted a Matrix oriented experience for
Below is the input on this topic from Christian Lorentzen, who for some
reason didn't get through the mailing list approval to post directly:
Hi there
IMHO, numpy should definitely endorse SPEC7, otherwise this SPEC should
be removed or updated.
About SPEC0, please note that according to the tex
Yes, that does look like a conda-forge issue. I think it's this one:
https://github.com/conda-forge/python-feedstock/issues/738
On Tue, Nov 26, 2024 at 6:06 PM george trojan via NumPy-Discussion <
[email protected]> wrote:
> My apologies if this is a wrong venue. Is this a conda-forge p
On Sun, Feb 9, 2025 at 6:34 PM Carlos Martin
wrote:
> The following functions accept a diagonal offset argument:
> - https://numpy.org/doc/stable/reference/generated/numpy.diag.html
> - https://numpy.org/doc/stable/reference/generated/numpy.diagflat.html
> - https://numpy.org/doc/stable/reference
On Tue, Feb 11, 2025 at 10:55 AM Lucas Colley via NumPy-Discussion <
[email protected]> wrote:
> Ralf Gommers wrote:
> > This sounds quite reasonable to me. The `k=0` keyword is quite badly
> named,
> > which is my one concern. Especially when tacking it on at the end of a
> > signature
On Tue, Dec 17, 2024 at 8:18 AM Matti Picus via NumPy-Discussion <
[email protected]> wrote:
> We are starting to discuss moving up from manylinux2104_manylinux_2_17
> for the next NumPy release in June 2025. It seems, looking at
>
> https://github.com/mayeut/pep600_compliance?tab=readme
Hi all,
We just received two $1,000 donations on Open Collective (
https://opencollective.com/numpy), from MMIC and Joseph Jacks. Those are
the largest individual/anonymous donations we've received over the last
years I think, at least since the time we have a completely public record
of our finan
On Sat, Apr 5, 2025 at 2:41 PM Seungwoo (Simon) Kim via NumPy-Discussion <
[email protected]> wrote:
> Hi,
>
> It would be useful to have numpy support for noncentral student's
> t-distribution. Numpy already supports standard t, and it should be a
> straightforward transformation:
> - (
Hi all,
On behalf of the whole steering council, I'd like to welcome Marten van
Kerkwijk and Nathan Goldbaum as new steering council members. We're very
glad that Marten has returned to active NumPy development and is returning
to the council, and that Nathan is joining the council after 2.5 years
On Sun, Apr 27, 2025 at 7:31 AM Carlos Martin
wrote:
> Saturating arithmetic (https://en.wikipedia.org/wiki/Saturation_arithmetic)
> is important in digital signal processing and other areas.
>
> Feature request: Add saturating arithmetic functions for the following
> basic operations:
>
> - addi
On Tue, Apr 29, 2025 at 11:24 AM PIERRE AUGIER <
[email protected]> wrote:
> Dear Numpy community members and Numpy developers,
>
> This email is to get the points of view of the Numpy community members and
> developers about a subject that I find very important. I'm going to
>
On Wed, Apr 30, 2025 at 6:08 AM Bill Ross wrote:
> Why run someone else's code? Can't they monitor through git?
>
> [reads more] .. why?
>
Agreed, this request is badly thought out. The amount of research requests
we're receiving privately is going up in my experience. In this case it
seems to b
On Sat, Apr 12, 2025 at 12:13 PM Mateusz Sokol wrote:
> Hi all!
>
> The Array API standard states that `T` property should only be applied to
> 2-dimensional arrays, in all other cases it should raise an error:
>
> https://data-apis.org/array-api/latest/API_specification/generated/array_api.array
On Sat, Mar 1, 2025 at 9:17 PM Carlos Martin
wrote:
> Add a function called `spectral_radius` that computes the
> [spectral_radius](https://en.wikipedia.org/wiki/Spectral_radius) of a
> given matrix.
>
> A naive way to do this is `np.max(np.abs(np.linalg.eigvals(a)))`, but
> there are more effici
On Wed, May 7, 2025 at 7:44 PM Charles R Harris via NumPy-Discussion <
[email protected]> wrote:
> Hi All,
>
> Just thought I would raise the topic of PyPy status in NumPy 2.3. PyPy for
> Python 3.11 currently has a bug which has hung around for a while,
>
Is it relevant? There are of c
On Fri, Jun 13, 2025 at 11:13 AM Andrew Nelson via NumPy-Discussion <
[email protected]> wrote:
>
> On Fri, 13 Jun 2025 at 16:43, Ralf Gommers via NumPy-Discussion <
> [email protected]> wrote:
>
>>
>> For 2FA and repository/PyPI access, w
On Fri, Jun 13, 2025 at 11:07 AM Jerome Kieffer
wrote:
> Hi Matti,
>
> Sorry for the delay ...
>
> In one of my project I am working on, we use based Avoton server
> (Intel C2350) for CI/CD which can be rented today (2025) for less than
> 5€/month
> at online.net (a french provider). Switching to
Hi all,
Now that PyPI has organizations and they came out of beta and the
application queue cleared, I applied for a NumPy organization and that just
came through (https://pypi.org/org/numpy/). We can start moving projects
under that now, so it'll look more like https://pypi.org/org/scipy/. For
th
Hi all,
In https://github.com/numpy/numpy/issues/29178 I posted a proposal for
steps to take to improve supply chain security. The most important proposed
change is:
- Move building release artifacts that get uploaded to PyPI and anaconda.org
to a new repository.
Other proposed changes:
- Furth
On Sat, Jun 14, 2025 at 6:23 PM Jerome Kieffer
wrote:
> Hi Ralph,
>
> There is no problem here except "any hardware more than 10yo* is
> deprecated and we can discontinue its support" which is something Intel
> would love but not me (nor anybody who realized we are living in a
> finite world).
>
On Fri, Jun 13, 2025 at 4:47 PM Ralf Gommers wrote:
>
>
> On Fri, Jun 13, 2025 at 11:13 AM Andrew Nelson via NumPy-Discussion <
> [email protected]> wrote:
>
>>
>> On Fri, 13 Jun 2025 at 16:43, Ralf Gommers via NumPy-Discussion <
>> numpy-di
On Sat, May 17, 2025 at 3:00 PM wrote:
> Hi Sayed,
>
> I'm a bit confused: does your suggested change mean that prre-2009
> processors won't work at all, or that no use will be made of the (little)
> acceleration that they provided? The latter seems fine, but not working at
> all seems rather ba
On Sun, May 18, 2025 at 9:40 AM Jerome Kieffer
wrote:
> Hi,
>
> First I would like to highlight that "X86_V2" is very specific to the
> implementation in numpy, basically this implies the support of all 128
> bits SIMD extensions, i.e. SSE1,2,3&4, but does apparenty not requires
> any 256bit SIMD
On Tue, Sep 9, 2025 at 8:24 PM Charles R Harris via NumPy-Discussion <
[email protected]> wrote:
> Hi All,
>
> On behalf of the NumPy team, I'm pleased to announce the release of NumPy
> 2.3.3. The NumPy 2.3.3 release is a patch release split between a number of
> maintenance updates and
r.
Cheers,
Ralf
> Best,
> Hameer
>
> Le 14.09.2025 à 22:49, Ralf Gommers via NumPy-Discussion <
> [email protected]> a écrit :
>
>
>
>
> On Wed, Sep 10, 2025 at 3:28 PM Nathan via NumPy-Discussion <
> [email protected]> wrote:
>
&
Hi all,
GitHub Actions has deprecated the macos-13 image [1], which was the last
image to support Intel x86-64 runners. As a result, we won't be able to use
our current wheel build setup.
A quick sampling of what others are doing with their support policies:
CPython dropped it to Tier 2 [2], Anac
On Wed, Sep 10, 2025 at 3:28 PM Nathan via NumPy-Discussion <
[email protected]> wrote:
>
>
> On Wed, Sep 10, 2025 at 7:02 AM Ralf Gommers via NumPy-Discussion <
> [email protected]> wrote:
>
>>
>>
>> On Wed, Sep 10, 2025 at
On Wed, Sep 10, 2025 at 2:01 PM Charles R Harris via NumPy-Discussion <
[email protected]> wrote:
>
>
> On Wed, Sep 10, 2025 at 2:45 AM matti picus via NumPy-Discussion <
> [email protected]> wrote:
>
>> On Tue, Sep 9, 2025 at 10:11 PM
On Wed, Sep 10, 2025 at 2:06 PM Hugo van Kemenade wrote:
> I believe Azure Pipelines and GitHub Actions essentially use the same
> infra, and Azure Pipelines is also dropping macOS Intel x86-64:
>
I don't think that is correct. They use the same *runner images* and the
macos-13 image is indeed d
On Thu, Oct 30, 2025 at 3:53 AM Inessa Pawson via NumPy-Discussion <
[email protected]> wrote:
> Hi, all!
> In 2022, after much research and discussion with the NumPy maintainers and
> active contributors, we replaced Google Analytics with Plausible, an open
> source lightweight alternat
On Wed, Oct 22, 2025 at 5:19 AM matti picus via NumPy-Discussion <
[email protected]> wrote:
> On Wed, Oct 22, 2025 at 6:04 AM Carlos Martin
> wrote:
>
>> NumPy has the following nan-ignoring functions:
>>
>> ...
>> Suggestion: Replace these functions with an ignore_nan flag to their
>>
On Sat, Nov 8, 2025 at 2:25 PM sebastian wrote:
> Hi all,
>
> A heads up, that I have a PR to introduce `__numpy_dtype__` as a
> protocol.
> Right now when NumPy coerces to a dtype (e.g. via `np.dtype()` or
> `dtype=...`)
> it checks for a `.dtype` attribute on the object and if that is a NumPy
>
On Sat, Nov 8, 2025 at 12:15 PM sebastian
wrote:
> On 2025-11-07 02:58, Stefan van der Walt via NumPy-Discussion wrote:
> > On Mon, Nov 3, 2025, at 12:29, Nathan via NumPy-Discussion wrote:
> >
> >> Ralf rightly pointed out
> >>
> > (https://github.com/numpy/numpy/pull/30098#pullrequestreview-340
On Wed, Oct 22, 2025 at 10:48 PM Marten van Kerkwijk via NumPy-Discussion <
[email protected]> wrote:
> Hi Carlos,
>
> Indeed, the implementation for making NaN mean "omit" for some functions
> is not too difficult now. Your example actually leads to the opposite
> conclusion about ease
On Thu, Oct 23, 2025 at 2:18 PM Marten van Kerkwijk via NumPy-Discussion <
[email protected]> wrote:
> Hi Ralf,
>
> > So I think the relevant choices are:
> > 1. Change nothing to the current status quo (and possibly direct end
> users who need more than
> > what we offer now to `marray`
On Thu, Oct 2, 2025 at 6:27 PM Oscar Benjamin
wrote:
> On Tue, 9 Sept 2025 at 20:15, Ralf Gommers via NumPy-Discussion
> wrote:
> >
> > GitHub Actions has deprecated the macos-13 image [1], which was the last
> image to support Intel x86-64 runners. As a result, we won&#
Hi all,
First off, this is a very belated announcement on behalf of the NumPy
Steering Council of something that everyone actively working on NumPy is
already aware of. The delay in this announcement is totally my fault - my
apologies. With that out of the way, on to the announcement!
The NumPy t
On Tue, Nov 11, 2025 at 2:48 PM Veit Heller wrote:
> As another point of consideration, I also contributed changes to
> PyWavelets, Pandas, and scikit-image to replace all occurrences of `np.fix`
> with `np.trunc`, so that might also help further things along.
>
Thanks a lot for those contributi
40 matches
Mail list logo
