[Numpy-discussion] Re: spam on the mailing lists

Update: we now have a team of moderators for the mailing list. The policy for moderation is in the list summary [0]. Since moderation began on Oct 26, we have rejected 15 spam messages, unsubscribed 2 email addresses that spammed more than 3 each, and released 4 messages from moderated users t

[Numpy-discussion] Re: [RFC] - numpy/SVML appears to be poorly optimized

On 6/11/21 6:56 pm, Sayed Adel wrote: > appears to be poorly optimized. It should perform well, not poor neither heavily optimized. > this also makes it quite difficult to improve (with either a better compiler or by hand). We can put the blame on Intel for not sharing their source code but

[Numpy-discussion] Re: spam on the mailing lists

Upate: since there is a clear delineation of spammers vs legitimate posts, I would like to tweak the policy [0] and from now on a single spam message will move email addresses down a category: from authorized to moderated and from moderated to unsubscribed. I have changed the policy statement ac

[Numpy-discussion] Re: installing numpy on OpenIndiana

Your mail ended up in my spam bucket, maybe that is why no-one responded. On 11/11/21 8:58 pm, asyropou...@aol.com wrote: ld: fatal: file _configtest.o: wrong ELF class: ELFCLASS64 There is something seriously off with the way the co

[Numpy-discussion] Deprecating PyDataMem_SetEventHook

NumPy has had a way to add a call to a user-supplied function whenever allocating via PyDataMem_SetEventHook [0]. Python added the tracemalloc [1] functionality which make this redundant. NumPy also added memory alloc/free overriding in NEP 49 [2] which will be part of the 1.22 release. I propo

[Numpy-discussion] Re: computation of transcendentals

Many of the ufuncs like exp and log are hightly optimized kernels which use SIMD intrinsics where possible. The code can be found in various files in tthe numpy/core/src/umath directory, for instance here is the beginning of the SIMD exp function https://github.com/numpy/numpy/blob/f521ee5f9a9868f3

[Numpy-discussion] Re: help with PyArrayInterface

On 21/12/21 11:27 pm, blor...@lbl.gov wrote: ... but I don't know what the typekind value should be. Can you point to a list of vlaues? ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-l

[Numpy-discussion] Re: An article on numpy data types

On 26/12/21 3:44 pm, Michael Siebert wrote: Hey Lev, I‘ve forgotten to mention my MacBook M1, it‘s also int64 there. Python on Windows is and is supposed to be, as far as I get it, a dying platform. Your statement is the first time I have heard this. Of those who answered the 2020 Python

[Numpy-discussion] Re: No credits left in travis for 1.22.0 release

On 31/12/21 3:50 am, Charles R Harris wrote: On Thu, Dec 30, 2021 at 6:26 PM Charles R Harris mailto:charlesr.har...@gmail.com>> wrote: Hi All, We need to get more credits in order to run MacPython/numpy-wheels builds on travis. Anyone recall how to go about this? Chuck

[Numpy-discussion] Re: Who is the tallest and strongest Chinese basketball player?

On 31/12/21 6:14 am, Just allstar wrote: Yao Ming ... Sorry, I hit the wrong button when filtering spam off the list. Matti ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@py

[Numpy-discussion] Re: No credits left in travis for 1.22.0 release

ess sure about the other > systems)? > > James > > On Fri, 31 Dec 2021 at 17:03, Matti Picus wrote: > > > > > > On 31/12/21 3:50 am, Charles R Harris wrote: > > > > > > > > > On Thu, Dec 30, 2021 at 6:26 PM Charles R Harris > > > mai

[Numpy-discussion] Re: No credits left in travis for 1.22.0 release

