Re: [Numpy-discussion] numpy/windows-wheel-builder repository

On Tue, Dec 3, 2019 at 11:33 AM Warren Weckesser wrote: > It looks like the repo https://github.com/numpy/windows-wheel-builder > is defunct. Could someone with the appropriate access privileges > merge Matti's pull request to update README.rst > (https://github.com/numpy/windows-wheel-builder/p

Re: [Numpy-discussion] numpy/windows-wheel-builder repository

On Tue, Dec 3, 2019 at 5:49 PM Brigitta Sipocz wrote: > Hi, > > You could consider archiving the repository (bottom at the Settings > page for folks with admin access), too. That makes it ever more > visible that it's no longer maintained or in fact to be used. > Good idea, thanks Brigitta. Done

Re: [Numpy-discussion] BIDS-NumPy progress reports, 2018/2019

On Fri, Dec 20, 2019 at 2:12 AM Stefan van der Walt wrote: > Dear colleagues, > > I'd like to thank everyone who contributed to NumPy over the past year. > NumPy is a complex undertaking that requires inputs from many spheres to > progress. Your contribution, however big or small, is important,

Re: [Numpy-discussion] Cleaning up Python 2.7 code.

On Fri, Jan 3, 2020 at 1:01 AM Sebastian Berg wrote: > On Thu, 2020-01-02 at 16:51 -0700, Charles R Harris wrote: > > Hi All, > > > > Just want to propose cleaning up the Python 2.7 compatibility code > > for NumPy 1.19. Any objections? > > > > Not from me, sounds like a good plan, lets get it ov

Re: [Numpy-discussion] Deprecate numpy.dual?

On Fri, Jan 3, 2020 at 5:54 PM Warren Weckesser wrote: > On 1/3/20, Sebastian Berg wrote: > > On Fri, 2020-01-03 at 07:11 -0500, Warren Weckesser wrote: > >> In response to some work on improving the documentation of > >> `numpy.linalg` and how it compares to `scipy.linalg`, Kevin Sheppard > >>

Re: [Numpy-discussion] Is the build-system section of pyproject.toml a maintained list of the build dependencies?

On Wed, Jan 8, 2020 at 6:04 PM Warren Weckesser wrote: > On 1/8/20, Kevin Sheppard wrote: > > With recent versions of pip it will read the pyproject.toml file to get > the > > dependencies, and then install these in an isolated environment to build > > the wheel, and then install the wheel. The

[Numpy-discussion] Fwd: [NumFOCUS Projects] Job: Open Source Developer Advocate

-- Forwarded message - From: Nicole Foster Date: Wed, Jan 8, 2020 at 10:25 PM Subject: [NumFOCUS Projects] Job: Open Source Developer Advocate To: Fiscally Sponsored Project Representatives , Affiliated Projects Hi Everyone, We recently posted an ad for an Open Source Developer

Re: [Numpy-discussion] 8 Real Distributions

On Fri, Jan 17, 2020 at 3:46 AM Michael Lance wrote: > TLDR; > I think this could be a useful contribution to NumPy, but I want to get > feedback on where it should go (either in NumPy or elsewhere). > I have functions using numpy.random which invoke the 8 "Real" data sets as > estimated by Ted M

[Numpy-discussion] new absolute beginners tutorial merged

Hi all, I think this is worth announcing: we have a new tutorial in the user guide titled "NumPy: the absolute basics for beginners". This was Anne Bonner's Season of Docs project, and it is a big step in the right direction for making are docs more accessible to new users. Up at https://numpy.or

Re: [Numpy-discussion] new absolute beginners tutorial merged

day!!! Thank you! > > > ~Anne > > > On Tue, Jan 21, 2020 at 2:20 PM alexander baker < > baker.alexan...@gmail.com> > > wrote: > > > This looks really helpful, thanks to all those whom took the time to > write. > > Alex b. > > >

[Numpy-discussion] what to clean up, what to leave as is

Hi all, It's great to see that people are jumping at the chance to clean up Python 2 support. I would however caution about overdoing it on other cleanups. As a reminder, we normally do not want pure style PRs (e.g. PEP8 cleanups), because they make the code history (git blame, commits on particul

Re: [Numpy-discussion] NEP 37: A dispatch protocol for NumPy-like modules

