[Numpy-discussion] Re: Endorsing SPECs 1, 6, 7, and 8

It seems to me that we should only endorse SPECs that we ourselves implement, otherwise it is kind of "do as I say, not as I do". For instance, it would be strange to endorse SPEC0 but stay with NEP 29. If we are to endorse SPEC0 without changing our version end-of-life timing, we should at least m

[Numpy-discussion] Re: I am getting an error in anaconda jupyter notebook, I am unable to solve. please help me.

Your version of pandas is not compatible with your version of numpy. Try reinstalling both of them. Matti On Tue, Oct 1, 2024 at 4:27 PM Usha Gayatri via NumPy-Discussion wrote: > > This is the error i am getting when trying to execute import numpy as np > File E:\anaconda3\Lib\site-packages\pand

[Numpy-discussion] Re: help

Maybe python is picking up some other versions of pandas and numpy. What do you get when you check like this import numpy import pandas print(f”{numpy.__version__=}”) print(f”{pandas.__version__=}”) Matti On Wed, 2 Oct 2024 at 15:13, Usha Gayatri via NumPy-Discussion < numpy-discussion@python.or

[Numpy-discussion] Re: Fixing definition of reduceat for Numpy 2.0?

I am not sure how I feel about this. If I understand correctly, the issue started as a corner case when the indices were incorrect, and grew to dealing with initial values, and then added a desire for piecewise reducat with multiple segements. Is that correct? Could you give a better summary of the

[Numpy-discussion] Re: Proposing a flattening functionality for deeply nested lists in NumPy

On Tue, 31 Dec 2024 at 06:41, Mark via NumPy-Discussion < numpy-discussion@python.org> wrote: > Hello all, > > > Many people have asked how to flatten a nested > I think this is out of scope for NumPy. Our bar for adding functionality is quite high. We are unlikely to consider generic routines th

[Numpy-discussion] Build wheels for manylinux_2_24 instead of manylinux2014

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-ov-file#acceptable-distros-to-build-wheels

[Numpy-discussion] Re: Exact representable difference between for two arrays.

On Fri, Dec 20, 2024 at 4:48 AM Andrew Nelson via NumPy-Discussion wrote: > > Or is there a risk that the Python interpreter would prematurely optimize > that to give: > > ``` > dx = h > ``` > > > -- > _ > Dr. Andrew Nelson Wow, that would be a pretty seriou

[Numpy-discussion] Re: Exact representable difference between for two arrays.

The current CPython 3.13 version only has (as far as I know) two types of code-rewriting optimizations: - a rudimentary JIT[1] that replaces byte code with machine code, without changing semantics - a specializer[2] that will take things like a + b, and simplify the byte code if both a and b are kn

[Numpy-discussion] Re: New GitHub issue UI

On 14/01/2025 19:05, Nathan via NumPy-Discussion wrote: GitHub now has support for "issue types". I couldn't figure out how to customize the types, all I see are 'bug', 'feature', 'task' Matti ___ NumPy-Discussion mailing list -- numpy-discussi

[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: Beginners

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 cadence and subjects

[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] 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/numpy/). We can start movi

[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://github.com/orgs/numpy/people