[Numpy-discussion] Re: NumPy security roadmap proposal

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 < > numpy-discussion@python.org> wrote: > >> >> On Fri, 13 Jun 2025 at 16:43, Ralf Gommers via NumPy-Discussion < >> numpy-di

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

The next NumPy community meeting will be held this Wednesday, July 30th 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 2.3.2 released

Hi All, On behalf of the NumPy team, I'm pleased to announce the release of NumPy 2.3.2. The NumPy 2.3.2 release is a patch release with a number of bug fixes and maintenance updates. The highlights are: - Wheels for Python 3.14.0rc1 - PyPy updated to the latest stable release - OpenBLA

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

Hi, all! The next NumPy Optimization Team meeting will be held on Monday, July 28th 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: Python 3.14rc1 is out.

we may be waiting on cirrus. > > Chuck > Looks like the cirrus build uses cibuildwheel, so all we probably need to do is add cp314* . > >> >>> >>> On Tue, Jul 22, 2025 at 5:40 PM Charles R Harris via NumPy-Discussion < >>> numpy-discussion@python.org>

[Numpy-discussion] Re: Python 3.14rc1 is out.

tti moved the build. We may want to backport some of Matti's work for the next release, otherwise we may be waiting on cirrus. Chuck > > >> >> On Tue, Jul 22, 2025 at 5:40 PM Charles R Harris via NumPy-Discussion < >> numpy-discussion@python.org> wrote: >> >&

[Numpy-discussion] Re: Python 3.14rc1 is out.

best to leave OpenBLAS as was until the new release gets some testing. Chuck > > On Tue, Jul 22, 2025 at 5:40 PM Charles R Harris via NumPy-Discussion < > numpy-discussion@python.org> wrote: > >> Hi All, >> >> Just a note. >> >> Chuck >> _

[Numpy-discussion] Re: Python 3.14rc1 is out.

via NumPy-Discussion < numpy-discussion@python.org> wrote: > Hi All, > > Just a note. > > Chuck > ___ > NumPy-Discussion mailing list -- numpy-discussion@python.org > To unsubscribe send an email to numpy-discu

[Numpy-discussion] Python 3.14rc1 is out.

Hi All, Just a note. 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//lists/numpy-discussion.python.org Member address: arch...@mai

[Numpy-discussion] next NumPy New Contributors' Hour - July 24th, 2025 at 10 pm UTC

Our next New Contributors' Hour will be held this Thursday, July 24th 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] next NumPy triage meeting - Wednesday, July 23rd, 2025 at 5 pm UTC

The next NumPy triage meeting will be held this Wednesday, July 23rd 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: Upcoming event ==> Contributing to the NumPy Documentation (Jul 15, 2025)

Hello, We had quite an enthusiastic crowd at today's webinar by Mukulika: Contributing to the NumPy Documentation A link to the video, slides and all shared links is available here: https://blog.dataumbrella.org/numpy An attendee, Charlotte Wickham, already submitted an issue: https://github.com/

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

The next NumPy community meeting will be held this Wednesday, July 16th 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] ENH: Numpy histograms incapable of adding noninteger weights.

It would be great if the dtype= option could be used when creating the histogram in numpy because lots of scientific applications would benefit from being able to use non-integer weights. It would be nice to be able to specify that the histogram should store weights in float64. Thank you so much

[Numpy-discussion] Re: Request to mailing list "NumPy-Discussion" rejected

to NumPy development. I'm not greatly > opposed, it if send another I can let it through. > > Chuck > > On Tue, Jul 8, 2025 at 5:30 AM Yan Georget via NumPy-Discussion < > numpy-discussion@python.org> wrote: > >> Hello, >> >> Can I have a reason

[Numpy-discussion] UPDATE: Documentation team meetings now merged with community/triage meetings

Greetings everyone, I am no longer hosting the bi-weekly documentation meetings; all documentation-related discussions will now take place at the bi-weekly community and triage meetings. Everyone is welcome to attend these meetings and talk about documentation issues or enhancements you are wor

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

Hi, all! The next NumPy Optimization Team meeting will be held on Monday, July 7th 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] Re: Tricky ufunc implementation question

extensions. See e.g. Alex Gaynor’s blog post on this from the perspective of Rust and PyO3: https://alexgaynor.net/2022/oct/23/buffers-on-the-edge/ On Thu, Jul 3, 2025 at 5:50 AM Benjamin Root via NumPy-Discussion < numpy-discussion@python.org> wrote: > On a related note, does numpy

