[Numpy-discussion] Re: Build NumPy with Debugging Symbols with Meson

On 15/05/2024 23:55, Robert McLeod wrote: | | Hi everyone, | | Is there a gist or similar guide anywhere on the steps required to build NumPy with debugging symbols on the Windows platform using the new Meson build system? In general, I would try to avoid using python_d.exe. It requires the

[Numpy-discussion] Re: New feature

For a start you could share the link for the stand-alone package here, with a short description of what it does. Additional steps would be to write a blog post about it, write it up on reddit's python subreddit, give a talk about it at a conference. Matti On 25/04/2024 23:36, Alexei

[Numpy-discussion] Re: Please consider dropping Python 3.9 support for Numpy 2.0

On 05/05/2024 11:32, Mark Harfouche wrote: I know this is somewhat the 11th hour for the numpy 2.0 release but as downstream packager and user of numpy, I would really like to ask that Numpy strives to adhere to NEP29, and SPEC0 SEPC0 makes it pretty clear that Python 3.9 should not be

[Numpy-discussion] Re: New feature

On 25/04/2024 23:16, Alexei Lisitsa wrote: Waiting for answer What kind of answer would you like? I took a look at numpy_list[0] and if it serves your needs, that is great, but I don't think such ndarray generation routines should be added to NumPy until they become more commonly known,

[Numpy-discussion] Re: Making show_runtime and show_config enable file output

On 09/04/2024 2:42, Matan Addam wrote: Hello, I find the information printed by the above mentioned functions to be useful for understanding performance context on installed machines, as well as variability across machines when troubleshooting. How would the maintainers view a pull request

[Numpy-discussion] Moving the weekly traige/community meetings

Could we move the weekly community/triage meetings one hour later? Some participants have a permanent conflict, and the current time is inconvenient for my current time zone. Matti ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To

[Numpy-discussion] Re: Accelerated NumPy with Weld compiler

On 20/3/24 15:13, Hemant Singh via NumPy-Discussion wrote: Stanford and MIT jointly developed the Weld language and compiler to run NumPy and Pandas significantly faster, 10x-250x. My company has changed the compiler to be production ready. Anyone interested in trialing this compiler, please

[Numpy-discussion] Re: Arrays of variable itemsize

I am not sure what kind of a scheme would support various-sized native ints. Any scheme that puts pointers in the array is going to be worse: the pointers will be 64-bit. You could store offsets to data, but then you would need to store both the offsets and the contiguous data, nearly doubling

[Numpy-discussion] Change in behaviour: broadcasting rules for np.solve

API changes should hit the mailing list, so I am copying from PR https://github.com/numpy/numpy/pull/25914 by Aaron Meurer: Previously the np.linalg.solve documentation stated: |a : (..., M, M) array_like Coefficient matrix. b : {(..., M,), (..., M, K)}, array_like | however, this is

[Numpy-discussion] Re: builing numpy on windows

On 27/2/24 06:09, Ganesh Rajora via NumPy-Discussion wrote: Hi Team, I am Ganesh working for an MNC here in India and I am working on customised Python where I build set of python modules with python. I do not install them directly from web but I build each and everything from source code. 

[Numpy-discussion] Re: JSON format for multi-dimensional data