On Wed, Feb 5, 2020 at 10:01 AM Andreas Mueller wrote: > A bit late to the NEP 37 party. > I just wanted to say that at least from my perspective it seems a great > solution that will help sklearn move towards more flexible compute engines. > I think one of the biggest issues is array creation (i

Re: [Numpy-discussion] NEP 37: A dispatch protocol for NumPy-like modules

atible again. Ralf > On Wed, 5 Feb 2020 at 17:38, Ralf Gommers wrote: > >> >> >> On Wed, Feb 5, 2020 at 10:01 AM Andreas Mueller wrote: >> >>> A bit late to the NEP 37 party. >>> I just wanted to say that at least from my perspective it seems a g

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

On Tue, Feb 4, 2020 at 2:00 PM Hameer Abbasi wrote: > —snip— > > > 1) Once NumPy adds the framework and initial set of Universal Intrinsic, > if contributors want to leverage a new architecture specific SIMD > instruction, will they be expected to add software implementation of this > instruction

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

t easy to figure out) making that platform fall back to the generic non-SIMD version of the ufunc. Cheers, Ralf > > > *From:* NumPy-Discussion intel@python.org> *On Behalf Of *Ralf Gommers > *Sent:* Monday, February 10, 2020 9:17 PM > *To:* Discussion of Numerical Python &g

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

On Wed, Feb 12, 2020 at 1:37 PM Devulapalli, Raghuveer < raghuveer.devulapa...@intel.com> wrote: > >> I hope there will not be a demand to use many non-universal intrinsics > in ufuncs, we will need to work this out on a case-by-case basis in each > ufunc. Does that sound reasonable? Are there int

Re: [Numpy-discussion] NEP 37: A dispatch protocol for NumPy-like modules

On Sun, Feb 23, 2020 at 3:31 PM Stephan Hoyer wrote: > On Thu, Feb 6, 2020 at 12:20 PM Sebastian Berg > wrote: > >> >> Another thing about backward compatibility: What is our vision there >> actually? >> This NEP will *not* give the *end user* the option to opt-in! Here, >> opt-in is really rese

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

On Thu, Mar 12, 2020 at 7:14 AM David Cournapeau wrote: > Hi chuck, > > > > Le jeu. 12 mars 2020 à 13:17, Charles R Harris > a écrit : > >> >> Hi David, >> >> On Wed, Mar 11, 2020 at 8:43 PM David Cournapeau >> wrote: >> >>> Hi there, >>> >>> My current employer is organizing regular "hack week

Re: [Numpy-discussion] Documentation Team Meetings - all are welcome!

On Thu, Mar 12, 2020 at 8:21 PM Melissa Mendonça wrote: > Hello all, > > As part of NumPy's recent focus on documentation writing and improvement > (see NEP 44), we are proposing a regular meeting for the Documentation Team > to discuss possible content, ideas and general planning. A small group

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

On Tue, Mar 17, 2020 at 12:46 PM David Cournapeau wrote: > > > On Thu, Mar 12, 2020 at 3:41 PM Matti Picus wrote: > >> >> 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

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

additional methods related > > to the > > GPU rather than as a mechanism to define new datatypes. > > A class hierarchy does provides value, this may be achieved by > > allowing the creation of *abstract* datatypes. > > An

Re: [Numpy-discussion] Put type annotations in NumPy proper?

On Tue, Mar 24, 2020 at 11:43 PM Joshua Wilson wrote: > > That is, is this an all-or-nothing thing where as soon as we start, > numpy-stubs becomes unusable? > > Until NumPy is made PEP 561 compatible by adding a `py.typed` file, > type checkers will ignore the types in the repo, so in theory you

Re: [Numpy-discussion] Deprecating ndarray.tostring()

On Mon, Mar 30, 2020 at 1:09 PM Eric Wieser wrote: > Hi all, > > Just a heads up that in https://github.com/numpy/numpy/pull/15867 I plan > to deprecate ndarray.tostring(), which is just a confusing way to spell > ndarray.tobytes(). > > This function has been documented as a compatibility alias s

Re: [Numpy-discussion] Is `numpy.lib.shape_base.normalize_axis_index` considered part of the public API?

On Mon, Apr 6, 2020 at 3:31 PM Eric Wieser wrote: > When I added this function, it was always my intent for it to be consumed > by downstream packages, but as Sebastian remarks, it wasn't really > desirable to put it in the top-level namespace. > This is a nice function indeed, +1 for making it

Re: [Numpy-discussion] NEP 37: A dispatch protocol for NumPy-like modules

On Wed, Mar 4, 2020 at 1:22 AM Sebastian Berg wrote: > On Sun, 2020-02-23 at 22:44 -0800, Stephan Hoyer wrote: > > On Sun, Feb 23, 2020 at 3:59 PM Ralf Gommers > > wrote: > > > > > > On Sun, Feb 23, 2020 at 3:31 PM Stephan Hoyer > > > wrote: > &g

Re: [Numpy-discussion] NEP 37: A dispatch protocol for NumPy-like modules

