Re: [Numpy-discussion] My introduction to NumPy community

On 27/3/19 5:14 pm, Arpita Dash wrote: Hello, My name is Arpita Dash and I'm an Outreachy Applicant. I'm a CSE undergraduate. I am interested in contributing to the Numpy project "Improve C API documentation for Numpy." I am looking forward to working with Numpy and contributing to the communit

Re: [Numpy-discussion] Outreachy Applicant

On 28/3/19 11:37 pm, Sargam Monga wrote: Hello everyone, I am Sargam, an undergrad from India.I am an outreachy applicant and would like to contribute to this project. On 28/3/19 7:37 pm, Aishwarya Dash wrote: Hi, I'm Aishwarya Dash, an applicant for Outreachy. I am quite interested to work o

Re: [Numpy-discussion] Beginner Help: Generating HTML using Sphinx

On 31/3/19 10:56 pm, Mbeng Tanyi wrote: Hello I also got an error the first time I tried $ make file as follows: mkdir -p build/html build/doctrees LANG=C sphinx-build -b html -WT --keep-going -d build/doctrees source build/html /bin/sh: 1: sphinx-build: not found Makefile:

Re: [Numpy-discussion] Beginner Help: Generating HTML using Sphinx

Note the /home/valentina-t/.local/lib/python2.7 in the error message. This indicates you are using python2.7, not python3.6. Please try using a virtual environment or activating a conda environment. If you need further help please reach out to me personally. Matti On 2/4/19 11:41 am, Mbeng T

[Numpy-discussion] overhauling numpy.random and randomgen

Thanks to the work of Kevin Sheppard, Robert Kern and others, the branch to merge randomgen https://github.com/bashtage/randomgen into numpy is ready for final review. The branch is here https://github.com/numpy/numpy/pull/13163. It is fully backward compatible: numpy.random.mtrand, numpy.ran

Re: [Numpy-discussion] Adding to the non-dispatched implementation of NumPy methods

On 27/4/19 6:51 am, Marten van Kerkwijk wrote: Maybe it is best to just stick with __wrapped__ +1 for simplicity, clarity (since __wrapped__ is part of the |documented @functools.wraps() interface)|, and lowering expectations. Matti ___ NumPy-

Re: [Numpy-discussion] GSoD'19 project discussion

On 6/5/19 4:51 pm, Oishika Pradhan wrote: Hi, I am Oishika Pradhan, a research student at IIIT Hyderabad, India. I am interested in machine learning and neural networks and hence have used numpy very regularly in my projects and

Re: [Numpy-discussion] Contributing: NumPy Documentation

On 6/5/19 10:22 pm, Bhanu Bhandari wrote: Hello, I’m Bhanu, a third year student of Electronics and Computers Engineering. I’d like to get started with contributing into the NumPy documentation. I’m a writer who is actively machine learning research as well, and have used NumPy extensively for

[Numpy-discussion] numpy.org/neps not refreshing

When we merge a PR, a CI job on circleCI updates both https://github.com/numpy/neps and https://github.com/numpy/devdocs. These are meant to be served as github pages at http://www.numpy.org/neps/ and http://www.numpy.org/devdocs respectively. For some reason the devdocs is updating but the nep

Re: [Numpy-discussion] defining a NumPy API standard?

On 1/6/19 7:31 pm, Charles R Harris wrote: I generally agree with this. The most useful aspect of this exercise is likely to be clarifying NumPy for its own developers, and maybe offering a guide to future simplification. Trying to put something together that everyone agrees to as an official s

Re: [Numpy-discussion] (Value Based Promotion) Current Behaviour

On 14/6/19 1:37 am, Sebastian Berg wrote: For such a scalar object instead what would seem necessary is to call a `dtype.__coerce_pyvalue__(scalar, casting="safe")`, or a `__can_coerce_pyvalue__` method/slot. It would replace the current `PyArray_CanCastArrayTo`, which can only handle the current

[Numpy-discussion] Top level release index page

In PR 13886 I reworked the way the link to the release notes is generated. The current page is http://www.numpy.org/devdocs/release.html and  the new page is https://8001-908607-gh.circle-artifacts.com/0/home/circleci/repo/doc/build/html/release.html I don't like the "wall of text" in the