On 6/1/22 2:15 pm, Peter Cock wrote: Hello Matti, Charles, ... Do you have any advice on how to request TravisCI credits (I'd be happy to discuss off list), or would you advise us to focus on the migration now (which pushes back any release plans). Thank you, Peter Here is what travis-ci wr

[Numpy-discussion] Re: MacPython travis funds have run out (again)

On 14/1/22 3:04 am, Charles R Harris wrote: Hi All, Travis wheel build problems again. There is still a positive balance, but apparently it is insufficiently positive. Which is strange if ARM64 is free. Wheel builds have been failing since last weekend. Matti, could you ask for more credit

[Numpy-discussion] Re: MacPython travis funds have run out (again)

On Fri, Jan 14, 2022, 08:53 Matti Picus <mailto:matti.pi...@gmail.com>> wrote: ... If we want to move off travis for aarch64, I think the only option right now is to use emulation, conda-forge does this on Azure machines [0] and the build + tests takes ~40 m

[Numpy-discussion] Re: MacPython travis funds have run out (again)

On 14/1/22 10:51 am, Matti Picus wrote: On 14/1/22 3:04 am, Charles R Harris wrote: Hi All, Travis wheel build problems again. There is still a positive balance, but apparently it is insufficiently positive. Which is strange if ARM64 is free. Wheel builds have been failing since last

[Numpy-discussion] Re: NumPy 1.22.1 has been released.

On 18/1/22 5:37 pm, Peter Cock wrote: Dear Charles, Thank you for your work on the numpy releases, including v1.22.1. I noticed that for Windows Python 3.10, there is only a 64-bit wheel: ... Is this expected? My interest is in building Windows Wheels for packages compiling against NumPy.

[Numpy-discussion] Re: Unpacking 0-D object arrays when setting item/filling

On 15/2/22 09:53, Stefan van der Walt wrote: On Mon, Feb 14, 2022, at 12:45, Sebastian Berg wrote: But this is currently *not* consistently the case. I wish to make this consistent. The confusion is around object arrays, though: value = np.array(None, dtype=object) arr[0] = value

[Numpy-discussion] Re: NumPy 1.21.6 released

On 12/4/22 19:46, Charles R Harris wrote: Hi All, On behalf of the NumPy team I am pleased to announce the release of NumPy 1.21.6. NumPy 1.21.6 is a very small release that achieves two things: * Backs out the mistaken backport of C++ code into 1.21.5. * Provides a 32 bit Windows wheel

[Numpy-discussion] Re: Automatic formatters for only changed lines

On 6/5/22 01:32, Stefan van der Walt wrote: On Thu, May 5, 2022, at 12:00, Trevor Gross wrote: I don't necessarily know that this should be enforced on CI off the bat (though in the future it could be), but at least having the tool available and easily usable would help to incrementally improv

[Numpy-discussion] Re: Automatic formatters for only changed lines

On 6/5/22 09:09, Stefan van der Walt wrote: Hi Matti, On Thu, May 5, 2022, at 22:08, Matti Picus wrote: This somehow runs when I do "git commit"? Do I need to add anything to my git environment to pick up the hook? How do I turn it off if I find it prevents progress or breaks? Do

[Numpy-discussion] Re: [Feature Request] Add alias of np.concatenate as np.concat

The array API defines concat [0] so that is a powerful reason to implement an alias as part of bringing NumPy into compliance. Matti [0] https://data-apis.org/array-api/latest/API_specification/manipulation_functions.html ___

[Numpy-discussion] Re: Enhancement for AArch64 SVE instruction set

On 19/5/22 16:50, kawakam...@fujitsu.com wrote: Hello, I am working on speeding up NumPy with the AArch64 SVE instruction set. I could not find a numpy implementation for SVE. Is there already a test implementation or discussion about SVE support? OpenBLAS apparently has SVE support from 0.3

[Numpy-discussion] Re: New stable documentation

On Sat, 21 May 2022 at 08:46, Ralf Gommers wrote: > > > On Sat, May 21, 2022 at 3:40 AM Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> Hi All, >> >> I've put up new stable documentation for NumPy 1.22.4. I'd appreciate it >> if those familiar with how they want the documentation to l

[Numpy-discussion] Re: New stable documentation

On Sat, 21 May 2022 at 16:26, Charles R Harris wrote: > > > On Sat, May 21, 2022 at 5:38 AM Sebastian Berg > wrote: > >> On Sat, 2022-05-21 at 10:33 +0300, matti picus wrote: >> > On Sat, 21 May 2022 at 08:46, Ralf Gommers >> > wrote: >> > >

[Numpy-discussion] Re: Dropping the pdf documentation.

On 23/5/22 01:51, Rohit Goswami wrote: Being very hard to read should not be reason enough to stop generating them. In places with little to no internet connectivity often the PDF documentation is invaluable. I personally use the PDF documentation both on my phone and e-reader when I trave

[Numpy-discussion] Re: NEP 29 and the faster Python release cadence

On 26/5/22 05:40, Aaron Meurer wrote: We cannot do that (yet, at least). Failing to publish wheels for a supported Python version on a major OS is far worse than dropping support completely. This will remain true until the time that Pip starts defaulting to wheels-only and never picks the sdi

[Numpy-discussion] Re: Numpy binary wheels and CI for win/arm64 platform

When you say "we could request access to new Volterra machines": how do you see that playing out? Who would provide them, and who would maintain them? Would they be available to the more general scientific python community? Who would pay the bill? If the people supporting this niche platform st

[Numpy-discussion] Re: Fuzzing integration of Numpy into OSS-Fuzz

On 7/6/22 14:02, david korczynski wrote: Hi Numpy maintainers, Would you be interested in integrating continuous fuzzing by way of OSS-Fuzz? Fuzzing is a way to automate test-case generation and has been heavily used for memory unsafe languages. Recently efforts have been put into fuzzing memor

[Numpy-discussion] Re: Njumpy-stl

Hmm. Do you mean this project [0] on PyPI? It is developed by a team entirely separate from NumPy. The README should have an appropriate disclaimer. Frank you can find more information about the library in their documentation [1] Matti [0] https://pypi.org/project/numpy-stl/ [1]  https://num

[Numpy-discussion] Re: numpy build question

On 14/6/22 18:14, Jesse Peet wrote: I am trying to build numpy 1.22.3 in container using a rhel8 host  and the container being rhel7. My version of gcc is 4.8.5-44.   Here is the error I get RuntimeError: Broken toolchain: cannot link a simple C++ program. note: A compiler with support for C+

[Numpy-discussion] Re: assert_array_equal scalar broadcast behaviour

On 16/6/22 19:28, Jon Morris wrote: Hello all, I was recently tripped up by issue #9542 , where a call to assert_array_equal unexpectedly passed because a single scalar can be declared equal to an array if every value in the array is the same. I’

[Numpy-discussion] Re: Need help extending a NumPy array in C

On 8/7/22 01:37, lpsm...@uw.edu wrote: Hello! I am maintaining a C++ codebase with extensive ties to Python bindings (via SWIG). One of the features of the code is that we define (in C) a subclass of a NumPy Array. Everything worked until we started getting this message with numpy 1.23:

[Numpy-discussion] Re: generate a random sample based on independent priors in `random.choice` #22082

Every new feature, method, function or keyword argument adds cognitive load, maintainer burden, makes the package larger, and can confuse users so we reject much more than we accept. The first step would be to present a convincing case _why_ Poisson sampling should be added to NumPy, before di

[Numpy-discussion] Re: aarch64 wheels on github actions

I personally prefer using the travis runs since they get tested, even with the additional maintenance burden of requesting travis credits when they run out. It is good to know there is another option. Matti On 7/8/22 09:15, Andrew Nelson wrote: At the moment Linux aarch64 wheels are being mad

[Numpy-discussion] Re: Display runtime information through a new function: `show_runtime`

My assumption in advising Ganesh to create a new function was that there may be some people who find show_config useful. Personally I do not find it useful. If there is agreement that what matters is runtime and not build-time then we should replace the current show_config. Otherwise we should

[Numpy-discussion] Additional aliases for MaskedArray

PR 21998 [0] adds methods "ones_like", "zeros_like", "dsplit","split", and "vsplit" for MaskedArrays. The motivation was to clean up broken documentation links, and it seemed logical to add the interfaces. As far as I can tell we do not have users asking for these methods. Should we add them (e

[Numpy-discussion] Re: I need help on the issue of replacing the original C math library with an external C math library

Sorry for the late reply, this ended up in my SPAM filter. I think google does not like your qq.com domain. The best way to manage blas/lapack implementations right now is via the site.cfg file, the example site.cfg.example has extensive instructions. If it is not working as expected, please share

[Numpy-discussion] Re: Display runtime information through a new function: `show_runtime`

The PR to implement this was merged Matti ___ 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.py

[Numpy-discussion] Re: Support for Multiple Interpreters (Subinterpreters) in numpy

On 22/8/22 18:59, Eric Snow wrote: Hi all, CPython has supported multiple interpreters (in the same process) for a long time, but only through the C-API. I'm working on exposing that functionality to Python code (see PEP 554), aiming for 3.12. I expect that users will find the feature useful

[Numpy-discussion] Re: Support for Multiple Interpreters (Subinterpreters) in numpy

On 23/8/22 03:16, Matti Picus wrote: ... One thing CPython could do is to provide clear documentation how to port a small c-extension module [1] Matti [1] https://github.com/python/cpython/issues/79601 I should have searched the documentation, there is now a quite extensive guide [2

[Numpy-discussion] Re: An extension of the .npy file format

Sorry for the late reply. Adding a new "*.npy" format feature to allow writing to the file in chunks is nice but seems a bit limited. As I understand the proposal, reading the file back can only be done in the chunks that were originally written. I think other libraries like zar or h5py have so

[Numpy-discussion] Re: Representation of NumPy scalars

On 9/9/22 04:15, Warren Weckesser wrote: ... To quote from https://docs.python.org/3/library/functions.html#repr: For many types, this function makes an attempt to return a string that would yield an object with the same value when passed to eval(); Sebastian, is this an explicit goal of the

[Numpy-discussion] Re: Enhancement for AArch64 SVE instruction set

It seems cirrus-ci offers AWS EKS Graviton2 instances [0] and this is free for open source projects. Do you know if that offering has SVE-enabled CPUs? Matti [0] https://cirrus-ci.org/guide/linux/ On Fri, Sep 16, 2022 at 5:54 AM kawakam...@fujitsu.com wrote: > > Hi, > > It's been a long time sin

[Numpy-discussion] Re: PR hasn't been responded to in 2 weeks

The idea of using fft in polynomial.polymul in the PR got a cool reception. It is not clear if we should add this to NumPy or refer users to other packages.  Maybe the mailing list would be a forum to discuss the need for the enhancement. It should have at least one other champion in order to m

[Numpy-discussion] Re: Introducing Arm Optimized Routines

Thanks, this seems like it would improve performance on aarch64. Would the routines also work with the Apple silicon arm64? If these are new routines, it would be better to implement them in terms of the numpy universal intrinsics rather than adding a new submodule. Matti On 8/11/22 13:30,

[Numpy-discussion] Re: Introducing Arm Optimized Routines

On 8/11/22 19:45, Chris Sidebottom wrote: Hi Matti, Thanks for your questions :-) This seems like it would improve performance on aarch64. Would the routines also work with the Apple silicon? Yip, I can't see a reason why that wouldn't be the case. If these are new routines, it would be

[Numpy-discussion] Add a new CI provider for aarch64, macos arm64, musl

I am writing to the list for visibility: I opened an issue [0] about adding the Cirrus CI provider to take over some of the CI task runners from travis.com. We have been experiencing strange timeouts on the travis runs, and in general the platform does not feel stable. SciPy made the transition

[Numpy-discussion] Re: Expanding support in testing for external collections.Sequence objects

On 30/11/22 05:47, Stefan van der Walt wrote: On Tue, Nov 29, 2022, at 07:21, i...@markopacak.com wrote: The debate is whether np.testing.asset_equal should support collections.Sequence objects. assert list(sequence1) == list(sequence2) should do the trick, and also handles int vs float and n

[Numpy-discussion] Re: ANN: NumPy Fellowship Program & Sayed Adel as our first Developer in Residence

This is an important milestone and a great initiative. I am looking forward to working with Sayed. Matti ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.pytho

[Numpy-discussion] Re: CI: testing of musllinux

On 21/12/22 06:41, Andrew Nelson wrote: On Wed, 21 Dec 2022 at 07:29, Andrew Nelson wrote: In https://github.com/scipy/scipy/issues/17630 we're seeing some issues (amongst others) with the scipy test suite that uses numpy==1.24.0 on musllinux. I was wondering if numpy would l

[Numpy-discussion] Congratulation to our newest maintainer Mukulika Pahari

The NumPy steering council recently granted maintainer rights to Mukulika Pahari (https://github.com/Mukulikaa/) Mukulika was recently elected to co-lead the numpy documentation team, and has been active in reviewing documentation issues and PRs. Welcome and thanks for all you do. Matti

[Numpy-discussion] Re: How to fix this problem? np.arange(0,20.01,0.01)

On 3/4/23 18:11, sideri...@gmail.com wrote: The last element of "np.arange(0,20.01,0.01)" is 20.01 in my python result. Is this numpy error ? ___ This is due to inaccurate float value representation. The documentation for arange states: "When us

[Numpy-discussion] Re: Google Season of Docs 2023 Project Roadmap

On 27/4/23 23:40, Mars Lee wrote: Hi everyone, I'm Mars, the selected technical writer for NumPy’s Google Summer of Docs project proposal, the ‘NumPy Contributor Comics'. The project roadmap and timeline can be read here: https://medium.com/@marsbarlee/gsod-numpy-contributor-comics-project-ro

[Numpy-discussion] Re: Precision changes to sin/cos in the next release?

On 31/5/23 09:33, Jerome Kieffer wrote: Hi Sebastian, I had a quick look at the PR and it looks like you re-implemented the sin-cos function using SIMD. I wonder how it compares with SLEEF (header only library, CPU-architecture agnostic SIMD implementation of transcendental functions with preci

[Numpy-discussion] Re: Precision changes to sin/cos in the next release?

On 31/5/23 14:12, Matthew Brett wrote: The ideal would be a run-time toggle for people to experiment with, with binary wheels. Is that practical? Cheers, Matthew There is a discussion about a runtime context variable/manager that would extend errorstate to have a precision flag as well

[Numpy-discussion] Re: mean_std function returning both mean and std

On 2/6/23 13:09, Ronald van Elburg wrote: Mean_var, mean_std and tests are now ready. (https://github.com/soundappraisal/numpy/tree/stdmean-dev-001) Some decisions made during implementation: - the output shape of mean follows the output shape of the variance or the standard deviation. So

[Numpy-discussion] Re: mean_std function returning both mean and std

On 2/6/23 13:41, Matti Picus wrote: On 2/6/23 13:09, Ronald van Elburg wrote: Mean_var, mean_std and tests are now ready. (https://github.com/soundappraisal/numpy/tree/stdmean-dev-001) Some decisions made during implementation:    - the output shape of mean follows the output shape of the

[Numpy-discussion] Re: Numpy with eigen c++ binding

On 6/6/23 06:46, darshan patel wrote: it seems like numpy is moving toward c++ implementation, so is there any plan to have eigen c++ library also inline with numpy to get better performance? is there any ongoing work happening around this? NumPy does not currently use eigen and I am not awar

[Numpy-discussion] Re: Precision changes to sin/cos in the next release?

In PR 23925 the tests for allowed ULP error for sin and cos were tightened for float32 and float64 to 1.49 and 1.00 respectively. The use of SVML/SIMD routines for sin/cos on float64 was disabled across the board, and the checks all pass. People using the latest H

[Numpy-discussion] Re: New user dtypes and the buffer protocol

On 6/7/23 20:44, Evgeni Burovski wrote: On Thu, Jul 6, 2023 at 7:56 PM Nathan wrote: > > Hi all, > > As you may know, I'm currently working on a variable-width string dtype using the new experimental user dtype API. As part of this work I'm running into papercuts that future dtype authors wil

[Numpy-discussion] Re: mixed mode arithmetic

On 9/7/23 23:34, glaserj--- via NumPy-Discussion wrote: Reviving this old thread - I note that numpy.dot supports in-place computation for performance reasons like this c = np.empty_like(a, order='C') np.dot(a, b, out=c) However, the data type of the pre-allocated c array must match the result

[Numpy-discussion] Re: mixed mode arithmetic

On 10/7/23 16:13, Jens Glaser via NumPy-Discussion wrote: Hi Matti, The documentation for numpy.dot currently states """ out ndarray, optional Output argument. This must have the exact kind that would be returned if it was not used. In particular, it must have the right type, must be C-conti

[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

<    1   2   3