[Numpy-discussion] Re: Tricky ufunc implementation question

orize() 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-Discussion < >

[Numpy-discussion] July'25 announcements

Hi, all! Can you believe we're already halfway through 2025? I hope you're making great progress on whatever you set out to accomplish this year. I’m reaching out with two quick announcements: 1. No triage meeting on July 9th – A few of our regulars will be traveling next week, so we’re skipping

[Numpy-discussion] Upcoming event ==> Contributing to the NumPy Documentation (Jul 15, 2025)

Hello, We are excited to host the following: Upcoming event = = > > Contributing to the NumPy Documentation Speaker: Mukulika Pahari, oceanographer, open source contributor, and NumPy maintainer NumPy is a fundamental, open-source Python library for N-dimensional array programming used extensive

[Numpy-discussion] Re: Tricky ufunc implementation question

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-Discussion < >

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

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

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

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: Tricky ufunc implementation question

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: Tricky ufunc implementation question

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] Tricky ufunc implementation question

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] NumPy 2.3.1 released

Hi All, On behalf of the NumPy team, I'm pleased to announce the release of NumPy 2.3.1. The NumPy 2.3.1 release is a patch release with several bug fixes, annotation improvements, and better support for OpenBSD. Highlights are: - Fix bug in ``matmul`` for non-contiguous out kwarg parameter

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

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: we have a NumPy PyPI organization now

On Mon, Jun 16, 2025 at 7:24 AM Ralf Gommers via NumPy-Discussion < numpy-discussion@python.org> 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 thro

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

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] we have a NumPy PyPI organization now

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] next NumPy community meeting - Wednesday, June 18th, 2025 at 5 pm UTC

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] Re: Bumping CPU baseline to x86-64-v2

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: Bumping CPU baseline to x86-64-v2

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] Re: NumPy security roadmap proposal

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: NumPy security roadmap proposal

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: NumPy security roadmap proposal

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] NumPy security roadmap proposal

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: Addition of eigenvalue functions

12, 2025 at 6:39 AM waqar jamali via NumPy-Discussion < numpy-discussion@python.org> wrote: > 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

[Numpy-discussion] Addition of eigenvalue functions

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] next NumPy Optimization Team meeting - Monday, June 16th, 2025 at 5 pm UTC

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] Silent data type casting

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] ANN: NumExpr 2.11.0, with free-threaded support, is out!

= 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] NumPy 2.3.0 released

Hi All, On behalf of the NumPy team, I'm pleased to announce the release of NumPy 2.3.0. The NumPy 2.3.0 release improves free threaded Python support and annotations together with the usual set of bug fixes. It is unusual in the number of expired deprecations, code modernizations, and style clea

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

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] Re: Wondering if there is interest in a "variable convolution" feature in numpy?

Thanks for the response, Nathan! I'll check in with SciPy. They have quite a few different convolution functions. Our backup is publishing this as a standalone package on PyPI and conda-forge. I wanted to see if it made sense to integrate it with something else first, though. Unfortunately

[Numpy-discussion] Re: Wondering if there is interest in a "variable convolution" feature in numpy?

PyOpenSci guide, which has extensive guidance for writing and publishing packages for general consumption: https://www.pyopensci.org/python-package-guide/index.html On Wed, Jun 4, 2025 at 6:32 AM cantor.duster--- via NumPy-Discussion < numpy-discussion@python.org> wrote: > Hello, > &

[Numpy-discussion] Wondering if there is interest in a "variable convolution" feature in numpy?

Hello, My team and I (especially @Arqu1100) have been working on energy-dependent convolutions for a nuclear physics application: https://github.com/det-lab/energyDependentColvolve. We're looking to release this code either as a standalone library or as part of a library because we ran into qu

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

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] Re: Feature Request: Left (and Right) inverse of the Cross Product

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

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] Feature Request: Left (and Right) inverse of the Cross Product

### 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] next NumPy community meeting - Wednesday, June 4th, 2025 at 5 pm UTC

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] Interesting discussion of ``fast-math``

Hi All, Thought some might find this discussion interesting. Chuck ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://

[Numpy-discussion] NumPy 2.3.0rc1 Released

