[Numpy-discussion] updated backwards compatibility and deprecation policy NEP

Hi all, Here is a long overdue update of the draft NEP about backwards compatibility and deprecation policy: https://github.com/numpy/numpy/pull/18097 - This is NEP 23: https://numpy.org/neps/nep-0023-backwards-compatibility.html - Link to the previous mailing list discussion: https://mail.python

Re: [Numpy-discussion] updated backwards compatibility and deprecation policy NEP

lg in which, what to do is crystal > clear but how to do it without breaking anything is herding the cats hence > I am genuinely curious how to go about this. > If anyone has a good proposal, that'd be great. But I find it hard to come up with those few lines right now. Cheers, Ralf

Re: [Numpy-discussion] updated backwards compatibility and deprecation policy NEP

On Sat, Jan 2, 2021 at 3:55 AM Sebastian Berg wrote: > On Wed, 2020-12-30 at 11:43 -0600, Sebastian Berg wrote: > > On Wed, 2020-12-30 at 16:27 +0100, Ralf Gommers wrote: > > > > > That's very hard to describe, since it relies so much on previous > experience an

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

On Sun, Jan 3, 2021 at 8:43 AM Matti Picus wrote: > > 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 Spons

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

On Mon, Jan 4, 2021 at 5:35 PM Matti Picus wrote: > > 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. > Very we

Re: [Numpy-discussion] Welcome Chunlin to the NumPy development team.

On Tue, Jan 5, 2021 at 3:27 PM Charles R Harris wrote: > Hi All, > > Welcome Chunlin Fang, aka Qiyu8, to the NumPy development team. He has > made substantial contributions to the SIMD infrastructure, both code and > reviews, and we look forward to his continuing work. > Awesome. Thanks for all

Re: [Numpy-discussion] NumPy EOL Versions?

On Wed, Jan 13, 2021 at 4:41 PM Matti Picus wrote: > 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 an

Re: [Numpy-discussion] NumPy EOL Versions?

On Wed, Jan 13, 2021 at 6:50 PM Charles R Harris wrote: > > > On Wed, Jan 13, 2021 at 10:47 AM Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> >> >> On Wed, Jan 13, 2021 at 9:04 AM Ralf Gommers >> wrote: >> >>> &g

Re: [Numpy-discussion] Value based promotion and user DTypes

On Tue, Jan 26, 2021 at 2:01 AM Sebastian Berg wrote: > Hi all, > > does anyone have a thought about how user DTypes (i.e. DTypes not > currently part of NumPy) should interact with the "value based > promotion" logic we currently have? > For now I can just do anything, and we will find out later

Re: [Numpy-discussion] NumPy video content: creating a YouTube channel

On Mon, Jan 25, 2021 at 6:45 PM Melissa Mendonça wrote: > Hi all, > > The NumPy Documentation Team has been discussing video content as part of > our outreach and documentation efforts, in part inspired by the excellent > Spyder IDE channel [1]. At our last meeting, we realized there is already a

[Numpy-discussion] accepting NEP 23 - backwards compatibility and deprecation policy NEP

Hi all, The update PR was merged after a lot more review on GitHub. I propose we change the status of this NEP to Accepted. We'll merge a PR to do so unless there are objections within the next five days. Cheers, Ralf On Wed, Dec 30, 2020 at 3:05 PM Ralf Gommers wrote: > Hi all, >

[Numpy-discussion] accepting NEP 46 - sponsorship guidelines

