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 specializin
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 roll
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 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
> Pyt
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 keyword
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 th
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 th
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
> ou
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 Merge
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.
>
Th
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 <
numpy-discussion@python.org> 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 <
numpy-discussion@python.org> 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 <
numpy-discussion@python.org> 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 th
On Tue, Dec 17, 2024 at 8:18 AM Matti Picus via NumPy-Discussion <
numpy-discussion@python.org> 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 <
numpy-discussion@python.org> 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 <
pierre.aug...@univ-grenoble-alpes.fr> 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 <
numpy-discussion@python.org> 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 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 Fri, Jun 13, 2025 at 11:13 AM Andrew Nelson via NumPy-Discussion <
numpy-discussion@python.org> wrote:
>
> On Fri, 13 Jun 2025 at 16:43, Ralf Gommers via NumPy-Discussion <
> numpy-discussion@python.org> 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).
>
701 - 734 of 734 matches
Mail list logo