[Numpy-discussion] Shippable builds are broken - I filed an issue with them

For the past few days shippable (arm builds) CI has been failing. I opened an issue with them https://github.com/Shippable/support/issues/4882 ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/nump

[Numpy-discussion] Adding a "suffle=True" kwarg to numpy.random.Generator.choice

In PR https://github.com/numpy/numpy/pull/13812, Thrasibule rewrote the algorithm used with a faster alternative branch for some cases. The faster algorithm does not necessarily shuffle the results, so for instance gen.choice(2000, 2000, replace=False) may simply return arange(2000). In the old

[Numpy-discussion] Using a pyproject.toml file

In PR #13908 I implemented the previously-discussed new method of creating the release notes: writing separate fragments and then combining them at release time via towncrier. Towncrier requires a PEP-508/PEP-517/PEP-518 pyproject.toml file for configuration, and

[Numpy-discussion] Kriti (our Outreachy intern) has published a blog post about being accepted to the program

https://github.com/kritisingh1/numpy/wiki/Now-You-Know-It! Worth a read, see what applicants go through to get accepted. Feel free to re-publish it. There will be more coming as she progresses through the summer. ___ NumPy-Discussion mailing list N

[Numpy-discussion] Reformat the wall-of-text release notes

Our Release Note page https://numpy.org/devdocs/release.html is one long litany of all the releases ever. While this is convenient for searching with CTRL-F, it is not conducive to browsing. I suggested splitting it into pages with a TOC page https://8001-908607-gh.circ

Re: [Numpy-discussion] Numpy twitter handle?

On 18/8/19 7:36 am, Abdur-Rahmaan Janhangeer wrote: Poor me a paper has been published citing numpy in the top 10 imports (the others being from the std lib), it was a great event as it was the conclusion after analysing ALL of pypi. A ping would have sufficed to notify. From the tweet: http

[Numpy-discussion] Allowing Dependabot access to the numpy repo

In PR 14378 https://github.com/numpy/numpy/pull/14378 I moved all our python test dependencies to a test_requirements.txt file (for building numpy the only requirement is cython). This is worthy since it unifies the different "pip install" commands across the diff

Re: [Numpy-discussion] Allowing Dependabot access to the numpy repo

eds write permission seems to be to be able to work with private repos: https://github.com/dependabot/feedback/issues/22 There doesn't seem to be any way around it... :( Ryan On Thu, Aug 29, 2019 at 12:04 AM Matti Picus mailto:matti.pi...@gmail.com>> wrote:

[Numpy-discussion] Using hypothesis in testing

We have discussed using the hypothesis package to generate test cases at a few meetings informally. At the EuroSciPy sprint, kitchoi took up the challenge and issued a pull request https://github.com/numpy/numpy/pull/14440 that actually goes ahead and does it. Whi

Re: [Numpy-discussion] DType Roadmap/NEP Discussion

On 19/9/19 2:34 am, Sebastian Berg wrote: Hi all, to try and make some progress towards a decision since the broad design is pretty much settling from my side. I am thinking about making a meeting, and suggest Monday at 11am Pacific Time (I am open to other times though). My hope is to get ever

Re: [Numpy-discussion] Low-level API for Random

On 20/9/19 6:25 am, Robert Kern wrote: Well, we must because one's used by the legacy RandomState and one's used by Generator. :-) I would prefer not to create a legacy C-API at all. Are we required to from the NEP? Matti ___ NumPy-Discussio

Re: [Numpy-discussion] Low-level API for Random

On 20/9/19 2:18 pm, Neal Becker wrote: I have used C-api in the past, and would like to see a convenient and stable way to do this. Currently I'm using randomgen, but calling (from c++) to the python api. The inefficiency is amortized by generating and caching batches of results. I thought ran

[Numpy-discussion] Unsupporting python3.5

According to NEP 29, numpy 1.18 will be released after Sept 2019, which as I understand it is the cutoff for Python 3.5. In PR 14673 I proposed removing it from the test matrix and also removing some shims in the code to support it - meaning that in order to use N

