[Numpy-discussion] Re: Proposal to Extend NumPy Broadcasting for (D₁, D₂, ..., N, M) → (D₁, D₂, ..., K, M) When K is a Multiple of N (K % N == 0)

2025-03-25 Thread Benjamin Root via NumPy-Discussion
, Mar 25, 2025 at 9:29 AM Shasang Thummar via NumPy-Discussion < numpy-discussion@python.org> wrote: > Dear NumPy Developers, > > > I hope you are doing well. I am writing to propose an enhancement to NumPy’s > broadcasting mechanism that could make the library even more p

[Numpy-discussion] Proposal to Extend NumPy Broadcasting for (D₁, D₂, ..., N, M) → (D₁, D₂, ..., K, M) When K is a Multiple of N (K % N == 0)

2025-03-25 Thread Shasang Thummar via NumPy-Discussion
Dear NumPy Developers, I hope you are doing well. I am writing to propose an enhancement to NumPy’s broadcasting mechanism that could make the library even more powerful, intuitive, and flexible while maintaining its memory efficiency. ## **Current Broadcasting Rule and Its Limitation** As per N

[Numpy-discussion] Re: Proposal to Extend NumPy Broadcasting for (D₁, D₂, ..., N, M) → (D₁, D₂, ..., K, M) When K is a Multiple of N (K % N == 0)

2025-03-25 Thread Kevin Sheppard via NumPy-Discussion
to broadcast to (1,9), you could want [[1,1,1,2,2,2,3,3,3]] or [[1,2,3,1,2,3,1,2,3]] This ambiguity doesn't arise with broadcasting from 1->N. Probably better to allow users to manually tile in this case. Kevin On Tue, Mar 25, 2025 at 1:31 PM Shasang Thummar via NumPy-Discussion < nu

[Numpy-discussion] Re: Moving the meetings schedule to one hour earlier

2025-03-27 Thread Inessa Pawson via NumPy-Discussion
Meeting one hour earlier will work better for me as well. On Wed, Mar 26, 2025 at 10:18 PM Charles R Harris via NumPy-Discussion < numpy-discussion@python.org> wrote: > > > On Wed, Mar 26, 2025 at 1:18 PM Sebastian Berg > wrote: > >> Hi all, >> >> it'

[Numpy-discussion] next NumPy Optimization Team meeting - Monday, April 14th, 2025 at 5 pm UTC

2025-04-10 Thread Inessa Pawson via NumPy-Discussion
Hi, all! The next NumPy Optimization Team meeting will be held on Monday, April 14th at 17:00 UTC. Join us via Zoom: https://numfocus-org.zoom.us/j/81261288210?pwd=iwV99tGSjR61RTGEERKM4QKxe46g1n.1 Everyone is welcome and encouraged to attend. To add to the meeting agenda the topics you’d like to di

[Numpy-discussion] Re: Moving the meetings schedule to one hour earlier

2025-03-30 Thread Inessa Pawson via NumPy-Discussion
:18 PM Charles R Harris via NumPy-Discussion < > numpy-discussion@python.org> wrote: > >> >> >> On Wed, Mar 26, 2025 at 1:18 PM Sebastian Berg < >> sebast...@sipsolutions.net> wrote: >> >>> Hi all, >>> >>> it's that t

[Numpy-discussion] next NumPy community meeting - Wednesday, March 12th, 2025 at 6 pm UTC

2025-03-15 Thread Inessa Pawson via NumPy-Discussion
The next NumPy community meeting will be held this Wednesday, March 12th at 18:00 UTC. Join us via Zoom: https://numfocus-org.zoom.us/j/83278611437?pwd=ekhoLzlHRjdWc0NOY2FQM0NPemdkZz09 Everyone is welcome and encouraged to attend. To add to the meeting agenda the topics you’d like to discuss, follo

[Numpy-discussion] next NumPy community meeting - Wednesday, April 23rd, 2025 at 5 pm UTC

2025-04-20 Thread Inessa Pawson via NumPy-Discussion
The next NumPy community meeting will be held this Wednesday, April 23rd at 17:00 (5 pm) UTC. Join us via Zoom: https://numfocus-org.zoom.us/j/83278611437?pwd=ekhoLzlHRjdWc0NOY2FQM0NPemdkZz09 Everyone is welcome and encouraged to attend. To add to the meeting agenda the topics you’d like to discuss

[Numpy-discussion] NumPy Steering Council membership update

2025-04-20 Thread Ralf Gommers via NumPy-Discussion
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

[Numpy-discussion] Re: ENH: Add saturating arithmetic functions

2025-04-28 Thread Ralf Gommers via NumPy-Discussion
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

[Numpy-discussion] Re: Better compatibility of the Python scientific/data stack with fast Python interpreters

2025-04-29 Thread Ralf Gommers via NumPy-Discussion
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 >

[Numpy-discussion] Re: Fwd: Research Opportunity: Can we monitor your projects?

2025-04-29 Thread Joren Hammudoglu via NumPy-Discussion
Where can I find the source code of that app? I wasn't able to find it on the github organization or on the website. ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https:

[Numpy-discussion] next NumPy triage meeting - Wednesday, April 30th, 2025 at 5 pm UTC

2025-04-29 Thread Inessa Pawson via NumPy-Discussion
The next NumPy triage meeting will be held TOMORROW, April 30th at 17:00 (5 pm) UTC. This is a meeting where we synchronously triage prioritized PRs and issues. Everyone is welcome to attend and contribute to a conversation. Join us via Zoom: https://numfocus-org.zoom.us/j/82096749952?pwd=MW9oUmtKQ

[Numpy-discussion] Re: Fwd: Research Opportunity: Can we monitor your projects?

2025-04-29 Thread Andrew Nelson via NumPy-Discussion
On Wed, Apr 30, 2025, 08:41 Charles R Harris via NumPy-Discussion < numpy-discussion@python.org> wrote: > Just thought I'd pass this along for discussion. > > Chuck > > -- Forwarded message - > From: > Date: Tue, Apr 29, 2025 at 4:09 PM > Su

[Numpy-discussion] Re: Fwd: Research Opportunity: Can we monitor your projects?

2025-04-29 Thread Ralf Gommers via NumPy-Discussion
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

[Numpy-discussion] next NumPy triage meeting - Wednesday, April 16th, 2025 at 5 pm UTC

2025-04-12 Thread Inessa Pawson via NumPy-Discussion
The next NumPy triage meeting will be held this Wednesday, April 16th at 17:00 (5 pm) UTC. This is a meeting where we synchronously triage prioritized PRs and issues. Everyone is welcome to attend and contribute to a conversation. Join us via Zoom: https://numfocus-org.zoom.us/j/82096749952?pwd=MW9

[Numpy-discussion] Re: Making `T` property Array API compatible

2025-04-12 Thread Lucas Colley via NumPy-Discussion
> The new discrepancy between `arr.T` and `arr.transpose()` is justified, as > `T` is defined by the Array API, where `transpose` isn't and should retain > the existing behavior. The other side of the coin here is that this change would fix the discrepancy between `arr.T` and the functions `np.ma

[Numpy-discussion] Re: Making `T` property Array API compatible

2025-04-12 Thread Ralf Gommers via NumPy-Discussion
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

[Numpy-discussion] Re: Making `T` property Array API compatible

2025-04-14 Thread Lucas Colley via NumPy-Discussion
If NumPy were to make a move on the deprecation, then I think it would be reasonable to change the standard from > If the array instance is not two-dimensional, an error should be raised. to “if the array instance is not two-dimensional, behaviour should match `.mT`, or an error should be raise

[Numpy-discussion] Re: [hpy-dev] Re: [pypy-dev] Re: Better compatibility of the Python scientific/data stack with fast Python interpreters

2025-05-05 Thread PIERRE AUGIER via NumPy-Discussion
Thanks Matti for this interesting and sad piece of news. I also reply on numpy-discussion@python.org since your message was not post on this list and take the opportunity to signal another important post about his subject on discuss.python.org by Stepan Sindelar: https://discuss.python.org/t/c-

[Numpy-discussion] Add Sampling with Dynamic weights with replacement to np.random.choice

2025-05-02 Thread Shourya Jain via NumPy-Discussion
Feature request : Add replacement based sampling method with weight decay for choosing samples from a list/array I would like to add it with an algorithm as follows : for _ in range(target_size): idx = np.random.choice(a, 1, p=p) # Get a sample samples.append(a[idx]) # Append sam

[Numpy-discussion] Re: Add Sampling with Dynamic weights with replacement to np.random.choice

2025-05-02 Thread Robert Kern via NumPy-Discussion
On Fri, May 2, 2025 at 9:55 AM Shourya Jain via NumPy-Discussion < numpy-discussion@python.org> wrote: > Feature request : Add replacement based sampling method with weight decay > for choosing samples from a list/array > > I would like to add it with an algorithm as follows

[Numpy-discussion] Re: next Documentation team meeting

2025-05-04 Thread Mukulika Pahari via NumPy-Discussion
Hi all, Our next Documentation Team meeting will happen on *Monday, May 5* at *7PM UTC*. All are welcome - you don't need to already be a contributor to join. If you have questions or are curious about what we're doing, we'll be happy to meet you! If you wish to join on Zoom, use this (updat

[Numpy-discussion] Re: ENH: Add saturating arithmetic functions