On 20/2/24 01:24, phili...@loco-labs.io wrote: Hi community, This memo is a proposal to implement a compact and reversible (lossless round-trip) JSON interface for multi-dimensional data and in particular for Numpy (see issue #12481). The links to the documents are at the end of the memo.

[Numpy-discussion] Re: How does Numpy model non-float arrays?

On 22/8/23 02:25, Dylon Edwards wrote: It is my understanding that Numpy accelerates array operations with BLAS where possible, but BLAS does not support all the dtypes that Numpy does. How does Numpy model non-float arrays like arrays of dtype=bool or dtype=object? Numpy only uses BLAS

[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

[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

[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

[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

[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

[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

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

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

[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

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

[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

[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

[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

[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] 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

[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

[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

[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

[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

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

[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

[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

[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] 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

[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

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

[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

[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] 

[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

[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

[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

[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

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

[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

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

[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

[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

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

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

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 > > > mailto:charlesr.ha

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

[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

[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

[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

[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

[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

[Numpy-discussion] spam on the mailing lists

The list default for new subscribers is to hold posts for approval before sending to the mailing list. Hopefully that will cut down the number of spam messages, at the cost of delay of maybe a day for new subscriber posts. In order to make the policy clear, I submitted a PR to numpy.org [0].

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

It seems the spammers have figured out how to get onto discourse as well. The last two messages on https://discuss.python.org/t/pypi-user-feedback/11125/4 (on the python discourse instance) are the first I have seen there. Matti On 10/10/21 7:37 pm, Hameer Abbasi wrote: Hello everyone,

[Numpy-discussion] Re: Intel's Short Vector Math Library has been merged as a git submodule

On 11/10/21 11:05 pm, Jerome Kieffer wrote: On Mon, 11 Oct 2021 18:04:58 +0300 Matti Picus wrote: As SciPy already found out, some downstream libraries may need to tweak their tolerances for some functions as a result of this PR. We wanted to put it in early enough in the release cycle so

[Numpy-discussion] Intel's Short Vector Math Library has been merged as a git submodule

Yesterday we merged PR 19478 [0] to add a open source version of Intel's Short Vector Math library into NumPy. The original PR was by Raghuveer Devulapalli. There was a lot of discussion on the PR, but now that I look back it seems the mailing list may not have been involved. The code lives in

[Numpy-discussion] Re: Musllinux wheels

On 11/10/21 2:22 pm, Ralf Gommers wrote: On Mon, Oct 11, 2021 at 9:52 AM Laurie O > wrote: CI request: build PEP 656 (https://www.python.org/dev/peps/pep-0656/ ) compliant "musllinux" wheels.

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

On 29/9/21 9:07 pm, Stefan van der Walt wrote: On Wed, Sep 29, 2021, at 03:02, Ralf Gommers wrote: We don't have admin access to the python.org lists, so this is a bit of a problem. We have never had a spam problem, so we can ask to block this user first. If it continues

[Numpy-discussion] Re: Moving community meeting to 16:00 UTC

On Tue, Sep 28, 2021 at 7:20 PM Sebastian Berg mailto:sebast...@sipsolutions.net>> wrote: Sorry about that, lets go with 16:30 UTC then, at least for now.  I will announce that later for tomorrow.  If that ends up bad for anyone (or the situation just changes) we can still move it. Could

Re: [Numpy-discussion] Help Regarding Debugging Cython Code

On 5/9/21 12:55 pm, Amardeep Singh wrote: Hi Team If some one has setup to debug cython code can  you please share the details. I am using ubuntu 20.4 . Not sure why gdb not picking up breakpoints. I am able to debug c extensions but not cython code. Thx There are a number of ways to

Re: [Numpy-discussion] Adding New Feature

On 19/8/21 6:15 pm, Bhavay Malhotra wrote: Dear Team, I’m thinking of adding a new feature in response to the issue no. #19039. The feature is basically a function to check whether the data type of both the numpy arrays are same or not. If the numpy arrays have different data types

Re: [Numpy-discussion] Drop LGTM testing.

On 15/8/21 12:15 am, Charles R Harris wrote: On Sat, Aug 14, 2021 at 2:35 PM Eric Wieser mailto:wieser.eric%2bnu...@gmail.com>> wrote: This might be worth creating a github issue for simply so we can tag someone working at LGTM; they've been helpful in the past, and it's

Re: [Numpy-discussion] reducing effort spent on wheel builds?

On 16/7/21 9:11 pm, Chris Barker wrote: Just a note on: > For the record, I am +1 on removing sdists from PyPI until pip changes its default to --only-binary :all: [1] I agree that the defaults for pip are unfortunate (and indeed the legacy of pip doing, well, a lot, (i.e. building and

Re: [Numpy-discussion] Revert the return of a single NaN for `np.unique` with floating point numbers?

On 2/8/21 8:49 pm, Ralf Gommers wrote: On Mon, Aug 2, 2021 at 7:04 PM Sebastian Berg mailto:sebast...@sipsolutions.net>> wrote: Hi all, In NumPy 1.21, the output of `np.unique` changed in the presence of multiple NaNs.  Previously, all NaNs were returned when we now only

Re: [Numpy-discussion] Proposal to accept NEP 49: Data allocation strategies

The NEP [0] and the corresponding PR [1] have gone through another round of editing. I would like to restart the discussion here if anyone has more to add. Things that have changed since the last round: - The functions now accept a context argument - The code has been cleaned up for

Re: [Numpy-discussion] reducing effort spent on wheel builds?

On 15/7/21 4:11 pm, Ralf Gommers wrote: On Thu, Jul 15, 2021 at 2:41 PM Matti Picus <mailto:matti.pi...@gmail.com>> wrote: On the other hand, packaging is made harder as more technologies go into a wheel build. ... Perhaps there should be some discussion of

Re: [Numpy-discussion] reducing effort spent on wheel builds?

On 15/7/21 1:21 pm, Ralf Gommers wrote: Hey all, I've seen Chuck and Matti burn a lot of time on the numpy-wheels repo again recently, and I've done the same for SciPy. ... Cheers, Ralf Since my name was mentioned, the things I have spent time on for wheel packaging in order of time

Re: [Numpy-discussion] NumPy's BLAS library on macOS?

On 8/7/21 2:23 am, Jerry Morrison wrote: Got it! *Summary:* * Installing a numpy wheel (e.g. `pip install numpy==1.21.0`) uses its embedded OpenBLAS on every platform that has a wheel.   That OpenBLAS is always compiled with gcc/gfortran.   In this case, `np.show_config()` reports

Re: [Numpy-discussion] `keepdims=True` for argmin/argmx and C-API `PyArray_ArgMaxWithKeepdims`

On 1/7/21 7:49 pm, Gagandeep Singh wrote: Hi, So should I remove these new functions from public C-API? Let me know. I will do that. Yes please. If needed we can add them, but once in we cannot remove them. Matti ___ NumPy-Discussion mailing

[Numpy-discussion] Acceptance of NEP 36 - fair play

Stefan has submitted a PR [0] to accept "NEP 36 -fair play" as accepted. It was discussed recently on the mailing list [1] and in the original PR [2] . If there is no opposition in a week (27 June) the PR will be merged. [0]https://github.com/numpy/numpy/pull/19284 [1]

Re: [Numpy-discussion] copy="never" discussion and no deprecation cycle?

On 18/6/21 2:23 am, Stephan Hoyer wrote: Overall, I think using an enum is the happiest situation. It's a slightly awkward API, to be sure, but not very awkward in the scheme of things, and it's

Re: [Numpy-discussion] copy="never" discussion and no deprecation cycle?

On 16/6/21 11:00 pm, Sebastian Berg wrote: Hi all, (sorry for the length, details/discussion below) On the triage call, there seemed a preference to just try to skip the deprecation and introduce `copy="never"`, `copy="if_needed"`, and `copy="always"` (i.e. string options for the `copy`

Re: [Numpy-discussion] NEP 36- fair play (was: request to remove the numpy-aarch64 package from PyPI)

On 14/6/21 11:03 pm, Stefan van der Walt wrote: On Sun, Jun 13, 2021, at 18:21, Charles R Harris wrote: On Sun, Jun 13, 2021 at 10:47 AM Ralf Gommers > wrote: FYI, I noticed this package that claimed to be maintained by us:

Re: [Numpy-discussion] PR for keywordlabeler

On 10/6/21 10:20 pm, Charles R Harris wrote: Hi All, There is a pending PR that uses keywordlabeler  to automatically label PRs and issues. Installing the app requires giving it write permissions to

Re: [Numpy-discussion] EHN: Discusions about 'add numpy.topk'

On 29/5/21 5:28 pm, Ralf Gommers wrote: On Fri, May 28, 2021 at 4:58 PM > wrote: Hi all, Finding topk elements is widely used in several fields, but missed in NumPy. I implement this functionality named as  numpy.topk using core numpy

Re: [Numpy-discussion] Proposal to accept NEP 49: Data allocation strategies

On 10/5/21 8:43 pm, Sebastian Berg wrote: But right now the proposal says this is static, and I honestly don't see much reason for it to be freeable? I think this is the crux of the issue. The current design is for a singly-allocated struct to be passed around since it is just an aggregate

Re: [Numpy-discussion] Proposal to accept NEP 49: Data allocation strategies

On 6/5/21 2:07 pm, Eric Wieser wrote: The NEP looks good, but I worry the API isn't flexible enough. My two main concerns are: ### Stateful allocators Consider an allocator that aligns to `N` bytes, where `N` is configurable from a python call in someone else's extension module. ... ###

[Numpy-discussion] Proposal to accept NEP 49: Data allocation strategies

Here is the current rendering of the NEP:https://numpy.org/neps/nep-0049.html The mailing list discussion, started on April 20 did not bring up any objections to the proposal, nor were there objections in the discussion around the text of the NEP. There were questions around details of the

Re: [Numpy-discussion] NEP 49: Data allocation strategies

See my comments interspersed in Ralf's reply. Thanks for the additional context. Matti On 21/4/21 3:10 am, Ralf Gommers wrote: ... Motivation and Scope Users may wish to override the internal data memory routines with ones of their own. Two

  1   2   3   >