[Numpy-discussion] Deprecate norm of 3d and more ndarrays

np.norm(a, axis=None) where a.ndim > 2 calls np.norm(np.ravel(a)). PR 14719 proposes deprecating this unexpected behavior, with the suggestion that people who need this should call ravel themselves. Thoughts? Matti ___ NumPy-Discussion mailing lis

[Numpy-discussion] Numpy community meeting Wed Oct 23

Hi all, There will be a NumPy Community meeting Wednesday Oct 23 at 11 am Pacific Time. Everyone is invited to join in and edit the work-in- progress meeting topics and notes: https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both Matti ___ NumPy-Discussion ma

[Numpy-discussion] NEP 34 - deprecate automatic dtype=object on ragged arrays

After a few iterations by reviewers, I would like to submit NEP 34 to deprecate automatically using dtype=object for ragged arrays. https://github.com/numpy/numpy/pull/14674 and an associated PR for the implementation https://github.com/numpy/numpy/pull/14794 Commments? Matti Abstract

[Numpy-discussion] Numpy community meeting Wed Oct 30

Hi all, There will be a NumPy Community meeting Wednesday Oct 30 at 11 am Pacific Time. Everyone is invited to join in and edit the work-in- progress meeting topics and notes: https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both Matti ___ NumPy-Discussion mai

[Numpy-discussion] Disallow Accelerate as a LAPACK backend for NumPy

Apple has dropped support for Accelerate. It has bugs that have not been fixed, and is closed source so we cannot fix them ourselves. We have been getting a handful of reports from users who end up building NumPy on macOS, and inadvertently link to Accelerate, then end up with wrong linalg resu

[Numpy-discussion] Numpy community meeting TODAY !!!

Hi all, Sorry for the late notice There will be a NumPy Community meeting Wednesday Nov 13 (today) at 11 am Pacific Time. Everyone is invited to join in and edit the work-in- progress meeting topics and notes: https://hackmd.io/76o-IxCjQX2mOXO_

Re: [Numpy-discussion] Disallow Accelerate as a LAPACK backend for NumPy

On Tue, Nov 12, 2019 at 12:41 AM Matti Picus wrote: Apple has dropped support for Accelerate. It has bugs that have not been fixed, and is closed source so we cannot fix them ourselves. We have been getting a handful of reports from users who end up building NumPy on macOS

[Numpy-discussion] "Proposal to accept NEP 34: Disallow inferring dtype=object from sequence

I propose to move the NEP https://numpy.org/neps/nep-0034.html from "draft" to "accepted" status. There were no objections (actually there were no responses at all) to the mail proposing the NEP https://mail.python.org/pipermail/numpy-discussion/2019-October/080200.html. PR 14794 https://gith

[Numpy-discussion] NumPy community meeting Wed Nov 20

There will be a NumPy Community meeting Wednesday Nov 20 at 11 am Pacific Time. Everyone is invited to join in and edit the work-in-progress meeting topics and notes: https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both Matti ___ NumPy-Discussion mailing lis

[Numpy-discussion] Updated numpy.random C-API

Hi everyone, We recently officially exposed and documented[0] the C-API side of numpy.random. There are now working examples[3] of using numpy.random from numba[1], cython[2], and cffi[5]. Please try this out before the 1.18 release by installing the latest HEAD version and making sure the

Re: [Numpy-discussion] Proposal to accept NEP 34: Disallow inferring dtype=object from sequence

On 16/11/19 1:42 pm, Matti Picus wrote: I propose to move the NEP https://numpy.org/neps/nep-0034.html from "draft" to "accepted" status. There were no objections (actually there were no responses at all) to the mail proposing the NEP https://mail.python.org/pipermail/n

[Numpy-discussion] removing undocumented use of __array__(dtype, context)

A code path and test have been in the code since NumPy 0.4 for a two-argument variant of ``__array__(dtype=None, context=None)``. It was activated when calling ``ufunc(op)`` or ``ufunc.reduce(op)`` if ``op.__array__`` existed. However that variant is not documented, and it is not clear what the

Re: [Numpy-discussion] Numpy support for Microblaze