Hi all, The sponsorship guidelines PR ( https://numpy.org/neps/nep-0046-sponsorship-guidelines.html) was merged as Draft and everyone seems happy with it. I propose to change its status to Accepted. We'll merge a PR to do so unless there are objections within the next five days. Cheers, Ralf

Re: [Numpy-discussion] Value based promotion and user DTypes

On Tue, Jan 26, 2021 at 10:21 PM Sebastian Berg wrote: > On Tue, 2021-01-26 at 06:11 +0100, Ralf Gommers wrote: > > On Tue, Jan 26, 2021 at 2:01 AM Sebastian Berg < > > sebast...@sipsolutions.net> > > wrote: > > > > > Hi all, > > > > >

Re: [Numpy-discussion] Value based promotion and user DTypes

On Wed, Jan 27, 2021 at 5:44 PM Sebastian Berg wrote: > On Wed, 2021-01-27 at 10:33 +0100, Ralf Gommers wrote: > > On Tue, Jan 26, 2021 at 10:21 PM Sebastian Berg < > > sebast...@sipsolutions.net> > > wrote: > > > > > Thanks for all the other co

Re: [Numpy-discussion] Math Inspector Beta

Hi Matt, Very cool, thanks for sharing! On Thu, Feb 4, 2021 at 12:19 AM Matt Calhoun wrote: > Hi Everyone! I have been using numpy for an extremely long time, but this > is the first time emailing the list. I recently released the beta version > of my free open source math app called math in

Re: [Numpy-discussion] ENH: Proposal to add atleast_nd function

On Fri, Feb 12, 2021 at 3:32 AM Juan Nunez-Iglesias wrote: > both napari and scikit-image use atleast_ a few times. I don’t have many > examples of where I used nd because it didn’t exist. But I have the very > distinct impression of needing it repeatedly. In some places, I’ve used > `np.broadcas

Re: [Numpy-discussion] ENH: Proposal to add atleast_nd function

On Fri, Feb 12, 2021 at 7:25 PM Sebastian Berg wrote: > On Fri, 2021-02-12 at 10:08 -0500, Robert Kern wrote: > > On Fri, Feb 12, 2021 at 9:45 AM Joseph Fox-Rabinovitz < > > jfoxrabinov...@gmail.com> wrote: > > > > > > > > > > > On Fri, Feb 12, 2021, 09:32 Robert Kern > > > wrote: > > > > > > >

Re: [Numpy-discussion] ENH: Proposal to add atleast_nd function

On Fri, Feb 12, 2021 at 9:21 PM Robert Kern wrote: > On Fri, Feb 12, 2021 at 1:47 PM Ralf Gommers > wrote: > >> >> On Fri, Feb 12, 2021 at 7:25 PM Sebastian Berg < >> sebast...@sipsolutions.net> wrote: >> >>> On Fri, 2021-02-12 at 10:08 -0500, Ro

Re: [Numpy-discussion] Type annotation for Numpy arrays, accelerators and numpy.typing

On Tue, Feb 16, 2021 at 10:20 AM PIERRE AUGIER < pierre.aug...@univ-grenoble-alpes.fr> wrote: > Hi, > > When Numpy 1.20 was released, I discovered numpy.typing and its > documentation https://numpy.org/doc/stable/reference/typing.html > > I know that it is very new but I'm a bit lost. A good API t

Re: [Numpy-discussion] What to do about structured string dtype and string regression?

On Wed, Feb 17, 2021 at 2:14 AM Stephan Hoyer wrote: > On Tue, Feb 16, 2021 at 3:13 PM Sebastian Berg > wrote: > >> Hi all, >> >> In https://github.com/numpy/numpy/issues/18407 it was reported that >> there is a regression for `np.array()` and friends in NumPy 1.20 for >> code such as: >> >>

Re: [Numpy-discussion] ENH: Proposal to add atleast_nd function

On Wed, Feb 17, 2021 at 12:26 AM Stefan van der Walt wrote: > On Tue, Feb 16, 2021, at 07:49, Joseph Fox-Rabinovitz wrote: > > I'm getting a generally lukewarm not negative response. Should we put it > to a vote? > > > Things here don't typically get decided by vote—I think you'll have to > build

Re: [Numpy-discussion] ENH: Proposal to add atleast_nd function

On Wed, Feb 17, 2021 at 9:26 PM Oscar Benjamin wrote: > On Wed, 17 Feb 2021 at 10:36, Ralf Gommers wrote: > > > > On Wed, Feb 17, 2021 at 12:26 AM Stefan van der Walt < > stef...@berkeley.edu> wrote: > >> > >> Ralf has been working towards this idea,

Re: [Numpy-discussion] Cleanup of the `np.lib` namespace (was: ENH: Proposal to add atleast_nd function)

On Fri, Feb 19, 2021 at 5:25 PM Sebastian Berg wrote: > On Thu, 2021-02-18 at 11:10 +0100, Ralf Gommers wrote: > > On Wed, Feb 17, 2021 at 9:26 PM Oscar Benjamin < > > > > > > > > > > It isn't, but it's relatively straightforward and can be d

[Numpy-discussion] NEP 48: Spending NumPy Project funds

of research on relevant policies and practices in other open source projects/communities. While we could find examples of practices, we did not find any published policies like this. If you know of any that are relevant, it'd be great if you could point to them. Cheers, Ralf :Author: Ralf Go

[Numpy-discussion] NEP: array API standard adoption (NEP 47)

Hi all, Here is a NEP, written together with Stephan Hoyer and Aaron Meurer, for discussion on adoption of the array API standard ( https://data-apis.github.io/array-api/latest/). This will add a new numpy.array_api submodule containing that standardized API. The main purpose of this API is to be

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

On Mon, Feb 22, 2021 at 1:44 PM Matti Picus wrote: > 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] NEP: array API standard adoption (NEP 47)

Thanks for the feedback Sebastian! On Mon, Feb 22, 2021 at 7:49 PM Sebastian Berg wrote: > On Sun, 2021-02-21 at 17:30 +0100, Ralf Gommers wrote: > > Hi all, > > > > Here is a NEP, written together with Stephan Hoyer and Aaron Meurer, > > for > > discus

Re: [Numpy-discussion] NEP: array API standard adoption (NEP 47)

On Mon, Feb 22, 2021 at 8:52 PM Sebastian Berg wrote: > On Mon, 2021-02-22 at 20:16 +0100, Ralf Gommers wrote: > > > > > > > > > It seems the current idea is to create a new NumPy array subclass. > > > That > > > sounds good, but I am a bit

Re: [Numpy-discussion] NEP 48: Spending NumPy Project funds

On Mon, Feb 22, 2021 at 9:34 PM Stephan Hoyer wrote: > On Mon, Feb 22, 2021 at 4:08 AM Pearu Peterson > wrote: > >> Hi, >> >> See GH discussion starting at >> https://github.com/numpy/numpy/pull/18454#discussion_r579967791 for the >> raised issue that is now moved here. >> >> Re "Compensating fa

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

On Tue, Feb 23, 2021 at 1:42 PM ChunLin Fang wrote: > Thanks for asking, this is a simple explanation for your questions: > 1. The download link of KML_BLAS: > The Chinese page is > https://www.huaweicloud.com/kunpeng/software/KML_BLAS.html > The English page is > https://kunpeng.huawei.com/en/#/

Re: [Numpy-discussion] NEP: array API standard adoption (NEP 47)

On Mon, Feb 22, 2021 at 7:49 PM Sebastian Berg wrote: > On Sun, 2021-02-21 at 17:30 +0100, Ralf Gommers wrote: > > Hi all, > > > > Here is a NEP, written together with Stephan Hoyer and Aaron Meurer, > > for > > discussion on adoption of the array API standard

Re: [Numpy-discussion] Guidelines for floating point comparison

On Wed, Feb 24, 2021 at 11:29 AM Bernard Knaepen wrote: > Hi all, > > We are developing a code that heavily relies on NumPy. Some of our > regression tests rely on floating point number comparisons and we are a bit > lost in determining how to choose atol and rtol (we are trying to do all > opera

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

Hi all, We now have a guide for downstream package authors, talking about API and ABI stability, NumPy versioning, testing against NumPy master, and how to add build time and runtime dependencies for numpy: https://numpy.org/devdocs/user/depending_on_numpy.html Especially the version constraints

Re: [Numpy-discussion] Development branches renamed

On Thu, Mar 4, 2021 at 8:09 AM Stefan van der Walt wrote: > Hi everyone, > > The development branches of most of the repositories on github.com/numpy > have been renamed to `main` (this is the GitHub default for newly created > repositories). The move has not yet been made for sub-projects such

Re: [Numpy-discussion] NEP: array API standard adoption (NEP 47)

On Wed, Mar 10, 2021 at 6:41 PM Sebastian Berg wrote: > Top Posting, to discuss post specific questions about NEP 47 and > partially the start on implementing it in: > > https://github.com/numpy/numpy/pull/18585 > > There are probably many more that will crop up. But for me, each of > these i

Re: [Numpy-discussion] NEP: array API standard adoption (NEP 47)

On Wed, Mar 10, 2021 at 11:41 PM Sebastian Berg wrote: > On Wed, 2021-03-10 at 13:44 -0700, Aaron Meurer wrote: > > On Wed, Mar 10, 2021 at 10:42 AM Sebastian Berg > > wrote: > > > > > > > 2. `np.result_type` special cases array-scalars (the current PR), > > > NEP > > > 47 promises it will not.

Re: [Numpy-discussion] Numpy 1.20.1 availability

On Sun, Mar 14, 2021 at 11:14 AM Peter Cock wrote: > I would recommend using the community run conda-forge as one of your > default conda channels. They have a very slick largely automated system > to update recipes when upstream makes a release. The default Anaconda > channel from Anaconda, Inc.

Re: [Numpy-discussion] NEP: array API standard adoption (NEP 47)

On Thu, Mar 11, 2021 at 6:08 PM Sebastian Berg wrote: > On Thu, 2021-03-11 at 12:37 +0100, Ralf Gommers wrote: > > On Wed, Mar 10, 2021 at 6:41 PM Sebastian Berg < > > sebast...@sipsolutions.net> > > wrote: > > > > > Top Posting, to discus

[Numpy-discussion] Japanese translation of numpy.org complete - proofreader help wanted

Hi all, We have our first complete translation of the numpy.org content, Japanese, thanks to Atsushi Sakai. It would be really helpful if someone else who speaks Japanese can proofread the translations. Then it's ready to deploy I think - we just need to enable the language switcher widget, the co

[Numpy-discussion] Steering Council membership updates

Hi all, On behalf of the NumPy Steering Council (SC) I have a number of membership changes to announce. We're excited to welcome Inessa Pawson and Melissa Mendonça as new SC members. Inessa has been contributing for close to two years, and has been a driving force behind the new website, the user

Re: [Numpy-discussion] Dot + add operation

On Wed, Mar 31, 2021 at 2:35 AM Guillaume Bethouart < guillaume.bethou...@eshard.com> wrote: > Is it possible to add a method to perform a dot product and add the result > to an existing matrix in a single operation ? > > Like C = dot_add(A, B, C) equivalent to C += A @ B.This behavior is > native

[Numpy-discussion] files for 3D printing of NumPy logo

Hi all, Andrej Krecker, who is a 3D printing engineer who likes NumPy, shared 3D printing files for the NumPy logo. It comes in two flavors, a really 3-D version, and a flatter (~0.5 cm thick) 2-D version. Check them out at https://www.thingiverse.com/thing:4821992. Cheers, Ralf _

Re: [Numpy-discussion] Is there a defined way to "unpad" an array, and if not, should there be?

On Tue, Apr 13, 2021 at 3:37 AM Jeff Gostick wrote: > It is great to hear that this might be useful. I would LOVE to create a > PR on this idea and contribute back to numpy...but let's not get ahead of > ourselves :-) > > Regarding the name, I kinda like "unpad" since it relates directly to > "p

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

On Tue, Apr 20, 2021 at 2:18 PM Matti Picus wrote: > 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: > Thanks Matti!

Re: [Numpy-discussion] Add pad_to_shape and pad_to_match for simpler padding if a target size is already known

On Thu, Apr 15, 2021 at 11:54 AM czorio4 wrote: > Hello all, > > I'm only two weeks late with this message about my pull request > that adds functions that > allow the user to pad to a target shape, instead of adding a certain amount > to each axis. >

Re: [Numpy-discussion] Add pad_to_shape and pad_to_match for simpler padding if a target size is already known

_to_match` > function, and instead have the user explicitly provide the other array's > shape: > > padded = np.pad_to(x, y.shape, ...) > Yes I agree, that's an even better idea. +1 for avoiding unions when the solution is as simple as using `.shape`. Cheers, Ralf >

Re: [Numpy-discussion] NumPy Tutorials

Thanks Melissa, Ryan, Olz, Ross, and everyone else who contributed! This site looks really nice, and the content is a big improvement on what we had before as tutorials! Cheers, Ralf On Thu, Apr 29, 2021 at 9:39 PM Melissa Mendonça wrote: > Hello, all! > > Recently, we added a link to NumPy Tu

Re: [Numpy-discussion] Google Season of Docs

On Fri, May 14, 2021 at 8:47 PM Stefan van der Walt wrote: > On Fri, May 14, 2021, at 11:41, Melissa Mendonça wrote: > > I am happy to announce we found our technical writer for the Google Season > of Docs program. After looking at all submitted proposals we have decided > to hire Mukulika. You c

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

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 > functions and open a PR: > > https://github.com/numpy/numpy/pull/19117 > > Any discussion ar

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

On Sun, May 30, 2021 at 10:01 AM Matti Picus wrote: > > > Did this function come up at all in the array-API consortium dicussions? > It happens to be in this list of functions which was made last week: https://github.com/data-apis/array-api/issues/187. That list is potential next candidates, bas

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

On Sun, May 30, 2021 at 10:41 AM 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

Re: [Numpy-discussion] RFC: supporting complex inputs in np.logaddexp

On Tue, Jun 1, 2021 at 3:18 PM Filippo Vicentini wrote: > Hello all, > > I would like to ask if the maintainers would be in favour of adding > support to np.logaddexp in order to support complex numbers. > scipy.special.logsumexp already does, and it would be relatively > straightforward to suppo

Re: [Numpy-discussion] Accepting NEP 35 `like=array_like` for use with `__array_function__`

On Mon, Jun 7, 2021 at 8:34 PM Sebastian Berg wrote: > Hi all, > > I have opened a PR (https://github.com/numpy/numpy/pull/19188) to > *finalize* NEP 35: > > > https://numpy.org/neps/nep-0035-array-creation-dispatch-with-array-function.html > > Which added `like=` keyword argument to `np.array`,

Re: [Numpy-discussion] Proposals for NumPy 1.22.0

On Wed, Jun 9, 2021 at 8:19 PM Charles R Harris wrote: > Hi All, > > Here are some proposals for the NumPy 1.22.0 release currently in > development. > > >1. Drop support for Python 3.7 (3.10 will be available). > > NEP 29 says December 2021, so that'd be kind of borderline. It would allow us

[Numpy-discussion] request to remove the numpy-aarch64 package from PyPI

Hi all, FYI, I noticed this package that claimed to be maintained by us: https://pypi.org/project/numpy-aarch64/. That's not ours, so I tried to contact the author (no email provided, but guessed the same username on GitHub) and asked to remove it: https://github.com/tomasriv/DNA_Sequence/issues/1

Re: [Numpy-discussion] 2020 NumPy survey results

On Tue, Jun 22, 2021 at 11:41 PM Inessa Pawson wrote: > Hi, everyone! > In 2020, the NumPy survey team in partnership with students and faculty > from a Master’s course in Survey Methodology jointly hosted by the > University of Michigan and the University of Maryland conducted the first > offici

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

On Thu, Jun 24, 2021 at 6:12 AM Gagandeep Singh wrote: > To me, adding enums as attributes of the `np.copy` function seems like a > pretty good idea. This trick might resolve the only relatively important > issue with Enums. Then, the benefits of Enum might outweigh the > disadvantage of uncommon

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

Let's see if we can finalize this. On Thu, Jun 24, 2021 at 9:23 PM Stefan van der Walt wrote: > On Thu, Jun 24, 2021, at 01:03, Ralf Gommers wrote: > > For this one, I'd say it kinda looks like we do need one, so then let's > just add one and be done with it

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

On Mon, Jul 5, 2021 at 3:53 AM Stefan van der Walt wrote: > On Sun, Jul 4, 2021, at 13:00, Ralf Gommers wrote: > > I don't think so. We basically arrived at the solution, and there's a PR > that is mostly done too. This really isn't that complicated tha

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

On Wed, Jul 7, 2021 at 9:56 PM Jerry Morrison < jerry.morrison+nu...@gmail.com> wrote: > Would someone please answer installation questions about NumPy's BLAS on > macOS? I'm not finding the answers in the release notes > , the PR >

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

On Thu, Jul 8, 2021 at 11:47 PM Jerry Morrison < jerry.morrison+nu...@gmail.com> wrote: > > On Wed, Jul 7, 2021 at 10:14 PM Matti Picus wrote: > >> >> 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

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

Hey all, This whole thread is quite interesting: https://twitter.com/zooba/status/1415440484181417998. Given how much effort we are spending on really niche wheel builds, I’m wondering if we should just draw a line somewhere: - we do what we do now for the main platforms: Windows, Linux (x86,

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

On Thu, Jul 15, 2021 at 2:41 PM Matti Picus wrote: > 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. ... > >

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

On Thu, Jul 15, 2021 at 3:45 PM Kevin Sheppard wrote: > When thinking about supporting a platform, it seems reasonable to consider > other sources for pre-compiled binaries, e.g., conda and especially > conda-forge. Conda-forge has > > > > linux-ppc64le v1.7.0 > > linux-64 v1.7.0 > > linux-aarc

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

On Thu, Jul 15, 2021 at 4:15 PM Charles R Harris wrote: > > > On Thu, Jul 15, 2021 at 8:02 AM Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> I spent so much time updating the wheels builds to 64 bit BLAS mostly >> because >> >> >>- I needed to actually understand how multibuild w

Re: [Numpy-discussion] Adding POWER10 (VSX4) support to the SIMD framework

On Wed, Jul 21, 2021 at 9:38 PM Nicholai Tukanov wrote: > I would like to understand how to go about extending the SIMD framework in > order to add support for POWER10. Specifically, I would like to add the > following instructions: `lxvp` and `stxvp` which loads/stores 256 bits > into/from two v

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

On Mon, Aug 2, 2021 at 7:04 PM Sebastian Berg 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 > return one (all NaNs were considered unique): > > a = np.array([1, 1, np.nan, np.nan,

Re: [Numpy-discussion] Dropping Python 3.7 for NumPy 1.22

On Fri, Aug 13, 2021 at 3:41 AM Charles R Harris wrote: > Hi All, > > This is to propose dropping Python 3.7 for NumPy 1.22. Doing so will allow > merging the array API standard > (keyword > only arguments), simplify removing import time compiles >

Re: [Numpy-discussion] OS X universal2 wheels

On Mon, Aug 16, 2021 at 6:47 PM Charles R Harris wrote: > Hi All, > > I note that the numpy universal wheels for Mac are marked "10_9" whereas > the wheels for Arm64 are marked '11_0'. Does that need to be fixed? > Arm64 hardware requires macOS >= 11.0 while Intel hardware works with 10.x and 11

Re: [Numpy-discussion] A bite of C++

On Thu, Aug 26, 2021 at 12:51 AM Sebastian Berg wrote: > On Wed, 2021-08-25 at 17:48 +0200, Serge Guelton wrote: > > > Potential follow-ups : > > > > - do we want to use -nostdlib, to be sure we don't bring any C++ > > runtime dep? > > What does this mean for compatibility? It sounds reasonable

Re: [Numpy-discussion] New Feature added to rotate MeshGrid

On Tue, Aug 31, 2021 at 12:07 PM Yash Tewatia wrote: > Hi, it is my first contribution to the open-source community, I have tried > to fix issue #19315, which is to add a new feature of rotating mesh grid in > NumPy. It would be great if I get improvements and suggestions for it. > Hi Yash, welc

[Numpy-discussion] no community meeting today

Hi all, Just a heads up that there's no community meeting later today. For next time, please feel free to add topics to https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both. Cheers, Ralf ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mai

Re: [Numpy-discussion] New CZI grant to support DEI initiatives in the scientific Python ecosystem

ence Lead positions to identify, document, > and implement practices to foster inclusive open-source communities. This > project will be led by Melissa Mendonça (NumPy), with additional mentorship > and guidance provided by Ralf Gommers (NumPy, SciPy), Hannah Aizenman and > Thomas Caswell (Mat

Re: [Numpy-discussion] np.trunc is inconsistent with array-api

On Sat, Sep 4, 2021 at 10:02 AM Kshitij Kalambarkar < kshitijkalambar...@gmail.com> wrote: > Hi, > > np.trunc returns floating dtype output even for integral dtype input. As > per array-api, it should preserve the input dtype. > Just a note that it's not compatibility with the array API standard

[Numpy-discussion] new searchable mailing list archives

Hi all, Thanks to the friendly folks who maintain the python.org mailing lists, we now have nice searchable mailing list archives for NumPy and SciPy: https://mail.python.org/archives/list/numpy-discussion@python.org/ https://mail.python.org/archives/list/scipy-...@python.org/ https://mail.python

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

On Wed, Sep 22, 2021 at 8:31 PM Sebastian Berg wrote: > Hi all, > > Melissa brought up that we should reschedule the bi-weekly community > meeting to the same time slot at the triage meeting: > > Wednesdays 16:00 UTC (9 am Pacific time) [1] > > This will simplify attending for those in Euro

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

On Tue, Sep 28, 2021 at 7:20 PM Sebastian Berg wrote: > On Wed, 2021-09-22 at 21:11 +0200, Ralf Gommers wrote: > > On Wed, Sep 22, 2021 at 8:31 PM Sebastian Berg < > > sebast...@sipsolutions.net> > > wrote: > > > > > Hi all, > > > > > >

[Numpy-discussion] Re: Running numpy.test() after pip install

On Tue, Sep 28, 2021 at 7:07 PM Kevin Sheppard wrote: > I think NumPy has always tried to have effectively no install dependencies > at least when installed from source (minimal install from git only requires > Cython). This seems like a good goal to me and there are scenarios where > extra pack

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

On Wed, Sep 29, 2021 at 9:32 AM Andras Deak wrote: > Hi All, > > Today both of the python.org mailing lists I'm subscribed to (numpy and > scipy-dev) got the same kind of link shortener spam. I assume all the > mailing lists started getting these, and that these won't go away for a > while. > I

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

On Wed, Sep 29, 2021 at 11:33 AM Andras Deak wrote: > On Wed, Sep 29, 2021 at 11:28 AM Andras Deak > wrote: > >> On Wed, Sep 29, 2021 at 11:15 AM Ralf Gommers >> wrote: >> >>> >>> >>> On Wed, Sep 29, 2021 at 9:32 AM Andras Deak &

[Numpy-discussion] Re: Running numpy.test() after pip install

Ralf > Aaron Meurer > > On Tue, Sep 28, 2021 at 11:33 AM Ralf Gommers > wrote: > > > > > > > > On Tue, Sep 28, 2021 at 7:07 PM Kevin Sheppard < > kevin.k.shepp...@gmail.com> wrote: > >> > >> I think NumPy has always tried to have e

[Numpy-discussion] Re: Running numpy.test() after pip install

On Wed, Sep 29, 2021 at 9:54 PM Robert Kern wrote: > On Wed, Sep 29, 2021 at 3:50 PM Ralf Gommers > wrote: > >> >> On Tue, Sep 28, 2021 at 10:39 PM Aaron Meurer wrote: >> >>> Could numpy include a variant (I'm not sure what setuptools calls >>>

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

On Wed, Sep 29, 2021 at 12:51 PM Ilhan Polat wrote: > I'd like to reheat the proposition that we enable discussion feature on > GitHub for the repos. Not only this makes things a bit more streamlined > (transfer nonbug reports to discussions to handle noise there) but also > makes it easier to co

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

On Wed, Sep 29, 2021 at 11:32 PM Stefan van der Walt wrote: > On Wed, Sep 29, 2021, at 13:58, Ralf Gommers wrote: > > This was discussed in the community meeting today. No one was really > enthusiastic, concerns that were brought up included the lack of an email > interface,

[Numpy-discussion] Re: numpy.math docs

On Sun, Oct 3, 2021 at 4:15 PM Mark Bakker wrote: > Dear List, > > I just found out that there is a numpy.math subpackage with a bunch of > extra mathematical functions (I needed the factorial function). I have been > googling for 10 minutes, but can not find any documentation on the > numpy.math

[Numpy-discussion] Re: Drop 32 bit manylinux wheels

On Mon, Oct 4, 2021 at 12:39 PM Matthew Brett wrote: > Hi, > > Dropping 32-bit wheels seems very reasonable at this stage, as long as > we keep testing on 32-bit, for the Raspberry Pi folks, > +1 for this plan. Testing in regular CI has value, and is less of a pain than building wheels. Cheers,

[Numpy-discussion] Re: Musllinux wheels

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 will allow easy installation in Alpine > Docker images. GitHub issue: https://github.com/numpy/numpy/issues/20089 Thanks for asking Laurie

[Numpy-discussion] Re: Musllinux wheels

On Mon, Oct 11, 2021 at 2:18 PM Andrew Nelson wrote: > > > > I'd say we may perhaps want to do this, but only if and when it becomes > much easier - for example once we have migrated all our wheel build infra > to GitHub Actions and cibuildwheel > > > I've been really impressed with cibuildwheel.

[Numpy-discussion] Re: Musllinux wheels

On Mon, Oct 11, 2021 at 2:10 PM Matti Picus wrote: > > On 11/10/21 2:22 pm, Ralf Gommers wrote: > > > > > > On Mon, Oct 11, 2021 at 9:52 AM Laurie O > <mailto:laurie_opper...@hotmail.com>> wrote: > > > > CI request: build PEP 656 &

[Numpy-discussion] Re: Musllinux wheels

On Mon, Oct 11, 2021 at 2:55 PM Ralf Gommers wrote: > > > On Mon, Oct 11, 2021 at 2:18 PM Andrew Nelson wrote: > >> >> >> > I'd say we may perhaps want to do this, but only if and when it becomes >> much easier - for example once we have migrated al

[Numpy-discussion] Re: What happened to the numpy.random documentation?

On Thu, Oct 14, 2021 at 7:19 PM Kevin Sheppard wrote: > I think the issue in random specifically is that a raw list of > available functions does not provide suitable guidance for someone looking > for random variate generating function. This is because the module-level > API is mostly dominated

[Numpy-discussion] Re: What happened to the numpy.random documentation?

On Fri, Oct 15, 2021 at 12:11 PM Kevin Sheppard wrote: > > > On Thu, Oct 14, 2021 at 7:22 PM Ralf Gommers > wrote: > >> >> >> On Thu, Oct 14, 2021 at 7:19 PM Kevin Sheppard < >> kevin.k.shepp...@gmail.com> wrote: >> >>> I

[Numpy-discussion] Re: Consistency of random number functions APIs.

On Sat, Oct 30, 2021 at 9:44 PM Todd Anderson wrote: > Some NumPy random number generation functions take a dtype parameter > whereas others don't. Some of them take an out parameter whereas others > don't. Just glancing at it, there seems to be no rhyme or reason why this > would be the case b

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

On Tue, Nov 2, 2021 at 1:54 PM Niyas Sait wrote: > Hello, > > Numpy v1.21.2 added > support for windows/arm64 platforms but we still don't have any systems in > place to produce binary wheels or test win/arm64 packages. I think it will > be go

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

On Tue, Nov 2, 2021 at 3:15 PM Peter Cock wrote: > > > On Tue, Nov 2, 2021 at 1:07 PM Ralf Gommers > wrote: > > > > Our current wheel build machinery is at > https://github.com/MacPython/numpy-wheels/, > > but please ignore that. We just merged a PR which uses

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

On Mon, Aug 2, 2021 at 7:49 PM Ralf Gommers wrote: > > > On Mon, Aug 2, 2021 at 7:04 PM Sebastian Berg > wrote: > >> Hi all, >> >> In NumPy 1.21, the output of `np.unique` changed in the presence of >> multiple NaNs. Previously, all NaNs were returned w

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

On Sat, Nov 6, 2021 at 1:18 PM Noah Goldstein wrote: > On Fri, Nov 5, 2021 at 1:38 PM Devulapalli, Raghuveer > wrote: > > > > They are meant to be optimized. Any contribution to improve them further > is more than welcome. > > Fantastic. I don't see any tests for any of the functions in there. >

[Numpy-discussion] Re: Deprecate np.MachAr?

On Tue, Oct 26, 2021 at 9:20 PM bas van beek wrote: > Hi all, > > > > The subject of `MachAr` recently came up in > https://github.com/numpy/numpy/pull/20132 and > > an earlier community meeting, more notably: it’s questionably role as > public (and even private?) API. > > > > Ever since the intr

[Numpy-discussion] Re: Code formatters

On Sun, Nov 14, 2021 at 6:14 PM Charles R Harris wrote: > Hi All, > > This post is for discussing the automatic code formatters for C/C++/*.py > that are now available. The current options, as I see them, are > clang-format (C/C++) and black (*.py, *.pyi, etc). Neither is perfect to my > eye, but

[Numpy-discussion] Re: win32 wheels for Python 3.10

On Wed, Nov 10, 2021 at 2:36 PM Aivar Annamaa wrote: > Has it been decided to stop publishing win32 wheels for Python 3.10? Numpy > 1.21.4 currently misses win32 wheel for Python 3.10 on PyPI. Is this > temporary? > > I'm confused, because > https://www.mail-archive.com/numpy-discussion@python.or

<    1   2   3   4   5   6   7   8   >