2025-04-28 Thread Neal Becker via NumPy-Discussion
On Mon, Apr 28, 2025 at 4:52 AM Ralf Gommers via NumPy-Discussion < numpy-discussion@python.org> wrote: > > > On Sun, Apr 27, 2025 at 7:31 AM Carlos Martin > wrote: > >> Saturating arithmetic ( >> https://en.wikipedia.org/wiki/Saturation_arithmetic) is importan

[Numpy-discussion] Fwd: [pypy-dev] Re: Better compatibility of the Python scientific/data stack with fast Python interpreters

2025-05-02 Thread matti picus via NumPy-Discussion
-- Forwarded message - From: matti picus Date: Fri, May 2, 2025 at 11:05 AM Subject: Re: [pypy-dev] Re: [Numpy-discussion] Better compatibility of the Python scientific/data stack with fast Python interpreters To: PyPy Developer Mailing List , Ralf Gommers , hpy-dev On Wed, Apr

[Numpy-discussion] next NumPy Optimization Team meeting - Monday, May 5th, 2025 at 5 pm UTC

2025-05-02 Thread Inessa Pawson via NumPy-Discussion
Hi, all! The next NumPy Optimization Team meeting will be held on Monday, May 5th at 17:00 UTC. Join us via Zoom: https://numfocus-org.zoom.us/j/81261288210?pwd=iwV99tGSjR61RTGEERKM4QKxe46g1n.1 Everyone is welcome and encouraged to attend. To add to the meeting agenda the topics you’d like to discu

[Numpy-discussion] next NumPy community meeting - Wednesday, May 7th, 2025 at 5 pm UTC

2025-05-03 Thread Inessa Pawson via NumPy-Discussion
The next NumPy community meeting will be held this Wednesday, May 7th at 17:00 (5 pm) UTC. Join us via Zoom: https://numfocus-org.zoom.us/j/83278611437?pwd=ekhoLzlHRjdWc0NOY2FQM0NPemdkZz09 Everyone is welcome and encouraged to attend. To add to the meeting agenda the topics you’d like to discuss, f

[Numpy-discussion] Re: Better compatibility of the Python scientific/data stack with fast Python interpreters

2025-05-07 Thread PIERRE AUGIER via NumPy-Discussion
- Mail original - > De: "Stefan Krah" > À: "numpy-discussion" > Envoyé: Mercredi 7 Mai 2025 13:47:19 > Objet: [Numpy-discussion] Re: Better compatibility of the Python > scientific/data stack with fast Python interpreters > On Wed, Apr 30, 2025 at 02:08:36PM +0200, PIERRE AUGIER wrote:

[Numpy-discussion] Re: Format of arrays to facilitate analysis

2025-02-18 Thread Robert Kern via NumPy-Discussion
On Tue, Feb 18, 2025 at 11:06 AM Dan Patterson wrote: > I tend to work with Nx2 arrays representing coordinate geometry. > I have examined a number of packages and there is no guidelines as to why > a certain arrangement is preferred over the other. > For example: a rectangle, coordinates ordere

[Numpy-discussion] Re: Format of arrays to facilitate analysis

2025-02-18 Thread Robert Kern via NumPy-Discussion
On Tue, Feb 18, 2025 at 3:00 PM Dan Patterson wrote: > So from a purely numpy perspective, there is no advantage if one of > aforementioned coordinate arrangements is used (eg Nx2, ravelled, 2xN). No, not from numpy's side. Some things you want to do will be easier/prettier in one of the arrang

[Numpy-discussion] next NumPy triage meeting - Wednesday, March 5th, 2025 at 6 pm UTC

2025-03-02 Thread Inessa Pawson via NumPy-Discussion
The next NumPy triage meeting will be held this Wednesday, March 5th at 18:00 UTC. This is a meeting where we synchronously triage prioritized PRs and issues. Everyone is welcome to attend and contribute to a conversation. Join us via Zoom: https://numfocus-org.zoom.us/j/82096749952?pwd=MW9oUmtKQ1c

[Numpy-discussion] Re: Add a spectral_radius function

2025-03-02 Thread Ralf Gommers via NumPy-Discussion
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

[Numpy-discussion] Re: Add a bit_width function

2025-03-06 Thread Oscar Benjamin via NumPy-Discussion
On Thu, 6 Mar 2025 at 18:12, Carlos Martin wrote: > > Feature request: Add a `bit_width` function to NumPy In Python this is called bit_length: >>> (7).bit_length() 3 ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe sen

[Numpy-discussion] Re: next Documentation team meeting

2025-03-09 Thread Mukulika Pahari via NumPy-Discussion
Hi all, Our next Documentation Team meeting will happen on *Monday, March 10* at *7PM UTC*. All are welcome - you don't need to already be a contributor to join. If you have questions or are curious about what we're doing, we'll be happy to meet you! If you wish to join on Zoom, use this (up

[Numpy-discussion] next NumPy Optimization Team meeting - Monday, March 3rd, 2025 at 5 pm UTC

2025-02-28 Thread Inessa Pawson via NumPy-Discussion
Hi, all! The next NumPy Optimization Team meeting will be held on Monday, March 3rd at 17:00 UTC. Join us via Zoom: https://numfocus-org.zoom.us/j/81261288210?pwd=iwV99tGSjR61RTGEERKM4QKxe46g1n.1 Everyone is welcome and encouraged to attend. To add to the meeting agenda the topics you’d like to dis

[Numpy-discussion] Re: Beginners

2025-03-11 Thread matti picus via NumPy-Discussion
On Tue, Mar 11, 2025 at 8:00 PM Monkeysigh via NumPy-Discussion wrote: > > Do you know if beginners are invited to attend? If you mean the community/triage/documentation/optimization team meetings: they are all open for anyone to drop in. Of course the meetings have their own caden

[Numpy-discussion] Automatic binning for np.histogram

2025-03-05 Thread Pieter Eendebak via NumPy-Discussion
Hi everyone, For certain input arrays with small variation the method np.histogram with automatic binning can select an enormous amount of bins and return with an out-of-memory error. A minimal example: import numpy as np e = 1 + 1e-12 Z = [0,1,1,1,1,1,e,e,e,e,e,e, 2] np.histogram(Z, bins="aut

[Numpy-discussion] ENH: Initilize Print Options from Environment Variables

2025-03-11 Thread Daniel Bershatsky via NumPy-Discussion
Dear NumPy Community, I would like to propose an enhancement to NumPy's print options that allows them to be initialized from environment variables. This would provide a more convenient way to configure array formatting without modifying source code. Background Currently, NumPy print options are

[Numpy-discussion] Re: Functions for secant, cosecant, and cotangent

2025-02-12 Thread Robert Kern via NumPy-Discussion
On Wed, Feb 12, 2025 at 5:12 PM Jayanth Tumuluri via NumPy-Discussion < numpy-discussion@python.org> wrote: > Hello, > > I noticed that current/past installations of Numpy do not have functions > for secant, cosecant, and cotangent. Sometimes, there's a reason to use

[Numpy-discussion] Re: next Documentation team meeting

2025-02-22 Thread Mukulika Pahari via NumPy-Discussion
Hi all, Our next Documentation Team meeting will happen on *Monday, February 24* at *7PM UTC*. All are welcome - you don't need to already be a contributor to join. If you have questions or are curious about what we're doing, we'll be happy to meet you! If you wish to join on Zoom, use this

[Numpy-discussion] next NumPy community meeting - Wednesday, February 26th, 2025 at 6 pm UTC

2025-02-23 Thread Inessa Pawson via NumPy-Discussion
The next NumPy community meeting will be held this Wednesday, February 26th at 18:00 UTC. Join us via Zoom: https://numfocus-org.zoom.us/j/83278611437?pwd=ekhoLzlHRjdWc0NOY2FQM0NPemdkZz09 Everyone is welcome and encouraged to attend. To add to the meeting agenda the topics you’d like to discuss, fo

[Numpy-discussion] Usage of Datetime DType in NumPy 2.0 C-API

2025-02-24 Thread Lee Johnston via NumPy-Discussion
We have a C-extension module that works with Datetime DType objects through the C-API. The existing code works fine for NumPy 1x, but not 2x. The NumPy 2.0 migration documentation does not addres

[Numpy-discussion] next NumPy New Contributors' Hour - April 3rd, 2025 at 10 pm UTC

2025-03-31 Thread Inessa Pawson via NumPy-Discussion
Our next New Contributors' Hour will be held this Thursday, April 3rd at 10 pm UTC. Stop by to ask questions, share your progress, or just to say hi. To add to the meeting agenda the topics you’d like to discuss, follow the link: https://hackmd.io/3f3otyyuTte3FU9y3QzsLg?both Join the meeting via Zo

[Numpy-discussion] array.T.max() vs array.max(axis=0) performance difference

2025-04-04 Thread George Tsiamasiotis via NumPy-Discussion
Hello NumPy community! I was writing a function that calculates the bounding box of a polygon (the smallest rectangle that fully contains the polygon, and who's sides are parallel to the x and y axes). The input is a (N,2) array containing the vertices of the polygon, and the output is a 4-tuple c

[Numpy-discussion] Re: array.T.max() vs array.max(axis=0) performance difference

2025-03-22 Thread George Tsiamasiotis via NumPy-Discussion
Very interesting! Thanks for the quick response! ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member

[Numpy-discussion] Re: next Documentation team meeting

2025-03-23 Thread Mukulika Pahari via NumPy-Discussion
Hi all, Our next Documentation Team meeting will happen on *Monday, March 24* at *7PM UTC*. All are welcome - you don't need to already be a contributor to join. If you have questions or are curious about what we're doing, we'll be happy to meet you! If you wish to join on Zoom, use this (up

[Numpy-discussion] 17ᵗʰ Advanced Scientific Programming in Python in Plovdiv, Bulgaria, 21–28 September, 2025

2025-03-24 Thread Tiziano Zito via NumPy-Discussion
ASPP2025: 17ᵗʰ Advanced Scientific Programming in Python Summer School == https://aspp.school Scientists spend more and more time writing, maintaining, and debugging software. While techniques for doing this efficiently have ev

[Numpy-discussion] Re: Dropping PyPy in NumPy 2.3

2025-05-07 Thread Ralf Gommers via NumPy-Discussion
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 r

[Numpy-discussion] Translations project - Crowdin migration

2025-05-12 Thread Melissa Mendonça via NumPy-Discussion
Hi all, We recently moved the numpy.org translations project on crowdin to the Scientific Python crowdin instance, so it benefits from the automations and workflows we have recently developed there for multiple others projects such as SciPy, pandas, xarray, zarr and networkx. To prevent folks fro

[Numpy-discussion] next NumPy triage meeting - Wednesday, May 14th, 2025 at 5 pm UTC

2025-05-11 Thread Inessa Pawson via NumPy-Discussion
The next NumPy triage meeting will be held this Wednesday, May 14th at 17:00 (5 pm) UTC. This is a meeting where we synchronously triage prioritized PRs and issues. Everyone is welcome to attend and contribute to a conversation. Join us via Zoom: https://numfocus-org.zoom.us/j/82096749952?pwd=MW9oU

[Numpy-discussion] Re: Bumping CPU baseline to x86-64-v2

2025-05-17 Thread Ralf Gommers via NumPy-Discussion
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

[Numpy-discussion] ANN: PyData/Sparse 0.17.0 released

2025-05-20 Thread Hameer Abbasi via NumPy-Discussion
Hello all, PyData/Sparse > 0.17.0 is now available on GitHub , pypi and conda-forge. PyData/Sparse provides sparse multi-dimensional arrays for t

[Numpy-discussion] Re: Bumping CPU baseline to x86-64-v2

2025-05-18 Thread matti picus via NumPy-Discussion
On Sun, May 18, 2025 at 10:39 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 SI

[Numpy-discussion] Re: Bumping CPU baseline to x86-64-v2

2025-05-18 Thread Ralf Gommers via NumPy-Discussion
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

[Numpy-discussion] next NumPy community meeting - Wednesday, May 21st, 2025 at 5 pm UTC

2025-05-19 Thread Inessa Pawson via NumPy-Discussion
The next NumPy community meeting will be held this Wednesday, May 21st at 17:00 (5 pm) UTC. Join us via Zoom: https://numfocus-org.zoom.us/j/83278611437?pwd=ekhoLzlHRjdWc0NOY2FQM0NPemdkZz09 Everyone is welcome and encouraged to attend. To add to the meeting agenda the topics you’d like to discuss,

[Numpy-discussion] next NumPy triage meeting - Wednesday, May 28th, 2025 at 5 pm UTC

2025-05-24 Thread Inessa Pawson via NumPy-Discussion
The next NumPy triage meeting will be held this Wednesday, May 28th at 17:00 (5 pm) UTC. This is a meeting where we synchronously triage prioritized PRs and issues. Everyone is welcome to attend and contribute to a conversation. Join us via Zoom: https://numfocus-org.zoom.us/j/82096749952?pwd=MW9oU

[Numpy-discussion] Re: Better compatibility of the Python scientific/data stack with fast Python interpreters

2025-05-15 Thread PIERRE AUGIER via NumPy-Discussion
at 03:52:33PM +0200, PIERRE AUGIER via NumPy-Discussion > wrote: >> > "If the goal is to run psycopg3 fast in PyPy, there are at least three >> > paths: >> > >> >use a cffi backend: this is likely to be the fastest one >> >(in case psycopg

[Numpy-discussion] ANN: Python-Blosc2 3.3.4 released

2025-05-22 Thread Francesc Alted via NumPy-Discussion
Hi, This is a bugfix release, with some minor optimizations. We further improved the correct chaining of *string* lazy expressions (to allow operands with more diverse data types). In addition, both indexing and where expressions are now supported within *string* lazy expressions. Finally, casting

[Numpy-discussion] next NumPy Optimization Team meeting - Monday, May 26th, 2025 at 5 pm UTC

2025-05-23 Thread Inessa Pawson via NumPy-Discussion
Hi, all! The next NumPy Optimization Team meeting will be held on Monday, May 26th at 17:00 UTC. Join us via Zoom: https://numfocus-org.zoom.us/j/81261288210?pwd=iwV99tGSjR61RTGEERKM4QKxe46g1n.1 Everyone is welcome and encouraged to attend. To add to the meeting agenda the topics you’d like to disc

[Numpy-discussion] next NumPy community meeting - Wednesday, June 4th, 2025 at 5 pm UTC

2025-06-01 Thread Inessa Pawson via NumPy-Discussion
The next NumPy community meeting will be held this Wednesday, June 4th at 17:00 (5 pm) UTC. Join us via Zoom: https://numfocus-org.zoom.us/j/83278611437?pwd=ekhoLzlHRjdWc0NOY2FQM0NPemdkZz09 Everyone is welcome and encouraged to attend. To add to the meeting agenda the topics you’d like to discuss,

[Numpy-discussion] Feature Request: Left (and Right) inverse of the Cross Product

2025-06-02 Thread Leon Deligny via NumPy-Discussion
### Proposed new feature or change: Motivations: This is specific to 3D vector algebra. In Fluid Dynamics, we have access to the moment of a force at a specific point (M_P = OP \cross F). This calculation is crucial when determining the center of pressure (CoP), a pivotal concept for understand

[Numpy-discussion] Re: Feature Request: Left (and Right) inverse of the Cross Product

2025-06-02 Thread Oscar Benjamin via NumPy-Discussion
On Mon, 2 Jun 2025 at 14:26, Leon Deligny via NumPy-Discussion wrote: > > ### Proposed new feature or change: > > Motivations: This is specific to 3D vector algebra. In Fluid Dynamics, we > have access to the moment of a force at a specific point (M_P = OP \cross F). > T

[Numpy-discussion] Re: Feature Request: Left (and Right) inverse of the Cross Product

2025-06-02 Thread Robert Kern via NumPy-Discussion
On Mon, Jun 2, 2025 at 1:09 PM Oscar Benjamin via NumPy-Discussion < numpy-discussion@python.org> wrote: > In vectors the minimum norm solution for b in a x b = c is just bhat = > (c x a) / |a|^2 so the cross product computes its own "inverse": > > In [135]: np.cros

[Numpy-discussion] next NumPy community meeting - Wednesday, June 18th, 2025 at 5 pm UTC

2025-06-15 Thread Inessa Pawson via NumPy-Discussion
The next NumPy community meeting will be held this Wednesday, June 18th at 17:00 (5 pm) UTC. Join us via Zoom: https://numfocus-org.zoom.us/j/83278611437?pwd=ekhoLzlHRjdWc0NOY2FQM0NPemdkZz09 Everyone is welcome and encouraged to attend. To add to the meeting agenda the topics you’d like to discuss,

[Numpy-discussion] next NumPy triage meeting - Wednesday, June 25th, 2025 at 5 pm UTC

2025-06-21 Thread Inessa Pawson via NumPy-Discussion
The next NumPy triage meeting will be held this Wednesday, June 25th at 17:00 (5 pm) UTC. This is a meeting where we synchronously triage prioritized PRs and issues. Everyone is welcome to attend and contribute to a conversation. Join us via Zoom: https://numfocus-org.zoom.us/j/82096749952?pwd=MW9o

[Numpy-discussion] Re: NumPy security roadmap proposal

2025-06-13 Thread Ralf Gommers via NumPy-Discussion
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

[Numpy-discussion] Re: Bumping CPU baseline to x86-64-v2

2025-06-13 Thread Ralf Gommers via NumPy-Discussion
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

[Numpy-discussion] we have a NumPy PyPI organization now

2025-06-16 Thread Ralf Gommers via NumPy-Discussion
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

[Numpy-discussion] Re: we have a NumPy PyPI organization now

2025-06-16 Thread matti picus via NumPy-Discussion
On Mon, Jun 16, 2025 at 4:24 PM Ralf Gommers via NumPy-Discussion wrote: > > 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/num

[Numpy-discussion] NumPy security roadmap proposal

2025-06-12 Thread Ralf Gommers via NumPy-Discussion
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

[Numpy-discussion] Re: NumPy security roadmap proposal

2025-06-13 Thread matti picus via NumPy-Discussion
On Fri, Jun 13, 2025 at 9:40 AM Ralf Gommers via NumPy-Discussion wrote: > > ... > For 2FA and repository/PyPI access, we'll start making changes soon. Note > that GitHub has recently made changes to its 2FA settings that ask for action > from many people: on https://g

[Numpy-discussion] Re: NumPy security roadmap proposal

2025-06-13 Thread Andrew Nelson via NumPy-Discussion
On Fri, 13 Jun 2025 at 16:43, Ralf Gommers via NumPy-Discussion < numpy-discussion@python.org> wrote: > > For 2FA and repository/PyPI access, we'll start making changes soon. Note > that GitHub has recently made changes to its 2FA settings that ask for > action fro

[Numpy-discussion] Re: Bumping CPU baseline to x86-64-v2

2025-06-15 Thread Ralf Gommers via NumPy-Discussion
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). >

[Numpy-discussion] Re: Feature Request: Left (and Right) inverse of the Cross Product

2025-06-02 Thread Robert Kern via NumPy-Discussion
On Mon, Jun 2, 2025 at 9:30 AM Leon Deligny via NumPy-Discussion < numpy-discussion@python.org> wrote: > ### Proposed new feature or change: > > Motivations: This is specific to 3D vector algebra. In Fluid Dynamics, we > have access to the moment of a force at a specific poin

[Numpy-discussion] next NumPy triage meeting - Wednesday, June 11th, 2025 at 5 pm UTC

2025-06-07 Thread Inessa Pawson via NumPy-Discussion
The next NumPy triage meeting will be held this Wednesday, June 11th at 17:00 (5 pm) UTC. This is a meeting where we synchronously triage prioritized PRs and issues. Everyone is welcome to attend and contribute to a conversation. Join us via Zoom: https://numfocus-org.zoom.us/j/82096749952?pwd=MW9o

[Numpy-discussion] ANN: NumExpr 2.11.0, with free-threaded support, is out!

2025-06-09 Thread Francesc Alted via NumPy-Discussion
= Announcing NumExpr 2.11.0 = Hi everyone, NumExpr 2.11.0 Initial support for free-threaded Python 3.13t has been added. This is still experimental, so please report any issues you find. Finally, Python 3.10 is now the minimum supported version. Pr

[Numpy-discussion] Silent data type casting

2025-06-09 Thread oc-spam66--- via NumPy-Discussion
Hello, I discovered the horror below. Do we really want silent data type casting in this case? from numpy import * x = array([0]) x[0] = 1.7# Silent data type casting print(x)# Prints [1] instead of [1.7] Olivier ___ NumPy-Discussion maili

[Numpy-discussion] next NumPy Optimization Team meeting - Monday, June 16th, 2025 at 5 pm UTC

2025-06-12 Thread Inessa Pawson via NumPy-Discussion
Hi, all! The next NumPy Optimization Team meeting will be held on Monday, June 16th at 17:00 UTC. Join us via Zoom: https://numfocus-org.zoom.us/j/81261288210?pwd=iwV99tGSjR61RTGEERKM4QKxe46g1n.1 Everyone is welcome and encouraged to attend. To add to the meeting agenda the topics you’d like to dis

[Numpy-discussion] Addition of eigenvalue functions

2025-06-12 Thread waqar jamali via NumPy-Discussion
NumPy currently lacks a generalized eigenvalue function such as eig(A, B) or polyeig(A, B). These functions are essential for several algorithms, including the Criss-Cross algorithm and various eigenvalue problems. In particular, large-scale problems in control theory are often reduced to subsp

[Numpy-discussion] Tricky ufunc implementation question

2025-06-27 Thread Benjamin Root via NumPy-Discussion
I'm looking at a situation where I like to wrap a C++ function that takes two doubles as inputs, and returns an error code, a position vector, and a velocity vector so that I essentially would have a function signature of (N), (N) -> (N), (N, 3), (N, 3). When I try to use np.vectorize() or np.fromp

[Numpy-discussion] Re: Tricky ufunc implementation question

2025-06-27 Thread Warren Weckesser via NumPy-Discussion
On Fri, Jun 27, 2025 at 5:29 PM Benjamin Root via NumPy-Discussion wrote: > > I'm looking at a situation where I like to wrap a C++ function that takes two > doubles as inputs, and returns an error code, a position vector, and a > velocity vector so that I essentially woul

[Numpy-discussion] Re: Tricky ufunc implementation question

2025-06-27 Thread Benjamin Root via NumPy-Discussion
I'll have a look at your examples. I did try that signature with np.vectorize() with the signature keyword argument, but it didn't seem to work. Maybe it didn't work for the reasons in that open issue. Thank you, Ben Root On Fri, Jun 27, 2025 at 8:03 PM Warren Weckesser via NumPy-

[Numpy-discussion] Re: Can't launch Jupyter

2025-06-28 Thread Robert Kern via NumPy-Discussion
On Sat, Jun 28, 2025 at 8:42 AM Kwaku Oppong via NumPy-Discussion < numpy-discussion@python.org> wrote: > can someone helps me. Whenever i ytried to launch Jupyter from Navigator, > this is the message I gets > Sorry, this isn't the place for Jupyter questio

[Numpy-discussion] Can't launch Jupyter

2025-06-28 Thread Kwaku Oppong via NumPy-Discussion
can someone helps me. Whenever i ytried to launch Jupyter from Navigator, this is the message I gets [I 2025-06-28 02:56:24.163 ServerApp] Extension package panel.io.jupyter_server_extension took 1.1084s to import [I 2025-06-28 02:56:24.164 ServerApp] jupyter_lsp | extension was successfully li

[Numpy-discussion] next NumPy community meeting - Wednesday, July 2nd, 2025 at 5 pm UTC

2025-06-28 Thread Inessa Pawson via NumPy-Discussion
The next NumPy community meeting will be held this Wednesday, July 2nd at 17:00 (5 pm) UTC. Join us via Zoom: https://numfocus-org.zoom.us/j/83278611437?pwd=ekhoLzlHRjdWc0NOY2FQM0NPemdkZz09 Everyone is welcome and encouraged to attend. To add to the meeting agenda the topics you’d like to discuss,

[Numpy-discussion] Re: ENH: Efficient operations on already sorted arrays

2024-01-16 Thread Peter Schneider-Kamp via NumPy-Discussion
Dear all, I second Yagiz’ proposal. I do, however, see that we need to ensure code style (and probably other forms of) consistency before merging these new functions in. And, particularly important, adherence to the conventions of function and method names. Cheers, Peter From: Yağız Ölmez Da

[Numpy-discussion] NumPy 2.1.2 released.

2024-10-05 Thread Charles R Harris via NumPy-Discussion
Hi All, On behalf of the NumPy team, I'm pleased to announce the release of NumPy 2.1.2. NumPy 2.1.2 is a maintenance release that fixes bugs and regressions discovered after the 2.1.1 release. This release supports Python 3.10-3.13. Wheels can be downloaded from PyPI

[Numpy-discussion] Re: What to do with np.matrix

2024-10-14 Thread Charles R Harris via NumPy-Discussion
On Mon, Oct 14, 2024 at 8:09 AM Sebastian Berg wrote: > On Sat, 2024-10-12 at 12:13 -0400, Marten van Kerkwijk wrote: > > Hi Dan, others, > > > > > > > Regardless, since there have been 7 years of > > PendingDeprecationWarning, > > I think changing that to a regular DeprecationWarning should not

[Numpy-discussion] Re: What to do with np.matrix

2024-10-14 Thread Charles R Harris via NumPy-Discussion
On Mon, Oct 14, 2024 at 9:10 AM Nathan wrote: > Here's a github code search for the string "np.matrix": > > https://github.com/search?q=%22np.matrix%22&type=code > > First, if you narrow down to just Python code, there are almost 60 > thousand results, which is quite high, much higher than we we'

[Numpy-discussion] Re: help

2024-10-03 Thread Kevin Toronto Developer via NumPy-Discussion
Hi, Can you check numpy version as if you try to run latest numpy with older version, u would get error as well ..Kevin On Wed, Oct 2, 2024 at 8:10 AM Usha Gayatri via NumPy-Discussion < numpy-discussion@python.org> wrote: > I am working on a Jupyter notebook in Anaconda Navigator. I

[Numpy-discussion] NumPy 2.2.x has been branched

2024-11-23 Thread Charles R Harris via NumPy-Discussion
Hi All, NumPy 2.2.x has been branched and main is now open for 2.3.0 development. Chuck ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3/l

[Numpy-discussion] NumPy 2.2.0 Released

2024-12-08 Thread Charles R Harris via NumPy-Discussion
Hi All, On behalf of the NumPy team, I'm pleased to announce the release of NumPy 2.2.0. The NumPy 2.2.0 release is a short release that brings us back into sync with the usual twice yearly release cycle. There have been a number of small cleanups, as well as work bringing the new StringDType to c

[Numpy-discussion] Re: [EXTERNAL] Copy on __setitem__

2024-12-25 Thread Israel, Daniel M via NumPy-Discussion
Numerical Algorithms d...@lanl.gov On Dec 25, 2024, at 3:23 PM, Steven Ellis wrote: Hi David, New to the listserv, but, maybe you can provide a reproducible example? Steven On Wed, Dec 25, 2024, 2:19 PM Israel, Daniel M via NumPy-Discussion mailto:numpy-discussion@python.org>> wrote: I was up

[Numpy-discussion] Re: [EXTERNAL] Copy on __setitem__

2024-12-27 Thread Israel, Daniel M via NumPy-Discussion
with `copy=True`. Would you open an issue on github? - Sebastian On Thu, 2024-12-26 at 03:46 +, Israel, Daniel M via NumPy- Discussion wrote: Sure. I didn’t originally, because I thought it would require an entire custom array container, but the following trivial example actually shows the

[Numpy-discussion] NumPy 2.2.1 released

2024-12-21 Thread Charles R Harris via NumPy-Discussion
Hi All, On behalf of the NumPy team, I'm pleased to announce the release of NumPy 2.2.1. NumPy 2.2.1 is a patch release following 2.2.0. It fixes bugs found after the 2.2.0 release and has several maintenance pins to work around upstream changes. There was some breakage in downstream projects fol

[Numpy-discussion] NumPy 2.2. 2 Release

2025-01-18 Thread Charles R Harris via NumPy-Discussion
Hi All, On behalf of the NumPy team, I'm pleased to announce the release of NumPy 2.2.2. NumPy 2.2.2 is a patch release that fixes bugs found after the 2.2.1 release. The number of typing fixes/updates is notable. This release supports Python 3.10-3.13. Wheels can be downloaded from PyPI

[Numpy-discussion] Copy on __setitem__

2024-12-25 Thread Israel, Daniel M via NumPy-Discussion
I was updating some code that uses a custom array container built with the mixin library. Specifically, I was trying to eliminate some warnings due to the change to the __array__ interface to add a copy argument. In doing so, I discovered that, for two objects u, v in my container class, the c

[Numpy-discussion] NumPy 2.2.4 released

2025-03-16 Thread Charles R Harris via NumPy-Discussion
Hi All, On behalf of the NumPy team, I'm pleased to announce the release of NumPy 2.2.3. NumPy 2.2.4 is a patch release that fixes bugs found after the 2.2.3 release. There are a large number of typing improvements, the rest of the changes are the usual mix of bug fixes and platform maintenance.

[Numpy-discussion] Add noncentral student's t-distribution

2025-04-05 Thread Seungwoo (Simon) Kim via NumPy-Discussion
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: - (scipy noncentral t) https://docs.scipy.org/doc/scipy/reference/generated/scipy.stats.nct.html - (numpy standard t) ht

[Numpy-discussion] Re: Moving the meetings schedule to one hour earlier

2025-03-26 Thread Charles R Harris via NumPy-Discussion
On Wed, Mar 26, 2025 at 1:18 PM Sebastian Berg wrote: > Hi all, > > it's that time of the year again where daylight savings time starts > (the US had it already and Europe will have it now). > > I suggest we "realign" our meeting to this time zone (since it is > scheduled as UTC), I think for our

<    1   2   3   4   >