On 9/1/20 10:03 pm, pnp wrote: Are there some steps to add support to a new cpu such as microblaze? Regards. -- Sent from: http://numpy-discussion.10968.n7.nabble.com/ ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python

[Numpy-discussion] Re-enable deprecation warning for "ragged arrays"

A few months ago we merged an implementation of "NEP 34 - Disallow inferring dtype=object from sequences" https://numpy.org/neps/nep-0034.html but it broke downstream packages like scipy, pandas, matplotlib, astropy (those are the ones we know about). Since then, the downstream projects seem to

[Numpy-discussion] NEP 38 - Universal SIMD intrinsics

Together with Sayed Adel (cc) and Ralf, I am pleased to put the draft version of NEP 38 [0] up for discussion. As per NEP 0, this is the next step in the community accepting the approach layed out in the NEP. The NEP PR [1] has already garnered a fair amount of discussion about the viability of

Re: [Numpy-discussion] NEP 38 - Universal SIMD intrinsics

On 11/2/20 7:16 am, Ralf Gommers wrote: On Tue, Feb 4, 2020 at 2:00 PM Hameer Abbasi mailto:einstein.edi...@gmail.com>> wrote: —snip— > 1) Once NumPy adds the framework and initial set of Universal Intrinsic, if contributors want to leverage a new architecture specific SIMD

Re: [Numpy-discussion] NEP 38 - Universal SIMD intrinsics

On 11/2/20 8:02 pm, Devulapalli, Raghuveer wrote: On top of that the performance implications aren’t clear. Software implementations of hardware instructions might perform worse and might not even produce the same result. The proposal for universal intrinsics does not enable replacing an

Re: [Numpy-discussion] Opportunities for a NumPy sprint in Japan

On 12/3/20 8:14 am, David Cournapeau wrote: I will try to join the meeting next week though (where are the info to join ?), David The next one will be a community meeting on Wed Mar 18, 11am California time on this zoom channel https://berkeley.zoom.us/j/762261535. We will be updating

Re: [Numpy-discussion] Proposal: NEP 41 -- First step towards a new Datatype System

