[Numpy-discussion] Re: NumPy accepted for Google Season of Docs 2024

That's great news, congratulations to you both Mars and Mukulika! ~Ross On Wed, Apr 10, 2024 at 5:24 PM Mukulika Pahari wrote: > Hi all, > > I am very happy to announce that NumPy has been accepted for the Google > Season of Docs grant. This year, Mars (@MarsBarLee) will continue working > on

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

+1 from me as well! On Mon, Apr 8, 2024 at 9:16 AM Devulapalli, Raghuveer < raghuveer.devulapa...@intel.com> wrote: > +1 > > > -Original Message- > > From: Matti Picus > > Sent: Sunday, April 7, 2024 7:33 PM > > To: Discussion of Numerical Python > > Subject: [Numpy-discussion] Moving

[Numpy-discussion] No numpy documentation meeting 08/28

Hi all, There will be no documentation meeting this tomorrow, Monday 08/28 as the regular attendees have conflicts. We'll pick back up in 2 weeks! Ross ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to

[Numpy-discussion] Re: Welcome Nathan Goldbaum as a Maintainer

Welcome Nathan! On Mon, May 29, 2023 at 7:47 AM Charles R Harris wrote: > > > On Mon, May 29, 2023 at 1:15 AM Sebastian Berg > wrote: > >> Hi all, >> >> On behalf of the steering council, I am very happy to announce that >> Nathan has joined us as a Maintainer! >> >> Nathan has been

[Numpy-discussion] Documentation Meeting: Monday May 8th at 4PM UTC

The next installment of the bi-weekly NumPy documentation meeting will be held tomorrow, Monday May 8th at 4PM UTC (9AM PDT). A rolling, editable agenda can be found here: https://hackmd.io/oB_boakvRqKR-_2jRV-Qjg

[Numpy-discussion] Align Community & Triage meeting times

Hi All, Currently, the numpy community and triage meetings alternate between 7PM UTC (community) and 5PM UTC (triage) on a biweekly basis. At the most recent community meeting, there was a strong preference among attendees to do away with the alternating times and have both meetings at 5PM UTC.

[Numpy-discussion] Documentation Meeting - Monday March 13th, 4PM UTC

Hi all, We'll have the bi-weekly NumPy documentation meeting tomorrow, Monday 3/13 at 4PM UTC. *Note that this will be an hour later in the US due to daylight savings! *Check out the community calendar to see if you're affected. ~Ross

[Numpy-discussion] NumPy Documentation Meeting - Monday 2/13 @ 8AM PDT

Hi all, We'll be meeting to discuss numpy documentation tomorrow at 8AM Pacific time. All are welcome! The zoom link and meeting agenda can be found here: https://hackmd.io/oB_boakvRqKR-_2jRV-Qjg ~Ross ___ NumPy-Discussion mailing list --

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

This developer-in-residence program is an excellent idea, many thanks to everyone who helped launch the initiative. Congratulations Sayed! ~Ross On Fri, Dec 2, 2022 at 5:04 AM Julien Jerphanion wrote: > Congratulations to all the NumPy team!  > > Sayed: I stumbled on a few of your

[Numpy-discussion] No documentation meeting Monday Sept. 26th

Hi all, The regularly-scheduled documentation meeting for this Monday, Sept. 26th has been cancelled due to limited availability. The next documentation meeting will be held on Monday October 10th. If there are any documentation-related discussions you'd like to raise before the next meeting,

[Numpy-discussion] Re: Additional aliases for MaskedArray

On the one hand it does seem like `ma` versions of these functions, especially `ones_like` and `zeros_like`, are sensible additions given that they should be relatively straightforward extensions of the core functions. OTOH in my experience "relatively straightforward changes" to the masked array

[Numpy-discussion] npreadtext: `numpy.loadtxt` in C

Hi all, This is to announce [`npreadtext`](https://github.com/BIDS-numpy/npreadtext), a drop-in replacement for `numpy.loadtxt` written in C for improved performance. We are now at feature parity with `loadtxt`, and would greatly appreciate your feedback & testing. We hope eventually to include

Re: [Numpy-discussion] Numpy FFT normalization options issue (addition of new option)

I think it's also important to get the thoughts of the SciPy community on this topic so that we avoid divergence between numpy.fft and scipy.fft. I would recommend sending this discussion to the scipy mailing list as well. ~Ross On Tue, Jun 23, 2020 at 4:11 PM Feng Yu wrote: > Your approach

Re: [Numpy-discussion] Numpy FFT normalization options issue (addition of new option)

n a compelling use-case at that time. One potential issue that stood out to me was the name of the new keyword option. At face value, "inverse" seems like a poor choice given the established use of the term in Fourier analysis. For example, one might expect

Re: [Numpy-discussion] Proposal - extend histograms api to allow uneven bins

Just a few thoughts re: the changes proposed in https://github.com/numpy/numpy/pull/14278 1. Though the PR is limited to the 'auto' kwarg, the issue of potential memory problems for the automated binning methods is a more general one (e.g. #15332 ).