Hi all,
There will be a NumPy Community meeting Wednesday September 25 at 11 am
Pacific Time. Everyone is invited to join in and edit the work-in-
progress meeting topics and notes:
https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both
Best wishes
Sebastian
BEGIN:VCALENDAR
PRODID:-//Ximian//NONSGML Evol
Hi all,
we propose formally accepting the NumPy enhancement proposal 29:
"Recommend Python and Numpy version support as a community policy
standard"
available at: https://numpy.org/neps/nep-0029-deprecation_policy.html
If there are no objections within a week it may be accepted. This
proposal i
Hi all,
There will be a NumPy Community meeting Wednesday October 9 at 11 am
Pacific Time. Everyone is invited to join in and edit the work-in-
progress meeting topics and notes:
https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both
Best wishes
Sebastian
BEGIN:VCALENDAR
PRODID:-//Ximian//NONSGML Evoluti
Hi all,
we are planning to remote spring to try to reduce the number of open
PRs and issues, and do triage work.
This is planned for next Tuesday, October 14th, between 9:00 and 15:00
Pacific time. And everyone is invited to join in for as long as you
wish.
I assume we will have a video chat up
tarting
with Monday and not Sunday (as my calendar now shows).
> Regards,
> ZJ
>
> On Wed, Oct 9, 2019 at 5:57 PM Sebastian Berg <
> sebast...@sipsolutions.net> wrote:
> > Hi all,
> >
> > we are planning to remote spring to try to reduce the number
On Fri, 2019-10-11 at 19:20 -0600, Charles R Harris wrote:
> Hi All,
>
> Thought I'd raise the option of trying to put together an NEP for the
> 1.18 release like Python does PEPs. If that is considered too
> procedural for releases that come out every six months or so, are
> there any suggestions
ing ongoing? I tried to join but there were no
> participants.
>
> On 10.10.19, 02:56, "NumPy-Discussion on behalf of Sebastian Berg" <
> numpy-discussion-bounces+einstein.edison=gmail@python.org on
> behalf of sebast...@sipsolutions.net> wrote:
>
>
Sorry for the confusion, we will be using this link:
https://berkeley.zoom.us/j/5416755993
On Tue, 2019-10-15 at 09:00 -0700, Sebastian Berg wrote:
> Hi all,
>
> I have to see if that zoom link works, and we probably have to switch
> over the day and need some place to write dow
for 1.18) 16 issues were closed.
And there are still a couple of PRs hanging which can get wrapped up
soon.
Cheers,
Sebastian
On Wed, 2019-10-09 at 17:55 -0700, Sebastian Berg wrote:
> Hi all,
>
> we are planning to remote spring to try to reduce the number of open
> PRs and is
Hi all,
I am very sorry, I forgot to send out a reminder yesterday with the
sprint going on all day. We will be meeting now, the meeting topics and
notes are:
https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both
Best wishes
Sebastian
signature.asc
Description: This is a digitally signed message part
Hi all,
There will be a NumPy Community meeting today (Wednesday Nov 27) at 11
am Pacific Time. Everyone is invited to join in and edit the work-in-
progress meeting topics and notes:
https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both
Note that from now on, we may try to focus on more technical discus
On Wed, 2019-11-27 at 10:00 -0700, mpro wrote:
> Hi all,
>
> I created pull request #14989, which adds reverse parameter in
> np.sort
> function.
>
> As suggested in the comments, I want to ask for some feedback on
> adding
> parameter 'reverse' . Not only in sort, but in ordering functions in
>
Hi all,
Pull request 14051:
https://github.com/numpy/numpy/pull/14051
means that `np.expand_dims` now accepts multiple axes in the `axis`
argument. As before, the axis signal where a new axis is in the output
array. From the new tests:
a = np.empty((3, 3, 3))
np.expand_dims(a, axis=(0, 1, 2)).s
On Tue, 2019-12-10 at 10:43 -0800, Zijie Poh wrote:
> Hi all,
>
> We've created a PR (#14922) on
> adding keepdims to linspace / logspace / geomspace, which
> enables linspace to directly take the output
> of min and max with keepdims = True as the start and stop arguments.
> That is, the followin
Hi all,
There will be a NumPy Community meeting Wednesday December 11 at 11 am
Pacific Time. Everyone is invited to join in and edit the work-in-
progress meeting topics and notes:
https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both
Best wishes
Sebastian
signature.asc
Description: This is a digital
On Mon, 2019-12-16 at 21:01 +0200, Matti Picus wrote:
> A code path and test have been in the code since NumPy 0.4 for a
> two-argument variant of ``__array__(dtype=None, context=None)``. It
> was
> activated when calling ``ufunc(op)`` or ``ufunc.reduce(op)`` if
> ``op.__array__`` existed. Howev
On Mon, 2019-12-16 at 13:41 -0600, Sebastian Berg wrote:
> On Mon, 2019-12-16 at 21:01 +0200, Matti Picus wrote:
> > A code path and test have been in the code since NumPy 0.4 for a
> > two-argument variant of ``__array__(dtype=None, context=None)``. It
> > was
> > act
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 over with :).
- Sebastian
> Chuck
> __
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
> suggested that the documentation of the module `numpy.dual` should
> also be improved. When I mentioned t
Hi all,
After the holiday break, there will be a NumPy Community meeting
Wednesday January 8 at 11 am Pacific Time. Everyone is invited to join
in and edit the work-in-progress meeting topics and notes:
https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both
Best wishes
Sebastian
signature.asc
Descript
module.html
>
> Best,
> Stephan Hoyer
>
> ===
> NEP 37 — A dispatch protocol for NumPy-like modules
> ===
>
> :Author: Stephan Hoyer
> :Author: Hameer Abbasi
> :Author: Sebastian Berg
> :S
On Fri, 2020-01-17 at 10:39 +, Eric Wieser wrote:
> Today, numpy has a np.ma.mask_rowcols function, which stretches masks
> along
> the full length of an axis. For example, given the matrix::
>
> Questions for the mailing list then:
>
The additional question: I think I am good with adding
Hi all,
There will be a NumPy Community meeting Wednesday January 22 at 11 am
Pacific Time. Everyone is invited to join in and edit the work-in-
progress meeting topics and notes:
https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both
Best wishes
Sebastian
signature.asc
Description: This is a digitall
On Fri, 2020-01-24 at 10:57 -0700, Charles R Harris wrote:
>
>
> On Fri, Jan 24, 2020 at 10:42 AM Kevin Sheppard <
> kevin.k.shepp...@gmail.com> wrote:
> > I think some types of clean-ups, for example, imports, are pretty
> > low cost, low risk and don't have much bearing on and it might be
> > b
Hi all,
I would like to deprecate three C-API functions (more may come later)
in https://github.com/numpy/numpy/pull/15427
The functions are:
* PyArray_GetArrayParamsFromObject
* PyUfunc_GenericCall
* PyUFunc_SetUsesArraysAsData
I could not find downstream usage for any of these and they s
On Fri, 2020-01-24 at 17:56 -0700, Charles R Harris wrote:
>
>
> On Fri, Jan 24, 2020 at 11:29 AM Sebastian Berg <
> sebast...@sipsolutions.net> wrote:
> > Hi all,
> >
> >
> > My idea is to add the deprecation warning now, and if nobody
> &g
Hi all,
Our bi-weekly triage-focused NumPy development meeting is tomorrow
(Wednesday, January 29) at 11 am Pacific Time. Everyone is invited
to join in and edit the work-in-progress meeting topics and notes:
https://hackmd.io/68i_JvOYQfy9ERiHgXMPvg
Best regards,
Sebastian
signature.asc
Descri
Hi all,
There will be a NumPy Community meeting Wednesday February 5 at 11 am
Pacific Time. Everyone is invited to join in and edit the work-in-
progress meeting topics and notes:
https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both
Best wishes
Sebastian
signature.asc
Description: This is a digitall
oposal can also be found
> > > online at https://numpy.org/neps/nep-0037-array-module.html
> > >
> > > Best,
> > > Stephan Hoyer
> > >
> > > ===
> > > NEP 37 — A dispatch protocol for
Hi all,
Our bi-weekly triage-focused NumPy development meeting is tomorrow
(Wednesday, Februrary 12) at 11 am 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 o
Hi all,
In https://github.com/numpy/numpy/pull/15534 I would like to start
deprecating creating dtypes from "abstract" scalar classes, such as:
np.dtype(np.floating) is np.dtype(np.float64)
While, at the same time, `isinstance(np.float32, np.floating)` is true.
Right now `arr.astype(np.floating
sibly
without the `dtype` as a positional argument).
The call your search finds is nice because it must delete `np.dtype`
call.
As is, it is doing the incorrect thing so the deprecation would flush
out a bug.
- Sebastian
> On Fri, Feb 14, 2020 at 2:28 PM Sebastian Berg <
> sebast...@si
On Tue, 2020-02-18 at 10:14 -0500, josef.p...@gmail.com wrote:
> I'm trying to track down test failures of statsmodels against recent
> master dev versions of numpy and scipy.
>
> The core computation is the following in one set of tests that fail
>
> pvals_corrected_raw = pvals * np.aran
Hi all,
There will be a NumPy Community meeting Wednesday February 19 at 11 am
Pacific Time. Everyone is invited to join in and edit the work-in-
progress meeting topics and notes:
https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both
Best wishes
Sebastian
signature.asc
Description: This is a digital
On Wed, 2020-02-19 at 08:58 -0300, Melissa Mendonça wrote:
> Hi all,
>
> I am proposing the acceptance of NEP 44 - Restructuring the NumPy
> Documentation.
>
> https://numpy.org/neps/nep-0044-restructuring-numpy-docs.html
>
> There were some comments about reorganizing the text to make it
> cle
Hi all,
When we create new datatypes, we have the option to make new choices
for the new datatypes [0] (not the existing ones).
The question is: Should every NumPy datatype have a scalar associated
and should operations like indexing return a scalar or a 0-D array?
This is in my opinion a comple
nswer is just that for datatypes that do not round-trip
easily, `.item()` is probably preferable, and for datatypes that do
round-trip scalars are fine.
- Sebastian
>
> On Fri, Feb 21, 2020 at 5:37 PM Sebastian Berg
> wrote:
> > Hi all,
> >
> > When we create new
Hi all,
Our bi-weekly triage-focused NumPy development meeting is tomorrow
(Wednesday, Februrary 26) at 11 am 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 o
On Sun, 2020-02-23 at 22:44 -0800, Stephan Hoyer wrote:
> >
> On Sun, Feb 23, 2020 at 3:59 PM Ralf Gommers
> wrote:
>
> > Also, I'm still not sure I agree with the tone of the discussion on
> > this topic. It's very heavily inspired by what the JAX devs are
> > telling you (the NEP still says P
Hi all,
There will be a NumPy Community meeting Wednesday March 4 at 11 am
Pacific Time. Everyone is invited and encouraged to join in and edit
the work-in-progress meeting topics and notes:
https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both
Best wishes
Sebastian
signature.asc
Description: This is
On Fri, 2020-02-28 at 11:28 -0500, Allan Haldane wrote:
> On 2/23/20 6:59 PM, Ralf Gommers wrote:
> > One of the main rationales for the whole NEP, and the argument in
> > multiple places
> > (
> > https://numpy.org/neps/nep-0037-array-module.html#opt-in-vs-opt-out-for-users
> > )
> > is that it's
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:
> > > On Thu, Feb 6, 2020 at 12:20 PM Sebastian Berg <
> > > sebast...@s
Hi,
On Thu, 2020-03-05 at 11:14 +0400, Abdur-Rahmaan Janhangeer wrote:
> Greetings list,
>
> I have a talk about dunder methods in Python
>
> (
> https://conference.mscc.mu/speaker/67604187-57c3-4be6-987c-ea4bef388ad3
> )
>
> and it would be nice to include Numpy in the mix. Can someone point
Hi all,
(Note that the US has switched to daylight saving time)
Our bi-weekly triage-focused NumPy development meeting is tomorrow
(Wednesday, Februrary 26) at 11 am Pacific Time. Everyone is invited
to join in and edit the work-in-progress meeting topics and notes:
https://hackmd.io/68i_JvOYQfy9
ype System
=
:title: Improved Datatype Support
:Author: Sebastian Berg
:Author: Stéfan van der Walt
:Author: Matti Picus
:Status: Draft
:Type: Standard Track
:Created: 2020-02-03
.. note::
This NEP is part of a series of NEPs encompassing first information
about the prev
Hi all,
There will be a NumPy Community meeting Wednesday March 18 at 11 am
Pacific Time. Everyone is invited and encouraged to join in and edit
the work-in-progress meeting topics and notes:
https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both
Best wishes
Sebastian
PS: The US had its daylight savin
(extension) MetaClass, all details of this class are supposed
to remain experimental in flux at this time.
Cheers
Sebastian
On Wed, 2020-03-11 at 17:02 -0700, Sebastian Berg wrote:
> Hi all,
>
> I am pleased to propose NEP 41: First step towards a new Datatype
> System https://numpy.
Hi all,
since we are spread out all over the world, we are considering moving
the Community meeting time, if you are interested in joining in
occasionally, please fill out the doodle:
https://doodle.com/poll/p3gik4xxdra93cwt
I have currently limited the times to hourly times in the California
wo
ess tangible/approachable.
So, my main point here is that we have to make this large refactor as
approachable as possible, and if that means that at some point someone
has to spend a huge, but hopefully straight forward effort, to rip
DTypes out of NumPy, I think that might be a worthy trade
> >
> > I agree with your suggestion that scalars should not be indexable.
> > Thus,
> > my duck-scalars (and proposed numpy_scalar) would not be indexable.
> > However, I think they should encode their datatype though a .dtype
> > attribute like ndarrays, rather t
On Mon, 2020-03-23 at 18:23 +0100, Francesc Alted wrote:
> > If we were designing a new programming language around array
> > computing
> > principles, I do think that would be the approach I would want to
> > take/consider. But I simply lack the vision of how marrying the
> > idea
> > with the sc
On Tue, 2020-03-24 at 13:59 -0400, Keyvis Damptey wrote:
> Hi Numpy dev community,
>
> I'm keyvis, a statistical data scientist.
>
> I'm currently using numpy in python 3.8.2 64-bit for a clustering
> problem,
> on a machine with 1.9 TB RAM. When I try using np.zeros to create a
> 600,000
> by 60
Hi all,
Our bi-weekly triage-focused NumPy development meeting is tomorrow
(Wednesday, March 25) at 11 am 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 or PR
Hi all,
There will be a NumPy Community meeting Wednesday April 1 at 1(!)pm
Pacific Time. Everyone is invited and encouraged to join in and edit
the work-in-progress meeting topics and notes:
https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both
Best wishes
Sebastian
PS: Remember that we will try doi
On Sun, 2020-04-05 at 00:43 -0400, Warren Weckesser wrote:
> On 4/4/20, Warren Weckesser wrote:
> > It would be handy if in scipy we can use the function
> > `numpy.lib.shape_base.normalize_axis_index` as a consistent method
> > for
> > validating an `axis` argument. Is this function considered p
Hi all,
Our bi-weekly triage-focused NumPy development meeting is tomorrow
(Wednesday, March 25) 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
at the current type numbers.
Best,
Sebastian
On Wed, 2020-03-11 at 17:02 -0700, Sebastian Berg wrote:
> Hi all,
>
> I am pleased to propose NEP 41: First step towards a new Datatype
> System https://numpy.org/neps/nep-0041-improved-dtype-support.html
>
> This NEP motivates
On Wed, 2020-04-08 at 12:37 -0700, Chris Barker wrote:
> sorry to have fallen off the numpy grid for a bit, but:
>
> On Mon, Mar 23, 2020 at 1:37 PM Sebastian Berg <
> sebast...@sipsolutions.net>
> wrote:
>
> > On Mon, 2020-03-23 at 11:45 -0700, Chris Bar
ed/versioned API front, I would hope that we can defer that
as a semi-orthogonal issue, basically saying that for now you have to
provide a NumPy API that faithfully reproduces whatever NumPy version
is installed on the system.
Cheers,
Sebastian
> Cheers,
> Andy
>
> On 3/3/20 6:34 PM,
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:
>
> > On Sun, 2020-02-23 at 22:44 -0800, Stephan Hoyer wrote:
> > > On Sun, Feb 23, 2020 at 3:59 PM Ralf Gomme
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 it would be nice to have a separate NEP 37 implementation
> outside
> of NumPy to play with
On Thu, 2020-04-09 at 22:11 -0500, 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 it would
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",
> > future_modules=("dask.array", "cupy"), fallback="warn")
> >
> >Will give FutureWarning/DeprecationWarning where necess
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, Ralf Gommers wrote:
> > > > 3. I a
Hi all,
There will be a NumPy Community meeting Wednesday April 15th at 1pm
Pacific Time (20:00 UTC). Everyone is invited and encouraged to join in
and edit
the work-in-progress meeting topics and notes:
https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both
Best wishes
Sebastian
___
On Sun, 2020-04-19 at 21:07 +0200, Ralf Gommers wrote:
> On Sun, Apr 19, 2020 at 8:47 PM Joshua Wilson <
> josh.craig.wil...@gmail.com>
> 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
Hi all,
the week has passed, and it has been discussed quite a bit longer, so I
assume that NEP 41 can effectively be accepted.
Even then, I will bring up one point again. I hope that if there is
still need for discussion, it will hopefully happen in a timely manner,
so that, I can go ahead with
Hi all,
Our bi-weekly triage-focused NumPy development meeting is tomorrow
(Wednesday, April 22) 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
Hi all,
it has come up in the last community call that many of our committee
membership lists have not been updated in a while.
This is not a big issue as such. But, while these committees are not
very active on a day-to-day basis, they are an important part of the
community and it is better to u
On Fri, 2020-04-24 at 11:34 +0100, 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=Fa
On Fri, 2020-04-24 at 10:12 -0700, Stephan Hoyer wrote:
> On Fri, Apr 24, 2020 at 6:31 AM Sebastian Berg <
> sebast...@sipsolutions.net>
> wrote:
>
> > One thing to note is that `__array__` is actually asked to return a
> > copy AFAIK.
>
> The documentation
On Fri, 2020-04-24 at 11:10 -0700, Stefan van der Walt wrote:
> On Fri, Apr 24, 2020, at 08:45, Joshua Wilson wrote:
> > But, Stephan pointed out that it might be confusing to users for
> > objects to only exist at typing time, so we came around to the
> > question of whether people are open to the
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 <
> > wieser.eric+nu...@gmail.com>
> > wrote:
> >
> > > Perhaps worth mentioning that we've discussed this sort of API
> > >
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.
> The
> PyTorch maintainers have already said they're fine with adding a
> force
> keyword.
But t
On Tue, 2020-04-28 at 09:58 -0500, 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-
Hi all,
There will be a NumPy Community meeting Wednesday April 29th at 1pm
Pacific Time (20:00 UTC). Everyone is invited and encouraged to join in
and edit the work-in-progress meeting topics and notes:
https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both
Best wishes
Sebastian
__
On Wed, 2020-04-29 at 05:26 -0500, Juan Nunez-Iglesias wrote:
> Hi everyone, and thank you Ralf for carrying the flag in my absence.
> =D
>
> Sebastian, the *primary* motivation behind avoiding detach() in
> PyTorch is listed in original post of the PyTorch issue:
>
> > People not very familiar w
Hi all,
in https://github.com/numpy/numpy/pull/15925 I propose to deprecate
promotion of strings and numbers. I have to double check whether this
has a large effect on pandas, but it currently seems to me that it will
be reasonable.
This means that `np.promote_types("S", "int8")`, etc. will lead
ension of concatenate
even without the loss of this potential use-case.
- Sebastian
> Eric
>
>
>
> On Thu, 30 Apr 2020 at 18:32, Sebastian Berg <
> sebast...@sipsolutions.net>
> wrote:
>
> > Hi all,
> >
> > in https://github.com/numpy/numpy/pul
On Fri, 2020-05-01 at 13:58 -0700, Anirudh Subramanian wrote:
> Hi all,
>
> I added a proposal to deprecate inexact and case insensitive matches
> for
> mode, order, searchside and sortkind. in
> https://github.com/numpy/numpy/pull/16056 , and this stemmed from a
> discussion started in
> https://
Hi all,
Our bi-weekly triage-focused NumPy development meeting is tomorrow
(Wednesday, May 6th) 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 i
Hi all,
There will be a NumPy Community meeting Wednesday May 13th at 1pm
Pacific Time (20:00 UTC). Everyone is invited and encouraged to join in
and edit the work-in-progress meeting topics and notes:
https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both
Best wishes
Sebastian
On Tue, 2020-05-19 at 17:11 +0100, Eric Wieser wrote:
> Hi Will,
>
> To force an iteration to run along certain axes, I believe you should
> be
> using `op_axes`. Your diagnosis is correct that `external_loop` is
> trying
> to help you be more optimal, since it's purpose is exactly that:
> optimiz
Hi all,
Our bi-weekly triage-focused NumPy development meeting is tomorrow
(Wednesday, May 20th) 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
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 compatibility, we cannot use the "right"
way to free the buffer information.
On Mon, 2020-05-25 at 10:09 -0400, Brian Racey wrote:
> Thanks. That is for performance and memory which of course is valid
> for
> most use cases. Would it really be much different than doing
> type/size
> checking of all the np.array arguments to a function to ensure the
> appropriate final np.ar
On Mon, 2020-05-25 at 11:10 -0400, Robert Kern wrote:
> On Mon, May 25, 2020 at 10:36 AM Sebastian Berg <
> sebast...@sipsolutions.net>
> wrote:
>
> > On Mon, 2020-05-25 at 10:09 -0400, Brian Racey wrote:
> > > Would a "complex default" mode ever ma
Hi all,
There will be a NumPy Community meeting Wednesday May 27th at 1pm
Pacific Time (20:00 UTC). Everyone is invited and encouraged to join in
and edit the work-in-progress meeting topics and notes:
https://hackmd.io/76o-IxCjQX2mOXO_wwkcpg?both
Best wishes
Sebastian
On Wed, 2020-05-27 at 18:36 +0200, Ralf Gommers wrote:
> On Fri, May 22, 2020 at 10:14 PM Sebastian Berg <
> sebast...@sipsolutions.net>
> wrote:
>
> I had no idea if we support that, so I crowdsourced some inputs.
>
> Feedback from Travis: "I would be qui
Hi all,
Our bi-weekly triage-focused NumPy development meeting is tomorrow
(Wednesday, June 3rd) 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
Hi all,
I am curious about exploring whether or not we could add simple blocked
iteration to NumPy.
It seems like a long standing small deficiency in NumPy that we do not
support blocked iteration. I do not know how much speed gain we would
actually have in real world code, but I assume some bad-
Hi all,
There will be a NumPy Community meeting Wednesday May 27th at 1pm
Pacific Time (20:00 UTC [0]). 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
De
Hi all,
In the pull request: https://github.com/numpy/numpy/pull/14882
Eric proposes to deprecate the type aliases which NumPy imports
into its main namespace (e.g. np.int, np.bool, see table below [1]).
Right now there seems to be a consensus to move this forward and I plan
on doing that, so thi
On Thu, 2020-06-11 at 09:59 -0500, Sebastian Berg wrote:
> Hi all,
>
> In the pull request: https://github.com/numpy/numpy/pull/14882
> Eric proposes to deprecate the type aliases which NumPy imports
> into its main namespace (e.g. np.int, np.bool, see table below [1]).
>
>
Hi all,
Our bi-weekly triage-focused NumPy development meeting is tomorrow
(Wednesday, June 17th) 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
Hi all,
tl;dr: `np.array()` is somewhat ill-defined, also creating issues for
Quantities. In a recent PR I am cementing, and slightly broadening,
its definition. So we have to decide how we wish to handle code such
as in the long run:
np.array([array-like, array-like])
---
Traditional
Hi all,
There will be a NumPy Community meeting Wednesday May 27th at 1pm
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.asc
Descr
On Fri, 2020-06-26 at 21:53 -0700, leofang wrote:
> Hi all,
>
>
> Since I brought this issue from CuPy to Numpy, I'd like to see a
> decision
> made sooner than later so that downstream libraries like SciPy and
> CuPy can
> act accordingly. I think norm='forward' is fine. If there're still
> peop
Hi all,
Our bi-weekly triage-focused NumPy development meeting is tomorrow
(Wednesday, July 1st) 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
On Sat, 2020-06-27 at 16:08 -0700, Rakesh Vasudevan wrote:
> Hi all,
>
>Following up on this. Created a WIP PR
> https://github.com/numpy/numpy/pull/16700
>
> As stated in the original thread, We need to start by having a sort()
> function for complex numbers that can do it based on keys, rat
201 - 300 of 664 matches
Mail list logo