On 24/3/20 11:48 am, Francesc Alted wrote: What I am trying to say is that NumPy should be rather agnostic about providing data types beyond the relatively simple set that already supports.  I am suggesting that focusing on providing a way to allow the storage (not only in-memory, but also p

Re: [Numpy-discussion] NEP 41: Is there still need to discuss DTypes vs. Scalars (or DType classes)?

On 20/4/20 11:37 pm, Sebastian Berg wrote: Hi all, ... In my proposal the DType class (i.e. `type(np.dtype("float64")`), is the core concept and different for every scalar type. It holds all the information on how to deal with array elements. This is some duplication of scalar types and it me

Re: [Numpy-discussion] Closing resolved good-first-issues

On 3/5/20 1:39 pm, Tina Oberoi wrote: These are the issues that have pull requests merged but still open, Please let me know if I am wrong else we can close these issues: - Issue #9476 - Issue #2802 - Is

Re: [Numpy-discussion] Call for Reviewers

On 20/5/20 11:27 pm, Anirudh Subramanian wrote: Hi all, This topic was brought up in the triage meeting today. Numpy is seeing a huge surge in the number of PRs (current open PRs: 253) which could means two things: 1. Increase in volume of incoming PRs 2. Not enough reviewers to review the PR

Re: [Numpy-discussion] reseed random generator (1.19)

On 6/29/20 5:37 PM, Kevin Sheppard wrote: The best practice is to use a SeedSequence to spawn child SeedSequences, and then to use these children to initialize your generators or bit generators.  

Re: [Numpy-discussion] NumPy Documentation Gallery structure

I think those projects use https://github.com/sphinx-gallery/sphinx-gallery to do the layout Matti On 7/8/20 9:31 AM, Saber Tooth wrote: Hello Melissa and Ralf , I was just wondering if we haven't h

Re: [Numpy-discussion] Replacement for Rackspace

On 8/10/20 10:54 PM, Peter Wang wrote: FWIW, we're happy to provide wheel hosting for statsmodels on anaconda.org . -Peter On Fri, Aug 7, 2020 at 8:01 AM Kevin Sheppard mailto:kevin.k.shepp...@gmail.com>> wrote: The Rackspace hosted wheel endpoints at https:/

Re: [Numpy-discussion] Replacement for Rackspace

, Peter On Mon, Aug 10, 2020 at 9:20 PM Matti Picus <matti.pi...@gmail.com> wrote: anaconda is generously hosting projects at https://anaconda.org/scipy-wheels-nightly/ (for weekly development release

Re: [Numpy-discussion] Proposal: split numpy.distutils into it's own package

On 10/25/20 10:46 AM, Dustin Spicuzza wrote: I took a first stab at it, and... surprise, surprise, there were a few more warts than I had originally expected in my initial survey. The biggest unexpected result is that numpy.f2py would need to also be a toplevel package. I did get the refactor c

Re: [Numpy-discussion] Proposal: split numpy.distutils into it's own package

On 10/25/20 5:39 PM, Dustin Spicuzza wrote: Sorry for not being clear, when I was discussing modifications to scipy I was referring to the specific use case of cross-compilation. The goal is that existing native builds would not break backwards compatibility. To that end, there's a package redi

Re: [Numpy-discussion] Should we transfer MacPython/numpy-wheels to the NumPy org?

On 10/29/20 5:42 AM, Charles R Harris wrote: Hi All, Seems that is pretty easy to transfer a github repo to another owner. Should we do this for the numpy-wheels repo? That would put all the management in one place and now might be a good time to do it before the 1.20.x branch. Chuck W

Re: [Numpy-discussion] Should we transfer MacPython/numpy-wheels to the NumPy org?

On 10/29/20 4:42 PM, Charles R Harris wrote: My thought was administration, which was triggered by the need to move to travis-ci.com. Note that the travis app shows up on the MacPytho

[Numpy-discussion] New package to speed up ufunc inner loops

Hi. On behalf of Quansight and RTOSHoldings, I would like to introduce "pnumpy", a package to speed up NumPy. https://quansight.github.io/numpy-threading-extensions/stable/index.html What is in it? - use "PyUFunc_ReplaceLoopBySignature" to hook all the UFunc inner loops - When the inner loop

Re: [Numpy-discussion] start of an array (tensor) and dataframe API standardization initiative

On 11/10/20 8:19 PM, Ralf Gommers wrote: Hi all, I'd like to share an update on this topic. The draft array API standard is now ready for wider review: - Blog post: https://data-apis.org/blog/array_api_standard_release - Array API st

Re: [Numpy-discussion] Proposal: add the timestamp64 type (Noam Yorav-Raphael)

On 11/12/20 6:04 PM, Stefano Miccoli wrote: On 11 Nov 2020, at 18:00, numpy-discussion-requ...@python.org wrote: I propose to add a new type called "timestamp64". It will be a pure timestamp, meaning that it represents a moment in time (as sec

[Numpy-discussion] shipping manylinux1 wheels - when do we stop?

The question of manylinux1 wheels came up enough that I wrote a blog post about it. In short: for 1.21 I would like to ship only manylinux2014 and up. Here is the blog post https://labs.quansight.org/blog/2020/11/manylinux1-is-obsolete-manylinux2010-is-almost-eol-what-is-next/ Matti

Re: [Numpy-discussion] shipping manylinux1 wheels - when do we stop?

On 11/13/20 5:57 PM, Charles R Harris wrote: Good job summarizing the information. I looked at the code for how Python supports pip and it seems build dependent, it isn't part of the Python library, so I'm not sure that pip and Python versions are strongly associated. I didn't find any such li

[Numpy-discussion] Changing the size of PyArrayObject_fields (the ndarray c-struct)

PyArrayObject_fields is the c-struct that underlies ndarray. It is defined in ndarraytypes.h [0]. Since version 1.7, we have been trying to hide it from the public C-API so that we can freely modify it, the structure has the comment:  * It has been recommended to use the inline functions defi

Re: [Numpy-discussion] Installing numpy

NumPy HEAD does not support python2. You should use v1.16.6 which was the last release to support python2. Matti On 12/14/20 4:14 PM, Lianyuan Zheng wrote: Is this caused by the python version installed too old (v2.7.17) or other

Re: [Numpy-discussion] locking np.random.Generator in a cython nogil context?

On 12/17/20 11:47 AM, Evgeni Burovski wrote: Just as a side note, this is not very prominent in the docs, and I'm ready to volunteer to send a doc PR --- I'm only not sure which part of the docs, and would appreciate a pointer. Maybe here https://numpy.org/devdocs/reference/random/bit_genera

Re: [Numpy-discussion] proposal for NumPy sponsorship guidelines (NEP 46)

On 12/29/20 1:27 PM, Ralf Gommers wrote: Entities who fall under "significant active supporter" we'll call Sponsor. The minimum level of support given to NumPy to be considered a Sponsor are: - $30,000/yr for unrestricted financial contributions - $60,000/yr for financial contributions for a

Re: [Numpy-discussion] Sayed Adel has joined the developer team.

On 1/4/21 6:05 PM, Charles R Harris wrote: Hi All, Sayed Adel is now part of the developer team. His SIMD work has been substantial and ongoing, may it long continue. Welcome Sayed. Chuck Welcome Sayed. Matti ___ NumPy-Discussion mailing list

Re: [Numpy-discussion] NumPy EOL Versions?

This message ended up in my spam box for some reason, sorry for the late reply. We typically release a new version twice a year, and support two versions at a time. So right now we are releasing version 1.20 and will support 1.19 and 1.20 for the next period. When 1.21 is released, we will s

Re: [Numpy-discussion] Unreliable crash when converting using numpy.asarray via C buffer interface

On 2/1/21 9:57 AM, Friedrich Romstedt wrote: Hi, Am Di., 26. Jan. 2021 um 09:48 Uhr schrieb Friedrich Romstedt : [...] The following Python code crashes:: image = <... Image production ...> ar = numpy.asarray(image) However, when I say:: image = <... Image production ...>

[Numpy-discussion] Speed up large arrays with PNumPy

I am pleased to announce the first release of PNumPy: a project to seamlessly speed up NumPy for large arrays (64K+ elements) with no change required to your existing NumPy code. PNumPy supports Linux, Windows, and MacOS on top of NumPy >= 1.18 for python 3.6, 3.7, 3.8, and 3.9. This first rele

Re: [Numpy-discussion] ENH: Proposal to add KML_BLAS support

On 2/22/21 2:13 PM, ChunLin Fang wrote:   Hi all,     Whether you're running apps on your phone or the world's fastest supercomputer, you're most likely running ARM. Many major events have occurred related to ARM archtecture:

Re: [Numpy-discussion] guide for downstream package authors & setting version constraints

This is a different topic altogether. I think you would get better results asking on the cython-users mailing list with a concrete example of something that didn't work. Matti On 3/6/21 7:52 PM, zoj613 wrote: Is there a best practice guide somewhere in the docs on how to correctly expose C-l

Re: [Numpy-discussion] Numpy 1.20.1 availability

On 3/14/21 6:12 AM, dan_patterson wrote: Any idea why the most recent version isn't available on the main anaconda channel. conda-forge and building are not options for a number of reasons. I posted a package request there but double digit days have gone by it just got

[Numpy-discussion] NEP 49: Data allocation strategies

I have submitted NEP 49 to enable user-defined allocation strategies for the ndarray.data homogeneous memory area. The implementation is in PR 17582 https://github.com/numpy/numpy/pull/17582 Here is the text of the NEP: Abstract The ``numpy.ndarray`` requires additional memory alloca

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 suc

[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] 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. ... ### Th

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

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 PR

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: https://pypi.org/project/num

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` keywor

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

[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] https://mail.python.or

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

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 `library_di

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 spen

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 th

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 consistenc

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

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 instal

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 possib

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 function

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 set

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

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

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

[Numpy-discussion] Re: Musllinux wheels

On 11/10/21 4:38 pm, Matthew Brett wrote: Hi, It will probably soon be trivial to do a manylinux Alpine build / test on multibuild. There's a work on progress PR here, https://github.com/matthew-brett/multibuild/pull/430 that only requires someone to build a trivial test container, in order t

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

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

<    1   2   3   >