Hi All, On behalf of the NumPy team, I'm pleased to announce the release of NumPy 2.3.0rc1. The NumPy 2.3.0rc1 release continues the work to improve free threaded Python support and annotations together with the usual set of bug fixes. It is unusual in the number of expired deprecations and the nu

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

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] next NumPy Optimization Team meeting - Monday, May 26th, 2025 at 5 pm UTC

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] ANN: Python-Blosc2 3.3.4 released

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] NumPy 2.3.x has been branched

Hi All, The main branch is now open for NumPy 2.4.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//lists/numpy-discu

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

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] next NumPy community meeting - Wednesday, May 21st, 2025 at 5 pm UTC

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] Re: Bumping CPU baseline to x86-64-v2

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] Re: Bumping CPU baseline to x86-64-v2

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] NumPy 2.2.6 released

Hi All, NumPy 2.2.6 is a patch release that fixes bugs found after the 2.2.5 release. It is a mix of typing fixes/improvements as well as the normal bug fixes and some CI maintenance. This release supports Python 3.10-3.13. Wheels can be downloaded from PyPI

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

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] Re: Bumping CPU baseline to x86-64-v2

On Fri, May 16, 2025 at 4:23 AM Sayed Adel wrote: > Hi All, > > I wanted to bring your attention to an important change to NumPy that will > affect CPU compatibility requirements on x86. > > PR #28896 (https://github.com/numpy/numpy/pull/28896) is reorganizing how > NumPy handles x86 CPU features

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

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] Translations project - Crowdin migration

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

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: Dropping PyPy in NumPy 2.3

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] Dropping PyPy in NumPy 2.3

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, and it is also likely that there will be no PyPy for Python 3.12. It looks like PyPy is reaching end of life, and this seems a good time to decide i

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

- 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: [hpy-dev] Re: [pypy-dev] Re: Better compatibility of the Python scientific/data stack with fast Python interpreters

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] Re: next Documentation team meeting

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] next NumPy community meeting - Wednesday, May 7th, 2025 at 5 pm UTC

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: Add Sampling with Dynamic weights with replacement to np.random.choice

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] next NumPy Optimization Team meeting - Monday, May 5th, 2025 at 5 pm UTC

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] Add Sampling with Dynamic weights with replacement to np.random.choice

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] Fwd: [pypy-dev] Re: Better compatibility of the Python scientific/data stack with fast Python interpreters

-- 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] Re: Fwd: Research Opportunity: Can we monitor your projects?

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] Re: Better compatibility of the Python scientific/data stack with fast Python interpreters

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] next NumPy triage meeting - Wednesday, April 30th, 2025 at 5 pm UTC

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?

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?

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] Fwd: Research Opportunity: Can we monitor your projects?

Just thought I'd pass this along for discussion. Chuck -- Forwarded message - From: Date: Tue, Apr 29, 2025 at 4:09 PM Subject: Research Opportunity: Can we monitor your projects? To: Charles Harris Hello Charles Harris, I'm Samuel Flint, and I'm working with Dr. Robert Dyer

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

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] Re: ENH: Add saturating arithmetic functions

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] NumPy Steering Council membership update

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] next NumPy community meeting - Wednesday, April 23rd, 2025 at 5 pm UTC

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 2.2.5 released

Hi All, NumPy 2.2.5 is a patch release that fixes bugs found after the 2.2.4 release. It has a large number of typing fixes/improvements as well as the normal bug fixes and some CI maintenance. This release supports Python 3.10-3.13. Wheels can be downloaded from PyPI

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

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] next NumPy triage meeting - Wednesday, April 16th, 2025 at 5 pm UTC

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

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

> 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] next NumPy Optimization Team meeting - Monday, April 14th, 2025 at 5 pm UTC

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: Add noncentral student's t-distribution

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 > stra

[Numpy-discussion] next NumPy community meeting - Wednesday, April 9th, 2025 at 5 pm UTC - now meeting ONE HOUR EARLIER

The next NumPy community meeting will be held this Wednesday, April 9th at 17:00 (5 pm) UTC. Please note the TIME CHANGE! 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

[Numpy-discussion] next NumPy triage meeting - Wednesday, April 2nd, 2025 at 5 pm UTC - now meeting ONE HOUR EARLIER

Hi, everyone! The next NumPy triage meeting will be held this Wednesday, April 2nd at 17:00 (5 pm) UTC. Please note the TIME CHANGE! 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://

  1   2   3   4   >