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

om> > > > > > wrote: > > > > > > > > > > > I totally agree with the namespace clutter concern, but > > > > > > honestly, I > > > > > > would use `atleast_nd` with its `pos` argument (I might > > >

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

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: > > > > > On Fri, Feb 12, 2021 at 5:15 AM Eric Wieser < > > > wieser.eric+nu...@gm

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

On Mon, 2021-02-15 at 10:12 +0100, Friedrich Romstedt wrote: > Hi, > > Am Do., 4. Feb. 2021 um 09:07 Uhr schrieb Friedrich Romstedt > : > > Am Mo., 1. Feb. 2021 um 09:46 Uhr schrieb Matti Picus < > > matti.pi...@gmail.com>: > > > Typically, one would create a complete example and then pointing > >

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

On Tue, 2021-02-16 at 12:40 +0100, Friedrich Romstedt wrote: > Hi Lev, > > Am Di., 16. Feb. 2021 um 11:50 Uhr schrieb Lev Maximov < > lev.maxi...@gmail.com>: > > > > I've reproduced the error you've described and got rid of it > > without valgrind. > > Those two lines are enough to avoid the segf

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

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: np.array(["1234"], dtype=("U1", 4)) # NumPy 1.20: array(['1', '1', '1', '1'], dtype='>> np.array(["1234"], dtype="(4)U1,i") ar

[Numpy-discussion] NumPy Community Meeting Wednesday

Hi all, There will be a NumPy Community meeting Wednesday February 17th at 12pm Pacific Time (20:00 UTC). Everyone is invited and encouraged to join in and edit the work-in-progress meeting topics and notes at: https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both Best wishes Sebastian signature.a

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

On Wed, 2021-02-17 at 11:15 +0100, Ralf Gommers wrote: > On Wed, Feb 17, 2021 at 2:14 AM Stephan Hoyer > wrote: > > > On Tue, Feb 16, 2021 at 3:13 PM Sebastian Berg < > > sebast...@sipsolutions.net> > > wrote: > > > > > Hi all, > > > &g

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

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 done without > thinking about the issues around our other namespaces. Basically: > - today `numpy.lib` is a public but fai

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

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 ( > https://data-apis.github.io/array-api/latest/). This will add a new > numpy.array_api submodule con

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

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 worried how that is going to interact > > with > > actual NumPy arrays. > > > > Not a subclass! If you got that impression

[Numpy-discussion] NumPy Development Meeting Wednesday - Triage Focus

Hi all, Our bi-weekly triage-focused NumPy development meeting is Wednesday, Feb 24th at 11 am Pacific Time (19:00 UTC). Everyone is invited to join in and edit the work-in-progress meeting topics and notes: https://hackmd.io/68i_JvOYQfy9ERiHgXMPvg I encourage everyone to notify us of issues or P

Re: [Numpy-discussion] Possible documentation bug for numpy.array

On Mon, 2021-03-01 at 01:30 +0100, Michal Radwanski wrote: > Hello, > > I'm not sure if it's expected behaviour or a bug, so I decided to > write > here. First an example: > In [4]: array([2**63]) > Out[4]: array([9223372036854775808], dtype=uint64) > > In [5]: array([2**63-1, 2**63]) > Out[5]:

[Numpy-discussion] NumPy Community Meeting Wednesday (Today)

Hi all, There will be a NumPy Community meeting Wednesday March 3rd at 12pm Pacific Time (20:00 UTC). Everyone is invited and encouraged to join in and edit the work-in-progress meeting topics and notes at: https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both Best wishes Sebastian PS: Sorry for the

Re: [Numpy-discussion] String accessor methods

On Sun, 2021-03-07 at 09:34 +, Kevin Sheppard wrote: > I think that and string functions that are exposed from an ndarray > would > have to be guaranteed to work in-place. Requiring casting to objects > to use > the methods feels more like syntactic sugar than an essential case. I > think > mos

[Numpy-discussion] NumPy logo merchandise available at spreadshirt NumFOCUS shop

On Thu, 2021-03-04 at 16:54 -0800, Stephan Hoyer wrote: > I love your mittens! > > NumPy really should be in the NumFOCUS store, but it currently isn't: > https://shop.spreadshirt.com/numfocus/all > Various items with the NumPy logo (text below cube) are now available here from the NumFOCUS spre

[Numpy-discussion] NumPy Development Meeting Wednesday - Triage Focus

Hi all, Our bi-weekly triage-focused NumPy development meeting is Wednesday, March 10th at 11 am Pacific Time (19:00 UTC). Everyone is invited to join in and edit the work-in-progress meeting topics and notes: https://hackmd.io/68i_JvOYQfy9ERiHgXMPvg I encourage everyone to notify us of issues or

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

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 is a pretty major difficulty without a clear answer as of now. 1. I

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

On Wed, 2021-03-10 at 13:44 -0700, Aaron Meurer wrote: > On Wed, Mar 10, 2021 at 10:42 AM Sebastian Berg > wrote: > > > > Top Posting, to discuss post specific questions about NEP 47 and > > partially the start on implementing it in: > > > >     https

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

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 discuss post specific questions about NEP 47 and > > partially the start on implementing it in: &

Re: [Numpy-discussion] Looking for a difference between Numpy 0.19.5 and 0.20 explaining a perf regression with Pythran

On Fri, 2021-03-12 at 21:36 +0100, PIERRE AUGIER wrote: > Hi, > > I'm looking for a difference between Numpy 0.19.5 and 0.20 which > could explain a performance regression (~15 %) with Pythran. > > I observe this regression with the script > https://github.com/paugier/nbabel/blob/master/py/bench

Re: [Numpy-discussion] Looking for a difference between Numpy 0.19.5 and 0.20 explaining a perf regression with Pythran

differences in the same `memcpy` or similar calls, due to whatever reasons (maybe due to compiler changes, or due to address space changes... or maybe the former causing the latter, I don't know.). Cheers, Sebastian > > Cheers, > > Pierre > > - Mail original -

Re: [Numpy-discussion] Looking for a difference between Numpy 0.19.5 and 0.20 explaining a perf regression with Pythran

use type(df.values) gives so I would > > expect arr.copy() and np.copy(arr) to give exactly the same result. > > > > Note that I think I'm doing quite serious and reproducible > > benchmarks. I also checked that this regression is reproducible on > > another compute

Re: [Numpy-discussion] Perf regression with Pythran between Numpy 0.19.5 and 0.20 (commit 4cd6e4b336fbc68d88c0e9bc45a435ce7b721f1f, ENH: implement NEP-35's `like=` argument)

> > > > > > arr = np.ascontiguousarray(df.values) > > > > > > lead to "slow" execution while arrays prepared with > > > > > > arr = np.copy(df.values) > > > > > > lead to faster execution. > > > > >

Re: [Numpy-discussion] NEP 42 status

On Tue, 2021-03-16 at 13:17 -0500, Lee Johnston wrote: > Is the work on NEP 42 custom DTypes far enough along to experiment > with? > TL;DR: Its not quite ready, but if we work together I think we could experiment a fair bit. Mainly ufuncs are still limited (though not quite completely missing)

[Numpy-discussion] Exposing experimental C-API for DTypes

Hi all, For DTypes, it may soon make sense to expose API publicly for testing/experimentation. But, right now I don't really want to get roped into discussing API details too much and slowing down potential revamps. Do we have any idea for exposing an "experimental" API? The first option would

[Numpy-discussion] NumPy Community Meeting Wednesday (no DST: for those in the US, one hour later)

Hi all, There will be a NumPy Community meeting Wednesday March 3rd at 20:00 UTC. Everyone is invited and encouraged to join in and edit the work-in-progress meeting topics and notes at: https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both Best wishes Sebastian PS: As the subject says, we will stay

Re: [Numpy-discussion] NEP 42 status

nge `[double_min, double_max]`. That seems like a good trade-off in complexity. > On Tue, Mar 16, 2021 at 4:11 PM Sebastian Berg < > sebast...@sipsolutions.net> > wrote: > > > On Tue, 2021-03-16 at 13:17 -0500, Lee Johnston wrote: > > > Is the work on NEP 42 cu

[Numpy-discussion] NumPy Development Meeting Wednesday - Triage Focus

Hi all, Our bi-weekly triage-focused NumPy development meeting is Wednesday, March 10th at 11 am Pacific Time (18:00 UTC). Everyone is invited to join in and edit the work-in-progress meeting topics and notes: https://hackmd.io/68i_JvOYQfy9ERiHgXMPvg I encourage everyone to notify us of issues or

Re: [Numpy-discussion] NEP 42 status – Store quantity in a NumPy array and convert it :)

On Wed, 2021-03-17 at 17:12 -0500, Sebastian Berg wrote: > On Wed, 2021-03-17 at 07:56 -0500, Lee Johnston wrote: > 3. In parallel, I will create a small "toy" DType based on that >    experimental API.  Probably in a separate repo (in the NumPy >    organization?). >

[Numpy-discussion] NumPy Community Meeting Wednesday (no DST: for those e.g. in the EU)

Hi all, There will be a NumPy Community meeting Wednesday March 3rd at 20:00 UTC. Everyone is invited and encouraged to join in and edit the work-in-progress meeting topics and notes at: https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both Best wishes Sebastian PS: As the subject says, we will stay

[Numpy-discussion] Type resolver related deprecations and changes

Hi all, I have to do some changes to the type resolution, and I started these here: https://github.com/numpy/numpy/pull/18718 There are four changes: * Deprecate `signature="l"` and `signature=("l",)`, these are confusing since the signature should include all inputs and outputs. To only pr

[Numpy-discussion] umPy Development Meeting Wednesday - Triage Focus

Hi all, Our bi-weekly triage-focused NumPy development meeting is Wednesday, March 10th at 11 am Pacific Time (18:00 UTC). Everyone is invited to join in and edit the work-in-progress meeting topics and notes: https://hackmd.io/68i_JvOYQfy9ERiHgXMPvg I encourage everyone to notify us of issues or

Re: [Numpy-discussion] Type resolver related deprecations and changes

On Fri, 2021-04-02 at 15:46 -0500, Sebastian Berg wrote: > Hi all, > > I have to do some changes to the type resolution, and I started these > here: https://github.com/numpy/numpy/pull/18718 > Just to keep everyone updated. We discussed this yesterdays meeting, and settled

[Numpy-discussion] NumPy Community Meeting Wednesday

Hi all, There will be a NumPy Community meeting Wednesday April 14th at 20:00 UTC. Everyone is invited and encouraged to join in and edit the work-in-progress meeting topics and notes at: https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both Best wishes Sebastian signature.asc Description: This is a

Re: [Numpy-discussion] Improving performance of the `numpy.any` function.

On Wed, 2021-04-14 at 18:53 -0700, dan_patterson wrote: > a = np.zeros(1_000_000) > > a[100] = 1 > > %timeit np.any(a) > 814 µs ± 17.8 µs per loop (mean ± std. dev. of 7 runs, 1000 loops > each) > > %timeit np.any(a == 1) > 488 µs ± 5.68 µs per loop (mean ± std. dev. of 7 runs, 1000 loops > each

[Numpy-discussion] NumPy Development Meeting Wednesday - Triage Focus

Hi all, Our bi-weekly triage-focused NumPy development meeting is Wednesday, Arpil 21st at 11 am Pacific Time (18:00 UTC). Everyone is invited to join in and edit the work-in-progress meeting topics and notes: https://hackmd.io/68i_JvOYQfy9ERiHgXMPvg I encourage everyone to notify us of issues or

[Numpy-discussion] NumPy Community Meeting Wednesday

Hi all, There will be a NumPy Community meeting Wednesday April 28th at 20:00 UTC. Everyone is invited and encouraged to join in and edit the work-in-progress meeting topics and notes at: https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both Best wishes Sebastian __

[Numpy-discussion] NumPy Development Meeting Wednesday - Triage Focus

Hi all, Our bi-weekly triage-focused NumPy development meeting is Wednesday, May 5th at 11 am Pacific Time (18:00 UTC). Everyone is invited to join in and edit the work-in-progress meeting topics and notes: https://hackmd.io/68i_JvOYQfy9ERiHgXMPvg I encourage everyone to notify us of issues or PR

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

On Thu, 2021-05-06 at 13:06 +0100, Eric Wieser wrote: > Another argument for supporting stateful allocators would be > compatibility > with the stateful C++11 allocator API, such as > https://en.cppreference.com/w/cpp/memory/allocator_traits/allocate. The Python version of this does have a `void

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

On Mon, 2021-05-10 at 10:01 +0100, Eric Wieser wrote: > > The Python version of this does have a `void *ctx`, but I am not > > sure if > the use for this is actually valuable for the NumPy use-cases. > > Do you mean "the CPython version"? If so, can you link a reference? Yes, sorry, had been a wh

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

that automatically releases the GPU > handle after the allocator has been restored to the default and the > last > array using it is cleaned up. > > If that cupy use-case seems somwhat plausible, then I think we should > go > with the PyObject approach. > If it doesn't s

Re: [Numpy-discussion] NEP 42 status – Store quantity in a NumPy array and convert it :)

On Thu, 2021-03-25 at 17:27 -0500, Sebastian Berg wrote: > On Wed, 2021-03-17 at 17:12 -0500, Sebastian Berg wrote: > > On Wed, 2021-03-17 at 07:56 -0500, Lee Johnston wrote: > > > > > 3. In parallel, I will create a small "toy" DType based on that >

[Numpy-discussion] NumPy Community Meeting Wednesday

Hi all, There will be a NumPy Community meeting Wednesday Mai 12th at 20:00 UTC. Everyone is invited and encouraged to join in and edit the work-in-progress meeting topics and notes at: https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both Best wishes Sebastian

[Numpy-discussion] NumPy Development Meeting Wednesday - Triage Focus

Hi all, Our bi-weekly triage-focused NumPy development meeting is Wednesday, May 19th at 11 am Pacific Time (18:00 UTC). Everyone is invited to join in and edit the work-in-progress meeting topics and notes: https://hackmd.io/68i_JvOYQfy9ERiHgXMPvg I encourage everyone to notify us of issues or P

Re: [Numpy-discussion] Indexing question

On Thu, 2021-05-20 at 13:46 -0400, Robert Kern wrote: > On Thu, May 20, 2021 at 1:40 PM CJ Carey > wrote: > > If NEP 21 is accepted ( > > https://numpy.org/neps/nep-0021-advanced-indexing.html) this would > > be > > even simpler: > > > > out.vindex[:, x] = 1 > > > > Was there ever a decision

[Numpy-discussion] The status of DType Refactor

Hi all, I thought I would give a brief update on where we are with new DTypes. Partially for Matti who is braving the brunt of the review, but also for anyone else interested.  Please don't hesitate to ask for clarifications, any questions, or to schedule a meeting to discuss! Recap The past yea

[Numpy-discussion] NumPy Community Meeting Wednesday

Hi all, There will be a NumPy Community meeting Wednesday Mai 26th at 20:00 UTC. Everyone is invited and encouraged to join in and edit the work-in-progress meeting topics and notes at: https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both Best wishes Sebastian

[Numpy-discussion] NumPy Development Meeting Wednesday - Triage Focus (Soon today!)

Hi all, Our bi-weekly triage-focused NumPy development meeting is Wednesday, June 2nd at 11 am Pacific Time (18:00 UTC). Everyone is invited to join in and edit the work-in-progress meeting topics and notes: https://hackmd.io/68i_JvOYQfy9ERiHgXMPvg I encourage everyone to notify us of issues or P

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

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`, `np.asarray`, `np.arange`, etc. as final. The previous acceptance ma

[Numpy-discussion] Tensor Typing presentation and discussion on Wednesday! (As part of the NumPy Community Meeting)

Hi all, There will be a NumPy Community meeting Wednesday June 9th at 20:00 UTC. This meeting will be dedicated to a presentation by Matthew and Pradeep about typing arrays. The title is: "Better types for numerical computing - arrays generic in dtype and shape" Abstract: An overview of why mo

Re: [Numpy-discussion] Tensor Typing presentation and discussion on Wednesday! (As part of the NumPy Community Meeting)

On Tue, 2021-06-08 at 11:40 -0700, Stefan van der Walt wrote: > On Tue, Jun 8, 2021, at 03:23, Juan Nunez-Iglesias wrote: > > Hello! Any chance this could be recorded for those of us in useless > > time zones? 😂 > > I added a note to the agenda; we'll ask the speakers and record if > they don't m

[Numpy-discussion] NumPy Development Meeting Wednesday - Triage Focus (Soon today!)

Hi all, Our bi-weekly triage-focused NumPy development meeting is Wednesday, June 16nd at 11 am Pacific Time (18:00 UTC). Everyone is invited to join in and edit the work-in-progress meeting topics and notes: https://hackmd.io/68i_JvOYQfy9ERiHgXMPvg I encourage everyone to notify us of issues or

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

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` keyword argument). Strictly speaking, this is again

[Numpy-discussion] NumPy Community Meeting Wednesday

Hi all, There will be a NumPy Community meeting Wednesday June 23rd at 20:00 UTC. Everyone is invited and encouraged to join in and edit the work-in-progress meeting topics and notes at: https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both Best wishes Sebastian __

[Numpy-discussion] Moving triage meeting two hours earlier

Hi all, I would like to move the triage meeting to two hours earlier. That would make it 9am Pacific time and 4pm UTC (6pm central European summer time). That is to allow eastern time zones to join more easily. If nobody of the core team has any objections, I will adjust the time for this Wednes

[Numpy-discussion] NumPy Development Meeting Wednesday - Triage Focus (now earlier!)

Hi all, Our bi-weekly triage-focused NumPy development meeting is Wednesday, June 30th at 9 am Pacific Time (18:00 UTC). Everyone is invited to join in and edit the work-in-progress meeting topics and notes: https://hackmd.io/68i_JvOYQfy9ERiHgXMPvg I encourage everyone to notify us of issues or P

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

Hi all, The PR https://github.com/numpy/numpy/pull/19211 proposes to extend argmin and argmax with a `keepdims=False` keyword-only argument. This is a standard argument in NumPy, so it is a small API addition. The PR also proposes to add: * `PyArray_ArgMinWithKeepdims` * `PyArray_ArgMaxWithKee

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

On Thu, 2021-07-01 at 00:39 -0700, Stefan van der Walt wrote: > Hi Sebastian, > > On Wed, Jun 30, 2021, at 18:23, Sebastian Berg wrote: > > The PR https://github.com/numpy/numpy/pull/19211 proposes to extend > > argmin and argmax with a `keepdims=False` keyword-only argu

[Numpy-discussion] NumPy Community Meeting Wednesday

Hi all, There will be a NumPy Community meeting Wednesday July 7th at 20:00 UTC. Everyone is invited and encouraged to join in and edit the work-in-progress meeting topics and notes at: https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both Best wishes Sebastian ___

[Numpy-discussion] Floating point warnings/errors for comparisons, etc.?

Hi all, I am trying to clean up our floating point warning handling: https://github.com/numpy/numpy/pull/19316 And an upcoming PR to remove most floating point error clearing. There are some things I am unsure about, though. Part of why it got so confusing, is that GCC seemed to have fixed

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

On Mon, 2021-07-05 at 11:17 -0700, Stefan van der Walt wrote: > On Mon, Jul 5, 2021, at 00:42, Ralf Gommers wrote: > > I share your dislike, but I don't really see a better place where > > it doesn't make it even harder to spell, but I did just think of an > > alternative that may actually be quite

[Numpy-discussion] NumPy Development Meeting Wednesday

Hi all, Our bi-weekly triage-focused NumPy development meeting is Wednesday, July 14th at 9 am Pacific Time (16:00 UTC). Everyone is invited to join in and edit the work-in-progress meeting topics and notes: https://hackmd.io/68i_JvOYQfy9ERiHgXMPvg I encourage everyone to notify us of issues or P

Re: [Numpy-discussion] Add smallest_normal and smallest_subnormal attributes to finfo

Hi all, We just merged the PR to add `np.finfo.smallest_normal` and `np.finfo.smallest_subnormal` to `np.finfo` (the floating point DType information object): * smallest_normal: - An alias for `np.finfo.tiny` - The smallest "normal". I.e. the smallest number larger than zero that has full

[Numpy-discussion] NumPy Community Meeting Wednesday

Hi all, There will be a NumPy Community meeting Wednesday July 21st at 20:00 UTC. Everyone is invited and encouraged to join in and edit the work-in-progress meeting topics and notes at: https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both Best wishes Sebastian signature.asc Description: This is a d

Re: [Numpy-discussion] Proposed change from POSIX to PyMem_RawXXX (plain text resend)

On Thu, 2021-07-22 at 16:48 +, Daniel Waddington wrote: > Hi, > I'm working with Numpy in the context of supporting different memory > types such as persistent memory and CXL attached.  I would like to > propose a minor change, but figured I would get some initial feedback > from the developer

[Numpy-discussion] NumPy Development Meeting Wednesday - Triage Focus

Hi all, Our bi-weekly triage-focused NumPy development meeting is Wednesday, July 28th at 9 am Pacific Time (16:00 UTC). Everyone is invited to join in and edit the work-in-progress meeting topics and notes: https://hackmd.io/68i_JvOYQfy9ERiHgXMPvg I encourage everyone to notify us of issues or P

[Numpy-discussion] Floating point precision expectations in NumPy

Hi all, there is a proposal to add some Intel specific fast math routine to NumPy: https://github.com/numpy/numpy/pull/19478 part of numerical algorithms is that there is always a speed vs. precision trade-off, giving a more precise result is slower. So there is a question what the general

Re: [Numpy-discussion] Floating point precision expectations in NumPy

On Fri, 2021-07-30 at 11:04 -0700, Jerry Morrison wrote: > On Tue, Jul 27, 2021 at 4:55 PM Sebastian Berg < > sebast...@sipsolutions.net> > wrote: > > > Hi all, > > > > there is a proposal to add some Intel specific fast math routine to > > NumPy: &

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

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, np.nan]) Before 1.21: >>> np.unique(a) array([ 1., nan, n

Re: [Numpy-discussion] Proposal for adding bit_count

On Thu, 2021-07-29 at 21:46 +0530, Ganesh Kathiresan wrote: > Hi All, > > > > I am working on a new > UFunc, ` > bit_count ` (popcount > in > other languages) that aims to count the number of 1-bits in > th

Re: [Numpy-discussion] Proposal for adding bit_count

On Mon, 2021-08-02 at 13:10 -0700, Stefan van der Walt wrote: > On Mon, Aug 2, 2021, at 10:50, Sebastian Berg wrote: > > * Should `np.ndarray.bit_count()` exist?  I tend against this; > >   but we should have it on (integer) scalars to mirror the > >   Python `int`. >

[Numpy-discussion] NumPy Community Meeting Wednesday

Hi all, There will be a NumPy Community meeting Wednesday August 4th at 20:00 UTC. Everyone is invited and encouraged to join in and edit the work-in-progress meeting topics and notes at: https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both Best wishes Sebastian signature.asc Description: This is a

[Numpy-discussion] NumPy Development Meeting Wednesday - Triage Focus

Hi all, Our bi-weekly triage-focused NumPy development meeting is Wednesday, August 11th at 9 am Pacific Time (16:00 UTC). Everyone is invited to join in and edit the work-in-progress meeting topics and notes: https://hackmd.io/68i_JvOYQfy9ERiHgXMPvg I encourage everyone to notify us of issues or

[Numpy-discussion] NumPy Community Meeting Wednesday

Hi all, There will be a NumPy Community meeting Wednesday August 18th at 20:00 UTC. Everyone is invited and encouraged to join in and edit the work-in-progress meeting topics and notes at: https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both Best wishes Sebastian signature.asc Description: This is

[Numpy-discussion] NumPy Development Meeting Wednesday - Triage Focus

Hi all, Our bi-weekly triage-focused NumPy development meeting is Wednesday, August 25th at 9 am Pacific Time (16:00 UTC). Everyone is invited to join in and edit the work-in-progress meeting topics and notes: https://hackmd.io/68i_JvOYQfy9ERiHgXMPvg I encourage everyone to notify us of issues or

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

On Wed, 2021-08-25 at 17:48 +0200, Serge Guelton wrote: > Hi folks, > > https://github.com/numpy/numpy/pull/19713 showcases what *could* be a > first step > toward getting rid of generated C code within numpy, in favor of some > C++ code, > coupled with a single macro trick. > > Basically, templa

[Numpy-discussion] NumPy Development Meeting Wednesday - Triage Focus

Hi all, Our bi-weekly triage-focused NumPy development meeting is Wednesday, September 8th at 9 am Pacific Time (16:00 UTC). Everyone is invited to join in and edit the work-in-progress meeting topics and notes: https://hackmd.io/68i_JvOYQfy9ERiHgXMPvg I encourage everyone to notify us of issues

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

On Sun, 2021-09-05 at 21:08 +0200, Ralf Gommers wrote: > 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 dtyp

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

On Fri, 2021-09-10 at 14:51 -0600, Aaron Meurer wrote: > On Thu, Sep 9, 2021 at 7:11 PM Sebastian Berg > wrote: > > > > On Sun, 2021-09-05 at 21:08 +0200, Ralf Gommers wrote: > > > On Sat, Sep 4, 2021 at 10:02 AM Kshitij Kalambarkar < > > > kshitijkalambar

[Numpy-discussion] NumPy Community Meeting Wednesday

Hi all, There will be a NumPy Community meeting Wednesday September 15th at 20:00 UTC. Everyone is invited and encouraged to join in and edit the work-in-progress meeting topics and notes at: https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both Best wishes Sebastian signature.asc Description: This

Re: [Numpy-discussion] deprecating float(x) for ndim > 0

On Wed, 2021-09-15 at 17:25 +, george trojan wrote: > Responding to the post by nico.schloe...@gmail.com (I subscribe to > the > digest). > > I just wrote the following code: > > twb = scipy.optimize.fsolve(phi, tdb, args=(tdb, p, w, hd_tdb, > hg_tdb), > xtol=1e-8) > tdb, p, w, hd_tdb, hg_tdb

[Numpy-discussion] Re: deprecating float(x) for ndim > 0

On Thu, 2021-09-16 at 14:39 -0600, Aaron Meurer wrote: > On Thu, Sep 16, 2021 at 12:32 AM Nico Schlömer < > nico.schloe...@gmail.com> wrote: > > > > > I was playing with this though and was a little surprised to find > > > NumPy allows things like this: > > > > > > > > > a = np.array([1, 2, 3])

[Numpy-discussion] NumPy Development Meeting Wednesday - Triage Focus

Hi all, Our bi-weekly triage-focused NumPy development meeting is Wednesday, September 22nd at 9 am Pacific Time (16:00 UTC). Everyone is invited to join in and edit the work-in-progress meeting topics and notes: https://hackmd.io/68i_JvOYQfy9ERiHgXMPvg I encourage everyone to notify us of issues

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

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 Europe and allow a more reasonable time including for India. As of now,

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

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, > > > > Melissa brought up that we should reschedule the bi-weekly > > community > > mee

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

On Wed, 2021-08-25 at 17:48 +0200, Serge Guelton wrote: > Hi folks, > > https://github.com/numpy/numpy/pull/19713 showcases what *could* be a > first step > toward getting rid of generated C code within numpy, in favor of some > C++ code, > coupled with a single macro trick. It seems time to pic

[Numpy-discussion] NumPy Community Meeting Wednesday (earlier @16:30 UTC!)

Hi all, There will be a NumPy Community meeting Wednesday September 29th at 16:30 UTC. Everyone is invited and encouraged to join in and edit the work-in-progress meeting topics and notes at: https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both Best wishes Sebastian NOTE: The time is different from

[Numpy-discussion] Re: ENH: Extended choose -- add an implementation of the choose function which supports more than 32 choices

On Wed, 2021-09-29 at 15:09 -0400, Aaron Watters wrote: > Hi folks! > > The np.choose function raises a ValueError if called with more than > 31 > choices. > This PR adds an alternate implementation np.extended_choose (which > uses the > base implementation) that supports any number of choices. >

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

On Wed, 2021-09-29 at 11:07 -0700, 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 continue

[Numpy-discussion] Deprecating boolean indices in `partition` and disable negative time unit factors `M8[-1s]`

Hi all, A brief note that the PR: https://github.com/numpy/numpy/pull/2 deprecated the use of boolean arrays as indices in argpartition (aligning its behaviour with normal indexing). Further: https://github.com/numpy/numpy/pull/19731 silently turns negative time factor indices into errors. Pr

[Numpy-discussion] NumPy Development Meeting Wednesday - Triage Focus

Hi all, Our bi-weekly triage-focused NumPy development meeting is Wednesday, October 6th at 9 am Pacific Time (16:00 UTC). Everyone is invited to join in and edit the work-in-progress meeting topics and notes: https://hackmd.io/68i_JvOYQfy9ERiHgXMPvg I encourage everyone to notify us of issues or

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

On Wed, 2021-08-25 at 17:50 -0500, Sebastian Berg wrote: > On Wed, 2021-08-25 at 17:48 +0200, Serge Guelton wrote: > > Hi folks, > > > > https://github.com/numpy/numpy/pull/19713 showcases what *could* be > > a > > first step > > toward getting rid of gen

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

is that we have two ways to template C now... I hope that will pay off soon (as in C++ is proofs useful in some way), since it feels like replacing all `c.src` code is a pretty large (although probably doable) endeavor. Cheers, Sebastian > On Thu, Oct 7, 2021 at 3:02 PM Sebastian Berg > >

[Numpy-discussion] Re: Documentation Team meeting - Monday October 11

On Mon, 2021-10-11 at 13:26 -0300, Melissa Mendonça wrote: > Can you try using this link: > https://zoom.us/j/96219574921?pwd=VTRNeGwwOUlrYVNYSENpVVBRRjlkZz09 > The link includes `pwd=...` its a bit annoying, but you can just copy paste the last bit of the link as the password. Although, there sh

[Numpy-discussion] NumPy Community Meeting Wednesday (today @16:30 UTC!)

Hi all, There will be a NumPy Community meeting Wednesday September 29th at 16:30 UTC. Everyone is invited and encouraged to join in and edit the work-in-progress meeting topics and notes at: https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both Best wishes Sebastian PS: Sorry for the late reminder!

[Numpy-discussion] Percentile/Quantile "interpolation" refactor

Hi all, after a long time Abel has helped us and refactored the quantile and percentile functions' `interpolation` keyword. This was long overdue since NumPy implements three (the non-default) interpolation methods that appear to be very much non-standard. On the other hand, NumPy currently has

[Numpy-discussion] Moving triage meeting to the same slot as the community meeting

Hi all, for simplicity, I suggest to move the triage meeting also by 30 minutes later to 16:30 UTC, sorry for not thinking of that when moving the community meeting. If no one protests I will announce it and change the calendar accordingly tomorrow. Cheers, Sebastian signature.asc Description

[Numpy-discussion] NumPy Development Meeting Wednesday - Triage Focus

Hi all, Our bi-weekly triage-focused NumPy development meeting is Wednesday, October 20th at 16:30 UTC (9:30am Pacific Time). Everyone is invited to join in and edit the work-in-progress meeting topics and notes: https://hackmd.io/68i_JvOYQfy9ERiHgXMPvg I encourage everyone to notify us of issues

[Numpy-discussion] NumPy Community Meeting Wednesday

Hi all, There will be a NumPy Community meeting Wednesday October 27th at 16:30 UTC. Everyone is invited and encouraged to join in and edit the work-in-progress meeting topics and notes at: https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both Best wishes Sebastian signature.asc Description: This is

[Numpy-discussion] Current state of the DType refactor

Hi all, with the latest changes, NumPy has a completely revised infrastructure for: * Creating a new array from Python objects * Organizing casting (to align almost fully with ufuncs) * Organize the inner-loops and dispatching of ufuncs * Create and "promote" DTypes Which means that the core fun

<    1   2   3   4   5   6   7   >