uck with any decisions in a released NumPy version. Also makes switching on/off very easy for users, just (don't) `pip install numpy-array-module`. Cheers, Ralf > Cheers, > > Sebastian > > > > Cheers, > > Andy > > > > On 3/3/20 6:34 PM, Sebastian Be

Re: [Numpy-discussion] NEP 37: A dispatch protocol for NumPy-like modules

On Thu, Apr 9, 2020 at 6:54 PM Sebastian Berg wrote: > On Thu, 2020-04-09 at 13:52 +0200, Ralf Gommers wrote: > > On Wed, Mar 4, 2020 at 1:22 AM Sebastian Berg < > > sebast...@sipsolutions.net> > > wrote: > > > > The NumPy version should normally be

Re: [Numpy-discussion] NEP 37: A dispatch protocol for NumPy-like modules

On Fri, Apr 10, 2020 at 5:17 AM Sebastian Berg wrote: > On Thu, 2020-04-09 at 13:52 +0200, Ralf Gommers wrote: > > On Thu, Apr 9, 2020 at 12:02 AM Sebastian Berg < > > sebast...@sipsolutions.net> > > wrote: > > > > > > > > > > I think

Re: [Numpy-discussion] NEP 37: A dispatch protocol for NumPy-like modules

On Fri, Apr 10, 2020 at 3:03 PM Sebastian Berg wrote: > On Fri, 2020-04-10 at 12:27 +0200, Ralf Gommers wrote: > > > 3. I added features to allow transitioning:: > > > > > > get_array_module(*arrays, modules="numpy", > > > futu

Re: [Numpy-discussion] NEP 37: A dispatch protocol for NumPy-like modules

On Fri, Apr 10, 2020 at 7:18 PM Sebastian Berg wrote: > On Fri, 2020-04-10 at 18:19 +0200, Ralf Gommers wrote: > > On Fri, Apr 10, 2020 at 3:03 PM Sebastian Berg < > > sebast...@sipsolutions.net> > > wrote: > > > > > On Fri, 2020-04-10 at 12:27 +0200

Re: [Numpy-discussion] Using scalar constructors to produce arrays

On Sun, Apr 19, 2020 at 8:47 PM Joshua Wilson wrote: > Over in the NumPy stubs there's an issue > > https://github.com/numpy/numpy-stubs/issues/41 > > which points out that you can in fact do something like > > ``` > np.float32([1.0, 0.0, 0.0]) > ``` > > to construct an ndarray of float32. It see

Re: [Numpy-discussion] Proposal: add `force=` or `copy=` kwarg to `__array__` interface

On Fri, Apr 24, 2020 at 12:35 PM Eric Wieser wrote: > Perhaps worth mentioning that we've discussed this sort of API before, in > https://github.com/numpy/numpy/pull/11897. > > Under that proposal, the api would be something like: > > * `copy=True` - always copy, like it is today > * `copy=False`

Re: [Numpy-discussion] Google Season of Docs Ideas

On Mon, Apr 20, 2020 at 7:16 PM Melissa Mendonça wrote: > Hello all, > > As some of you may know, we are aiming to participate in the Google Season > of Docs program [1] again this year. The deadline for applications from > open source organizations is May 4, so I've started on a proposal (heavil

Re: [Numpy-discussion] Proposal: add `force=` or `copy=` kwarg to `__array__` interface

On Mon, Apr 27, 2020 at 12:10 AM Sebastian Berg wrote: > On Sat, 2020-04-25 at 10:52 -0700, Stephan Hoyer wrote: > > On Sat, Apr 25, 2020 at 10:40 AM Ralf Gommers > > > > wrote: > > > > > > > > On Fri, Apr 24, 2020 at 12:35 PM Eric Wieser <

Re: [Numpy-discussion] Proposal: add `force=` or `copy=` kwarg to `__array__` interface

On Tue, Apr 28, 2020 at 5:03 PM Sebastian Berg wrote: > On Tue, 2020-04-28 at 11:51 +0200, Ralf Gommers wrote: > > > > So arguably, there is no type-safety concern due to `.detach()`. > > > > I'm not sure what the question is here; no one mentioned type-safety.

Re: [Numpy-discussion] Proposal: add `force=` or `copy=` kwarg to `__array__` interface

On Wed, Apr 29, 2020 at 12:27 PM Juan Nunez-Iglesias wrote: > > > Ralf, you said you don't want warnings — even for sparse arrays? That was > an area of concern for you on the PyTorch discussion side. > Providing a boolean keyword argument and then raising a warning every time anyone uses that k

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

On Fri, May 1, 2020 at 5:53 PM Tina Oberoi wrote: > Hi all, > > I observed that there are many good-first-issues that are resolved but yet > open. It would be a great help for new contributors if we could close them > and label new good-first-issues (if not labelled already). > Hi Tina, thanks f

Re: [Numpy-discussion] Update the Code of Conduct Committee Membership (new members wanted)

happy to serve on our CoC committee please > let me or e.g. Ralf Gommers know, join the next community meeting > (April 29th, 11:00PDT/18:00UTC), or reply on the list. > > I hope we will be able to discuss and reach a consensus between those > interested and involved quickly (possibly

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

On Mon, May 4, 2020 at 8:40 AM Matti Picus wrote: > > 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

Re: [Numpy-discussion] Update the Code of Conduct Committee Membership (new members wanted)

On Sat, May 2, 2020 at 10:23 PM Warren Weckesser wrote: > On 5/2/20, Ralf Gommers wrote: > > On Thu, Apr 23, 2020 at 11:38 PM Sebastian Berg > > > > wrote: > > > >> Hi all, > >> > >> it has come up in the last community call that man

Re: [Numpy-discussion] Application Pre-requisites

On Wed, May 13, 2020 at 7:24 PM Hmrishav Bandyopadhyay < hmrishavbandyopadh...@gmail.com> wrote: > Hi, > I'm sorry but i can't join the Google group--it says an invite is needed :( > Hi Hmrishav, Melissa, it's not a group you can join, it's just a mailing list where you can interact directly with

Re: [Numpy-discussion] Call for Reviewers

On Fri, May 22, 2020 at 3:41 AM ChunLin Fang wrote: > Hi all, > > I've reviewed and submitted several Numpy PRs before, Glad to have the > right to add tags.my github id is Qiyu8 . > Hi ChunLin, thanks for your help! I've sent you an invite to the triage team. Best, Ra

Re: [Numpy-discussion] new numpy.org is live

; redesigned numpy.org. To transform the website into a comprehensive, yet > user-centric, resource of all things NumPy was a primary focus of this > months-long effort. We thank Joe LaChance, Ralf Gommers, Shaloo Shalini, > Shekhar Prasad Rajak, Ross Barnowski, and Mars Lee for their exten

Re: [Numpy-discussion] new numpy.org is live

On Sun, May 24, 2020 at 8:19 PM Stephen Waterbury wrote: > This is an absolutely beautiful and very informative site! > It is clear all the work and thought that went into it. > > So please take the following input as a constructive suggestion > from an outsider -- I am a long-time (30-year) Pyth

Re: [Numpy-discussion] Is it OK to extend the ndarray structure?

On Fri, May 22, 2020 at 10:14 PM Sebastian Berg wrote: > Hi all, > > just curious, has anyone reservations about extending the ndarray > struct (and the void scalar one)? > > The reason is that, I am starting to dislike the way we handle the > buffer interface. > Due to issues with backward compa

Re: [Numpy-discussion] (no subject)

On Tue, Jun 2, 2020 at 7:14 AM Sandro Tosi wrote: > hey! > > On Sun, May 31, 2020 at 7:52 PM Charles R Harris > wrote: > > Downstream developers should use Cython >= 0.29.16 for Python 3.8 > support and OpenBLAS >= 3.7 to avoid wrong results on the Skylake > architecture. The NumPy Wheels for th

Re: [Numpy-discussion] introducing autoreg and autoregnn

On Fri, Jun 5, 2020 at 9:48 PM rondall jones wrote: > Hello! I have supported constrained solvers for linear matrix problems for > about 10 years in C++, but have now switched to Python. I am going to > submit a couple of new routines for linalg called autoreg(A,b) and > autoregnn(A,b). They work

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

On Sat, Jun 6, 2020 at 2:58 PM Adrin wrote: > This somehow also reminds me of the `__array_module__` (NEP37) protocol. > > I'm not sure if TF would ever implement it, but it would be really nice if > the NEP37 proposal > would move forward and libraries would implement it. > There is a plan to m

Re: [Numpy-discussion] Numpy Documentation: How-to content

On Mon, Jun 1, 2020 at 8:18 PM Ryan C. Cooper wrote: > > This sounds fantastic. > > Great! > > > In what context would the students be creating the notebooks -- as > > part of one of your existing ME courses, as a for-credit project, as a > > supervised but non-credit project? > > These would be

[Numpy-discussion] NumPy team update

Hi all, The NumPy team is growing, and it's awesome to see everything that is going on. Hard to keep up with, but that's a good thing! I think it's a good time for an update on people who gained commit rights, or joined one of the teams we now have. For those who haven't seen it yet, we have a te

Re: [Numpy-discussion] new NumPy logo design - cast your vote!

On Thu, Jun 25, 2020 at 2:27 AM Inessa Pawson wrote: > One of the most discussed and commented issues in the recent history of > NumPy is about to be closed. Don’t forget to cast your vote via reaction on > the new NumPy logo design by this Friday, June 26th. > Thanks Inessa! Here are the three

Re: [Numpy-discussion] Proposal to add clause to license prohibiting use by oil and gas extraction companies

On Thu, Jul 2, 2020 at 10:58 AM Juan Nunez-Iglesias wrote: > Hi everyone, > > If you live in Australia, this has been a rough year to think about > climate change. After the hottest and driest year on record, over 20% of > the forest surface area of the south east was burned in the bushfires. > A

Re: [Numpy-discussion] GSoD application technical limitations

On Tue, Jul 7, 2020 at 9:07 AM Saber Tooth wrote: > Hello Melissa , > > Today I was writing my GSoD proposal application , while I tried to copy / > paste my exact Google docs proposal in the application description , but > even after clearing all the formatting , the application form is stating

[Numpy-discussion] participating in AI Code-In?

Hi all, We got an invitation to participate in AI Code-In ( https://aicode-in.github.io/AICode-In/). It's a new initiative, seems a bit GSoC like, but created by and for middle/high schoolers. We'd have to create tasks to work on (more like tagging/creation actionable issues than a full project),

Re: [Numpy-discussion] a summary function to get a quick glimpse on the contents of a numpy array

On Fri, Jul 31, 2020 at 1:40 PM Peter Steinbach wrote: > Dear numpy devs and interested readers, > > as a day-to-day user, it occurred to me that having a quick look into the > contents and extents of arrays is well doable with > numpy. numpy offers a rich set of methods for this. However, very o

Re: [Numpy-discussion] Add Chebyshev (cosine) transforms implemented via FFTs

On Tue, Aug 4, 2020 at 1:49 AM Chris Vavaliaris wrote: > PR #16999: https://github.com/numpy/numpy/pull/16999 > > Hello all, > this PR adds the two 1D Chebyshev transform functions `chebyfft` and > `ichebyfft` into the `numpy.fft` module, utilizing the real FFTs `rfft` and > `irfft`, respectively

Re: [Numpy-discussion] Building Numpy Documentation

On Wed, Aug 5, 2020 at 7:58 PM cooperrc wrote: > I'm trying to build NumPy and its documentation from the current git repo, > but I'm hitting a snag. I keep getting a RuntimeError: > > > I'm trying to build NumPy inside the cloned repository from my fork. I'm > running Arch (kernel 5.7.12) with g

Re: [Numpy-discussion] Add Chebyshev (cosine) transforms implemented via FFTs

On Wed, Aug 5, 2020 at 8:16 PM Ben Nathanson wrote: > > scipy.fft is a superset of numpy.fft, and the functionality included in > NumPy is really only the basics that are needed in many fields. > > Exactly this sentence might be useful on top of the FFT page. > > Is the right page reference/routi

Re: [Numpy-discussion] Replacement for Rackspace

On Fri, Aug 7, 2020 at 2:00 PM Kevin Sheppard wrote: > The Rackspace hosted wheel endpoints at > > > > > https://7933911d6844c6c53a7d-47bd50c35cd79bd838daf386af554a83.ssl.cf2.rackcdn.com/ > > > > and > > > > > https://3f23b170c54c2533c070-1c8a9b3114517dc5fe17b7c3f8c63a43.ssl.cf2.rackcdn.com/ > >

Re: [Numpy-discussion] Experimental `like=` attribute for array creation functions

On Mon, Aug 10, 2020 at 8:37 PM Sebastian Berg wrote: > On Mon, 2020-08-10 at 17:35 +0200, Hameer Abbasi wrote: > > Hi, > > > > We should have a higher-bandwidth meeting/communication for all > > stakeholders, and particularly some library authors, to see what > > would be good for them. > I'm n

Re: [Numpy-discussion] Experimental `like=` attribute for array creation functions

Thanks for raising these concerns Ilhan and Juan, and for answering Peter. Let me give my perspective as well. To start with, this is not specifically about Peter's NEP and PR. NEP 35 simply follows the pattern set by previous PRs, and given its tight scope is less difficult to understand than oth

Re: [Numpy-discussion] Experimental `like=` attribute for array creation functions

uck's explicit OK for > that. > > I don't quite understand this either, why would that leave master in > an unreleasable state? > That's what Sebastian proposed yesterday: let's merge right now, open issues for all the things being brought up right now, and deal wi

Re: [Numpy-discussion] Experimental `like=` attribute for array creation functions

t; happened the end result was better — I hope the same is true here! And yes, >> I’ll reiterate Ralf’s point: my concerns are about the NEP process itself >> rather than this one. I’ll summarise my proposal: >> >> - strict NEP template. NEPs with missing sections will not

Re: [Numpy-discussion] NEP Procedure Discussion

On Fri, Aug 14, 2020 at 1:36 PM Ilhan Polat wrote: > Also, not to be a complete slacker, I'd like to add to this list; > > - How can I help as an external lib maintainer? > - Do you even want us to get involved before the final draft? Or wait > until internal discussion finishes? > Yes, before.

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

Hi all, I'd like to share this announcement blog post about the creation of a consortium for array and dataframe API standardization here: https://data-apis.org/blog/announcing_the_consortium/. It's still in the beginning stages, but starting to take shape. We have participation from one or more m

Re: [Numpy-discussion] Dropping manylinux1 wheels for NumPy 1.20.

On Fri, Aug 28, 2020 at 3:38 PM Matthew Brett wrote: > Hi, > > On Thu, Aug 27, 2020 at 10:51 PM Charles R Harris > wrote: > > > > Hi All, > > > > The 32 bit manylinux1 wheels are proving problematic, see > https://github.com/numpy/numpy/issues/17174. One proposed solution is to > only release ma

Re: [Numpy-discussion] Dropping manylinux1 wheels for NumPy 1.20.

On Fri, Aug 28, 2020 at 5:01 PM Matthew Brett wrote: > Hi, > > Updated for Numpy wheels only - BigQuery [1], Notebook [2]. > > 41% of 32-bit wheels need manylinux1, 30% of 64-bit wheels. > Thanks for doing the analysis, very useful data. > Ralf - agreed we shouldn't wait too long for old pip -

[Numpy-discussion] setuptools/distutils merger & numpy.distutils

Hi all, I spent some time looking at the fallout of the setuptools 50.0 release. There's quite a few small issues, those can/should all be worked around by pinning setuptools to a lower version. The root cause and main longer-term issue is that numpy.distutils extends and monkeypatches distutils,

Re: [Numpy-discussion] setuptools/distutils merger & numpy.distutils

ar. Cheers, Ralf [1] https://discuss.python.org/t/pep-632-deprecate-distutils-module/5134 On Wed, Sep 2, 2020 at 11:33 AM Ralf Gommers wrote: > Hi all, > > I spent some time looking at the fallout of the setuptools 50.0 release. > There's quite a few small issues, those can/should all be wor

Re: [Numpy-discussion] setuptools/distutils merger & numpy.distutils

orward. > > David > > On Sat, Sep 5, 2020 at 8:13 PM Ralf Gommers > wrote: > >> Hi all, >> >> Preliminary conclusion: let's pin all packages to setuptools < 50.0 and >> wait for 6-9 months till the dust settles. Things may still change; the >> r

Re: [Numpy-discussion] setuptools/distutils merger & numpy.distutils

On Sun, Sep 6, 2020 at 9:50 AM Daniele Nicolodi wrote: > On 06/09/2020 07:06, David Cournapeau wrote: > > Assuming the numpy.distutils codebase has not changed much in the last > > 10 years, my sense is that a lot of the features that relied on monkey > > patching can be merged upstream, fortran

[Numpy-discussion] the NumPy paper is out!

Hi all, Nature published our first official paper: https://www.nature.com/articles/s41586-020-2649-2 And here is the Twitter announcement: https://twitter.com/numpy_team/status/1306268442450972674 Thanks to everyone who contributed to this milestone! A few special mentions: Chuck, for many year

Re: [Numpy-discussion] Einops cross-linking from einsum

On Sun, Sep 27, 2020 at 7:09 AM Stephan Hoyer wrote: > On Sat, Sep 26, 2020 at 10:53 PM Alex Rogozhnikov < > alex.rogozhni...@yandex.ru> wrote: > >> Hello all, >> >> I'm developer of einops - python package for readable and reliable tensor >> operations. >> Einops handles different types of tenso

[Numpy-discussion] NumPy community town hall on Oct 14th

Hi all, Tomorrow there will be no regular community meeting. Instead, we will be holding a town hall meeting at 1pm PDT (20:00 UTC), focused on community building, our diversity, equity & inclusion (DEI) efforts, ways for new contributors to plug in, and related topics. For details see https://num

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

On Sun, Oct 25, 2020 at 1:20 PM Kevin Sheppard wrote: > NumPy could take an explicit runtime dependency on numpy-distutils so that > the code would be technically in a different repo bit would always be > available through NumPy. Eventually this could be removed as a runtime > dependency. > I pu

Re: [Numpy-discussion] NumPy 1.20.x branch in two weeks

On Thu, Oct 29, 2020 at 2:25 PM Charles R Harris wrote: > Hi All, > > Time to start planning for the 1.20.x branch. These are my thoughts at the > moment: > >- Keep support for Python 3.6. Python 3.7 came out in June 2018, which >seems too recent to be our oldest supported version. >-

Re: [Numpy-discussion] NumPy 1.20.x branch in two weeks

On Mon, Nov 2, 2020 at 7:47 AM Stephan Hoyer wrote: > On Sun, Nov 1, 2020 at 7:47 PM Stefan van der Walt > wrote: > >> On Sun, Nov 1, 2020, at 18:54, Jarrod Millman wrote: >> > I also misunderstood the purpose of the NEP. I assumed it was >> > intended to encourage projects to drop old versions

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

On Tue, Nov 3, 2020 at 3:54 PM Matti Picus wrote: > 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_ReplaceLoopBySig

Re: [Numpy-discussion] Add sliding_window_view method to numpy

On Thu, Nov 5, 2020 at 4:56 PM Sebastian Berg wrote: > Hi all, > > just a brief note that I merged this proposal: > > https://github.com/numpy/numpy/pull/17394 > > adding `np.sliding_window_view` into the 1.20 release of NumPy. > > There was only one public API change, and that is that the `s

Re: [Numpy-discussion] Add sliding_window_view method to numpy

y/pull/17394#discussion_r498724340 > > On 06/11/2020 01:39, Sebastian Berg wrote: > > On Thu, 2020-11-05 at 17:35 -0600, Sebastian Berg wrote: > >> On Thu, 2020-11-05 at 12:51 -0800, Stephan Hoyer wrote: > >>> On Thu, Nov 5, 2020 at 11:16 AM Ralf Gommers < >

Re: [Numpy-discussion] Python 3.6 has been dropped from NumPy 1.20

On Tue, Nov 10, 2020 at 1:18 AM Charles R Harris wrote: > Hi All, > > The subject says it all: Python 3.6 has been dropped for the NumPy 1.20 > release. > That's great, thanks! Cheers, Ralf ___ NumPy-Discussion mailing list NumPy-Discussion@python.org

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

cussion now would be useful though, since it's easier to make changes now rather than when that API standard is already further along. Cheers, Ralf On Mon, Aug 17, 2020 at 9:34 PM Ralf Gommers wrote: > Hi all, > > I'd like to share this announcement blog post about the c

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

Cheers, Ralf > On Tue, Nov 10, 2020 at 7:21 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/blo

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

mPy. Cheers, Ralf > Thanks with best regards, > Compl > > > On 2020-11-11, at 02:19, 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://d

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

On Thu, Nov 12, 2020 at 1:54 PM Matti Picus wrote: > > 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: > > &g

[Numpy-discussion] Fwd: [NumFOCUS Projects] Please Read: NumFOCUS Summit 2020

FYI, this may be interesting to some maintainers. I can forward invites if you let me know what you want one. Cheers, Ralf -- Forwarded message - From: Nicole Foster Date: Sat, Nov 21, 2020 at 4:46 PM Subject: [NumFOCUS Projects] Please Read: NumFOCUS Summit 2020 To: Fiscally Sp

Re: [Numpy-discussion] NumPy Feature Request: Function to wrap angles to range [ 0, 2*pi] or [ -pi, pi ]

On Tue, Nov 24, 2020 at 11:37 AM Daniele Nicolodi wrote: > On 24/11/2020 10:25, Thomas wrote: > > Like Nathaniel said, it would not improve much when compared to the > > modulo operator. > > > > It could handle the edge cases better, but really the biggest benefit > > would be that it is more con

Re: [Numpy-discussion] NumPy Community Meeting Wednesday -- One our earlier from now on!

On Wed, Nov 25, 2020 at 1:05 AM Sebastian Berg wrote: > Hi all, > > There will be a NumPy Community meeting Wednesday November 25th at 12pm > Pacific Time (19:00 UTC). Should be 20:00 UTC (~1.5 hrs from now) Cheers, Ralf Everyone is invited and encouraged to > join in and edit the work-in-pro

Re: [Numpy-discussion] Add sliding_window_view method to numpy

On Fri, Nov 6, 2020 at 4:03 PM Zimmermann Klaus wrote: > Hi, > > On 06/11/2020 15:58, Ralf Gommers wrote: > > On Fri, Nov 6, 2020 at 9:51 AM Zimmermann Klaus > > mailto:klaus.zimmerm...@smhi.se>> wrote: > > I have absolutely no problem keeping this out of t

Re: [Numpy-discussion] Showing by examples how Python-Numpy can be efficient even for computationally intensive tasks

On Thu, Nov 26, 2020 at 9:15 PM PIERRE AUGIER < pierre.aug...@univ-grenoble-alpes.fr> wrote: > > I conclude from these types of results that we need to tell Python users > how to accelerate their Python-Numpy codes when they feel the need of it. I > think acceleration tools should be mentioned in

Re: [Numpy-discussion] Added Rivest-Floyd selection algorithm as an option to numpy.partition

On Tue, Nov 24, 2020 at 12:56 PM Виктория Малясова < malyasova.viktor...@yandex.ru> wrote: > Hello everyone! > > I've implemented the Rivest-Floyd selection algorithm as a second option > to the partition method. I found it works about 1.5 times faster on average > for big array sizes; here are av

Re: [Numpy-discussion] np.{bool,float,int} deprecation

On Sun, Dec 6, 2020 at 4:23 PM Sebastian Berg wrote: > On Sat, 2020-12-05 at 20:12 -0700, Charles R Harris wrote: > > On Sat, Dec 5, 2020 at 4:31 PM Juan Nunez-Iglesias > > wrote: > > > > > Hi all, > > > > > > At the prodding [1] of Sebastian, I’m starting a discussion on the > > > decision to d

Re: [Numpy-discussion] Inclusion of licenses

On Thu, Dec 10, 2020 at 6:42 AM Charles R Harris wrote: > > > On Wed, Dec 9, 2020 at 5:17 PM Charles R Harris > wrote: > >> Hi All, >> >> Currently we append appropriate platform licenses to the LICENSE.txt >> file when building wheels for release. This means that there are >> uncommitted chang

Re: [Numpy-discussion] np.{bool,float,int} deprecation

On Thu, Dec 10, 2020 at 7:25 PM Sebastian Berg wrote: > On Wed, 2020-12-09 at 13:37 -0800, Stephan Hoyer wrote: > > On Wed, Dec 9, 2020 at 1:07 PM Aaron Meurer > > wrote: > > > > > On Wed, Dec 9, 2020 at 9:41 AM Sebastian Berg > > > wrote: > > > > > > > > On Mon, 2020-12-07 at 14:18 -0700, Aaro

Re: [Numpy-discussion] np.{bool,float,int} deprecation

#x27;t possibly introduce it in the main namespace), there `bool` can be the numpy boolean dtype (if desired). The key point is that `bool_` is a terrible name, and keeping `np.bool` that you can use as a dtype specifier is desirable. Cheers, Ralf > Eric > > On Thu, 10 Dec 2020 at 20:0

Re: [Numpy-discussion] np.{bool,float,int} deprecation

On Thu, Dec 10, 2020 at 9:00 PM Sebastian Berg wrote: > On Thu, 2020-12-10 at 20:38 +0100, Ralf Gommers wrote: > > On Thu, Dec 10, 2020 at 7:25 PM Sebastian Berg < > > sebast...@sipsolutions.net> > > wrote: > > > > > On Wed, 2020-12-09 at 13:37 -0800,

Re: [Numpy-discussion] Fixing/implementing value based Casting

On Wed, Dec 9, 2020 at 5:22 PM Sebastian Berg wrote: > Hi all, > > Sorry that this will again be a bit complicated again :(. In brief: > > * I would like to pass around scalars in some (partially new) C-API > to implement value-based promotion. > * There are some subtle commutativity issues wit

Re: [Numpy-discussion] np.{bool,float,int} deprecation

On Sun, Dec 13, 2020 at 7:29 PM Sebastian Berg wrote: > On Sun, 2020-12-13 at 19:00 +1100, Juan Nunez-Iglesias wrote: > > > > > > > On 13 Dec 2020, at 6:25 am, Sebastian Berg < > > > sebast...@sipsolutions.net> wrote: > > > > > > But "default" in NumPy really doesn't mean a whole lot? I can > >

Re: [Numpy-discussion] Installing numpy

On Mon, Dec 14, 2020 at 3:26 PM Matti Picus wrote: > NumPy HEAD does not support python2. You should use v1.16.6 which was the > last release to support python2. > That said, we should raise a comprehensible error. As well as write a test that checks we avoid py27 syntax errors like f-strings in

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

Hi all, I just opened https://github.com/numpy/numpy/pull/18084, "NumPy Sponsorship Guidelines". Below are the most important parts for review (for Related Work, References, etc. see the PR). Please bring up broader points here, and small/textual feedback on the PR. Cheers, Ralf Abstract -

<    1   2   3   4   5   6   7   8   >