[Numpy-discussion] Re: welcome Andrew Nelson to the NumPy maintainers team

On Mon, Aug 21, 2023, at 01:34, Ralf Gommers wrote: > On behalf of the steering council, I am very happy to announce that Andrew is > joining the Maintainers team. Andrew, a warm welcome to the team! Thank you for all your work so far, and for continuing your involvement with the project. Best

Re: [Numpy-discussion] Fwd: SciPy2017 Sprints FinAid for sprint leaders/core devs

On Wed, Mar 29, 2017, at 13:01, Charles R Harris wrote: > On Tue, Mar 28, 2017 at 5:16 PM, Nathaniel Smith > wrote: >> In case anyone is interested in helping run a NumPy sprint at SciPy >> this year: > > I haven't found numpy sprints to be very productive. However, I think > it would be useful

Re: [Numpy-discussion] Boolean binary '-' operator

Hi Chuck On Sun, Jun 25, 2017, at 09:32, Charles R Harris wrote: > The boolean binary '-' operator was deprecated back in NumPy 1.9 and > changed to an error in 1.13. This caused a number of failures in > downstream projects. The choices now are to continue the deprecation > for another couple of

Re: [Numpy-discussion] Scipy 2017 NumPy sprint

On Thu, Jun 29, 2017, at 11:09, Charles R Harris wrote: > > On Thu, Jun 29, 2017 at 12:07 PM, Charles R Harris > wrote:>> I will be running the NumPy sprint at > Scipy 2017 and I'm trying to >> put together a suitable list of things to sprint on. In my >> experience, sprinting on NumPy is hard,

Re: [Numpy-discussion] Generalized rectangle intersection. (Was: Array blitting)

On Mon, Jul 10, 2017, at 01:34, Jerome Kieffer wrote: > On Sun, 9 Jul 2017 23:35:58 +0200 > Mikhail V wrote: > > > disclaimer: I am not a past contributor to numpy and I don't know > > much about github, and what pull request means. So I just put the > > examples here. > > > > So in short, the p

Re: [Numpy-discussion] ENH: Proposal to add np.neighborwise in PR#9514

On Fri, Aug 4, 2017, at 19:54, Tim Cera wrote: > As noted https://github.com/numpy/numpy/pull/303 a large part of this > functionality has been implemented before for numpy and didn't go > anywhere because it is already present in scipy.ndimage.> > IMHO it is better suited in numpy with a better n

[Numpy-discussion] NumPy default citation

Hi, everyone I see that the NumPy homepage does not have a "Citation" section. Furthermore, on scipy.org, the default NumPy citation points to a short summary paper that I wrote with Gael V & Stephen C. While it's a reasonable introduction to three core concepts behind NumPy, attribution should

Re: [Numpy-discussion] NumPy default citation

On Tue, Sep 5, 2017, at 13:25, Charles R Harris wrote: > > On Tue, Sep 5, 2017 at 12:36 PM, Stefan van der Walt > wrote:>> Shall we add a citation to Travis's "Guide > to NumPy (2nd ed.)" >> on both> > What is the citation for? It's the su

Re: [Numpy-discussion] numpy grant update

On Thu, Oct 19, 2017, at 23:11, Ralf Gommers wrote: > Thanks Nathaniel. I'm looking forward to all of those people getting > involved. Hiring always takes longer than you want, but next year the > pace of development promises to pick up significantly:) I'm excited for the opportunity to dedicate ti

Re: [Numpy-discussion] Proposal of timeline for dropping Python 2.7 support

On Mon, Nov 13, 2017, at 10:26, Matthias Bussonnier wrote: > Unless the sdist is tagged with require_python and users have > recent-enough pip. Is this documented anywhere? I couldn't find it via Google, and suspect it may be widely useful in the next few months. Stéfan _

Re: [Numpy-discussion] Proposal of timeline for dropping Python 2.7 support

On Fri, Nov 17, 2017, at 13:12, Chris Barker wrote: > On Fri, Nov 17, 2017 at 4:35 AM, Peter Cock > wrote:>> Since Konrad Hinsen no longer follows > the NumPy discussion list >> for lack of time, he has not posted here - but he has commented >> about this on Twitter and written up a good blog p

Re: [Numpy-discussion] Deprecate matrices in 1.15 and remove in 1.17?

On Thu, Nov 30, 2017, at 10:13, josef.p...@gmail.com wrote: > recarrays are another half-hearted feature in numpy that is mostly > obsolete with pandas and pandas_like DataFrames in other > packages. I'm fully on board with factoring out np.matrix into a subpackage. But I would not touch structure

Re: [Numpy-discussion] Deprecate matrices in 1.15 and remove in 1.17?

On Thu, Nov 30, 2017, at 11:39, Charles R Harris wrote: > Agree, we don't want to pile in too many changes at once. I think the big > sticking point is the sparse matrices in SciPy, even issuing a > DeprecationWarning could be problematic as long as there are sparse matrices. Could you explain w

Re: [Numpy-discussion] Deprecate matrices in 1.15 and remove in 1.17?

On Thu, Nov 30, 2017, at 12:02, Marten van Kerkwijk wrote: > I think Josef specifically meant `recarrays`, which give access to > elements of a structured array via attribute access. I'd tend to agree > with him that those turned out not to be such a great idea. But (I > think) nobody is arguing we

Re: [Numpy-discussion] Deprecate matrices in 1.15 and remove in 1.17?

On Thu, Nov 30, 2017, at 16:15, Nathaniel Smith wrote: > PendingDeprecationWarning in np.matrix.__init__ (unless it kills > performance for scikit-learn and friends), and put a big warning box > at the top of the docs. The idea here is to not actually break > anyone's code, but start to get out the

Re: [Numpy-discussion] NEP process PR

On Mon, Jan 1, 2018, at 17:39, Ralf Gommers wrote: > > On Wed, Dec 13, 2017 at 11:45 AM, Jarrod Millman > wrote:>> Hi all, >> >> I've started working on the proposal discussed in this thread: >> >> https://mail.python.org/pipermail/numpy-discussion/2017-December/077481.html>> >> here: >>

[Numpy-discussion] Position at BIDS (UC Berkeley) to work on NumPy

Hi everyone, Chuck suggested that I send a reminder that the Berkeley Institute for Data Science (BIDS) is hiring scientific Python Developers to contribute to NumPy. You can read more about the new positions here: https://bids.berkeley.edu/news/bids-receives-sloan-foundation-grant-contribute-

Re: [Numpy-discussion] Multiple-field indexing: view vs copy in 1.14+

On Mon, 22 Jan 2018 10:11:08 -0500, Marten van Kerkwijk wrote: I think on the consistency argument is perhaps the most important: views are very powerful and in many ways one *counts* on them happening, especially in working with large arrays. I had the same gut feeling, but the fancy indexing

Re: [Numpy-discussion] Setting custom dtypes and 1.14

On Mon, 29 Jan 2018 14:10:56 -0500, josef.p...@gmail.com wrote: Given that there is pandas, xarray, dask and more, numpy could as well drop any pretense of supporting dataframe_likes. Or, adjust the recfunctions so we can still work dataframe_like with structured dtypes/recarrays/recfunctions.

Re: [Numpy-discussion] Hoop jumping, and other sports

On Wed, 07 Feb 2018 14:26:37 -0700, Charles R Harris wrote: > I was thinking about things to do to simplify the NumPy development > process. One thing that came to mind was our use of prefixes on commits, > BUG, TST, etc. Those prefixes were originally introduced by David > Cournapeau when he was m

Re: [Numpy-discussion] Where to discuss NEPs (was: Re: new NEP: np.AbstractArray and np.asabstractarray)

On Thu, 08 Mar 2018 20:22:29 -0800, Nathaniel Smith wrote: > 1. We merge updates to the NEPs as we go, so that whatever's in the > repo is the current draft. Anyone can go to the NEP webpage at > http://numpy.org/neps (WIP, see #10702) to see the latest version of > all NEPs, whether accepted, reje

Re: [Numpy-discussion] Where to discuss NEPs (was: Re: new NEP: np.AbstractArray and np.asabstractarray)

On Fri, 09 Mar 2018 17:00:43 +, Stephan Hoyer wrote: > I'll note that we basically used GitHub for revising __array_ufunc__ NEP, > and I think that worked out better for everyone involved. The discussion > was a little too specialized and high volume to be well handled on the > mailing list. A

[Numpy-discussion] NEP sprint: 21 and 22 March

Hi everyone, As you may have noticed, there's been quite a bit of movement recently around NumPy Enhancement Proposals---on setting specifications, building infrastructure, as well as writing new proposals. To further support this work, we will be hosting an informal NEP sprint at Berkeley on 21

Re: [Numpy-discussion] NEP sprint: 21 and 22 March

Hi everyone, A quick reminder of the NEP sprint that will happen at Berkeley next Wednesday and Thursday. Please let me know if you are interested in joining. Best regards Stéfan On Fri, 09 Mar 2018 15:26:38 -0800, Stefan van der Walt wrote: > Hi everyone, > > As you may have noticed

[Numpy-discussion] Introduction: NumPy developers at BIDS

Hi everyone, I am excited to report that we have completed the hiring of two full time NumPy developers at BIDS [0]. Matti Picus has done extensive work on the PyPy project and specifically cpyext, their C compatibility layer that allows PyPy to run NumPy. In the course of this work, Matti has a

Re: [Numpy-discussion] Introduction: NumPy developers at BIDS

On Fri, 06 Apr 2018 07:42:34 -0600, Charles R Harris wrote: > On Fri, Apr 6, 2018 at 12:08 AM, Stefan van der Walt > wrote: > > We are very excited about this opportunity to develop NumPy further, > > together with the NumPy community, and look forward to making in-person &g

Re: [Numpy-discussion] Introduction: NumPy developers at BIDS

Hi Eric, On Sun, 08 Apr 2018 08:02:19 -1000, Eric Firing wrote: > On 2018/04/07 9:19 PM, Stefan van der Walt wrote: > > We would love community input on identifying the best areas & issues to > > pay attention to, > > What is the best way to provide this, and how wil

Re: [Numpy-discussion] Introduction: NumPy developers at BIDS

On Tue, 10 Apr 2018 10:03:06 -0700, Nathan Goldbaum wrote: > You may want to explore other venues for this sort of feedback, e.g. a > SciPy BoF session, which will capture a different subset of the > community. Thanks for the suggestion, Nathan. We are coordinating with SciPy2018 to have both a B

Re: [Numpy-discussion] Introduction: NumPy developers at BIDS

Hi Matthew, On Wed, 18 Apr 2018 16:42:49 +0100, Matthew Brett wrote: > Hum - I see the Trello board is for bite- to meal- size practical > issues, but not for the general process of how to engage the community > in guiding the the project - is that fair? That's correct; it's just another window o

Re: [Numpy-discussion] Splitting MaskedArray into a separate package

On Wed, 23 May 2018 12:29:32 -0700, Ralf Gommers wrote: > >> * Compatibility: MaskedArray objects, being subclasses of `ndarrays`, > >>often cause complications when being used with other packages. > >>Fixing these issues is outside the scope of NumPy development. > > > Hmm, I wouldn't say

Re: [Numpy-discussion] Splitting MaskedArray into a separate package

Hi Eric, On May 23, 2018 13:25:44 Eric Firing wrote: On 2018/05/23 9:06 AM, Matti Picus wrote: I understand at least some of the motivation and potential advantages, but as it stands, I find this NEP highly alarming. I am not at my computer right now, so I will respond in more detail later.

Re: [Numpy-discussion] Splitting MaskedArray into a separate package

On May 23, 2018 14:28:05 Matthew Brett wrote: Can I ask what the plans are for supporting missing values, inside or outside numpy? Is there are successor to MaskedArray - and is this part of the succession plan? I am not aware of any concrete plans, maybe others can chime in? It's a bit str

Re: [Numpy-discussion] Splitting MaskedArray into a separate package

On Wed, 23 May 2018 13:30:49 -0700, Ralf Gommers wrote: > > Good point, which certainly needs to be discussed. My thought was to > > move it out into a separate package that could be maintained more in the > > spirit of a scikit by people who care deeply about its functionality. > > > That would b

Re: [Numpy-discussion] Splitting MaskedArray into a separate package

Hi Eric, On Wed, 23 May 2018 10:02:22 -1000, Eric Firing wrote: > Masked arrays are critical to my numpy usage, and I suspect they are > critical for many other use cases as well. That's good to know; and the goal of this NEP should be to improve your siatuion, not make it worse. > In fact, I wo

Re: [Numpy-discussion] Citation for ndarray

Hi Nathan, On Thu, 24 May 2018 13:13:16 -0500, Nathan Goldbaum wrote: > I see listed on the scipy.org site that the preferred citation for NumPy is > the "Guide to NumPy": > > https://www.scipy.org/citing.html > > This could work for what I'm writing, but I'd prefer to find a citation > specific

Re: [Numpy-discussion] NumPy sprint May 24-25 at BIDS

Hi Jaime, On Thu, 24 May 2018 10:01:40 -0700, Jaime Fernández del Río wrote: > I will be there tomorrow for sure, though. What time do you plan on > starting? Thanks for the heads-up. We'll probably start around 9:30am. We're at 190 Doe Library on Berkeley campus. We started today by discussin

Re: [Numpy-discussion] A roadmap for NumPy - longer term planning

Hi Ralf, On Thu, 31 May 2018 21:57:06 -0700, Ralf Gommers wrote: > - "internal refactorings": MaskedArray yes, but the other ones no. > numpy.distutils and f2py are very hard to test, a big refactor pretty much > guarantees breakage. there's also not much need for refactoring, because > those thin

[Numpy-discussion] Roadmap proposal, v3

Hi everyone, Please take a look at the latest roadmap proposal: https://github.com/numpy/numpy/pull/11611 This is a living document, so can easily be modified in the future, but we'd like to get in place a document that corresponds fairly closely with current community priorities. Best regards,

Re: [Numpy-discussion] Roadmap proposal, v3

Hi Chris, On Wed, 25 Jul 2018 08:13:26 -0700, Chris Barker - NOAA Federal wrote: > For example, I am very wary of putting a non-fixed width encoding (e.g. > Utf-8) in a fixed width field. > > But this PR is not the place to discuss that. Since you've followed that discussion closely, can you pus

[Numpy-discussion] Adoption of a Code of Conduct

Hi everyone, A while ago, SciPy (the library) adopted its Code of Conduct: https://docs.scipy.org/doc/scipy/reference/dev/conduct/code_of_conduct.html We worked hard to make that document friendly, while at the same time stating clearly the kinds of behavior that would and would not be tolerated.

Re: [Numpy-discussion] Adoption of a Code of Conduct

On July 27, 2018 17:04:23 Marten van Kerkwijk wrote: My ideal version would be substantially shorter, maybe just quote the golden rule, but I am happy with the suggestion to just adapt this text. Agreed! There's some basic ground that needs to be covered, though, and the result of exploring

Re: [Numpy-discussion] Adoption of a Code of Conduct

On August 3, 2018 09:50:38 Robert Kern wrote: On Thu, Aug 2, 2018 at 11:01 PM Robert Kern wrote: Nope, concision is definitely not my strength. But I hope I made the argument clear, at least. No, wait. I got it: Bad actors use "diversity of political beliefs" in bad faith as cover for und

Re: [Numpy-discussion] Adoption of a Code of Conduct

On August 3, 2018 10:35:57 Stefan van der Walt wrote: On August 3, 2018 09:50:38 Robert Kern wrote: On Thu, Aug 2, 2018 at 11:01 PM Robert Kern wrote: Nope, concision is definitely not my strength. But I hope I made the argument clear, at least. No, wait. I got it: Bad actors use

Re: [Numpy-discussion] Adoption of a Code of Conduct

On August 3, 2018 20:51:00 Chris Barker wrote: I'll note that at least the Contributor Covenant is pretty vague about enforcement: """ All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. """ I'd think

Re: [Numpy-discussion] Adoption of a Code of Conduct

Hi Matthew, On August 4, 2018 00:23:44 Matthew Harrigan wrote: One concern I have is the phrase "explicitly honour" in "we explicitly honour diversity in: age, culture, ...". Honour is a curious word choice. honour is defined as, among other things, "to worship", "high public esteem; fame;

Re: [Numpy-discussion] Adoption of a Code of Conduct

On August 15, 2018 06:31:08 Ralf Gommers wrote: On Fri, Aug 3, 2018 at 1:02 PM, Charles R Harris wrote: I prefer that to the proposed modification, short and sweet. This edit to the SciPy CoC has now been merged. It looks to me like we're good to go here and take over the SciPy CoC. +1

Re: [Numpy-discussion] rescuing missing data documents

On September 2, 2018 06:16:36 Ralf Gommers wrote: I'd like to see the NEPs rescued, and the summary moved from the numpy.org repo (maybe into yet another NEP?). It would be best if the original authors do this, but otherwise I'm happy to do it. Thoughts? I think this is an excellent suggestio

Re: [Numpy-discussion] Adding `max_rows` to `loadtxt'

It looks good to me too, to especially with Eric's refinements. Best regards, Stéfan On September 16, 2018 21:23:44 Stephan Hoyer wrote: This seems like a minor and uncontroversial improvement. No objections from me! On Sun, Sep 16, 2018 at 2:01 PM Matti Picus wrote: A new contributor submit

Re: [Numpy-discussion] Tidelift

On Tue, 18 Sep 2018 16:54:16 -0500, Andy Ray Terrel wrote: > FYI, Donald Fischer will be at the NumFOCUS forum next week if folks want > to talk to him about it. It looks like individuals sign up with Tidelift > and perform services to be paid this money. Looking at the contract it > doesn't seem l

Re: [Numpy-discussion] PR Cleanup

On Tue, 25 Sep 2018 09:51:13 -0600, Charles R Harris wrote: > As usual, the top of the PR stack is getting all the attention. As a start > on cleaning up the old PRs, I'd like to suggest that all the maintainers > look at their (long) pending PRs and decide which they want to keep, close > those th

[Numpy-discussion] BIDS/NumPy dev meetings, Wednesdays 12pm Pacific

Hi everyone, The team at BIDS meets once a week to discuss progress, priorities, and roadblocks. While our priorities are broadly determined by the project roadmap [0], we would like to provide an opportunity for the community to give more regular and detailed feedback on our work. We therefore

Re: [Numpy-discussion] BIDS/NumPy dev meetings, Wednesdays 12pm Pacific

Hi everyone, This is a friendly reminder of the BIDS/NumPy dev meetings, kicking off tomorrow at 12pm Pacific time. Please add any topics you wish to discuss to the agenda linked below. Best regards, Stéfan On Thu, 11 Oct 2018 22:43:58 -0700, Stefan van der Walt wrote: > The team at B

Re: [Numpy-discussion] Approving NEP 27 - Historical discussion of 0-D arrays

On Wed, 17 Oct 2018 20:58:55 +0300, Matti Picus wrote: > http://www.numpy.org/neps/nep-0027-zero-rank-arrarys.html. There was > fruitful discussion of the NEP and the need for both 0-D arrays and scalars > on the PR comments. Were those comments integrated back into the NEP? If not, can we add a

Re: [Numpy-discussion] BIDS/NumPy dev meetings, Wednesdays 12pm Pacific

Thank you to everyone who attended the development meeting this week. We've posted the agenda/notes online at: https://github.com/BIDS-numpy/docs/blob/master/status_meetings/status-2018-10-17.md On Tue, 16 Oct 2018 14:26:57 -0700, Stefan van der Walt wrote: > Hi everyone, > > This

Re: [Numpy-discussion] Reminder: weekly status meeting

Hi all, On Mon, 22 Oct 2018 09:56:37 +0300, Matti Picus wrote: > We therefore invite you to join us for our weekly calls, > each **Wednesday from 12:00 to 13:00 Pacific Time**. > > Detail of the next meeting (2018-10-24) is given in the agenda This week's meeting notes are at: https://github.co

Re: [Numpy-discussion] Reminder: weekly status meeting

Hi Hameer, On Fri, 26 Oct 2018 10:47:09 +0200, Hameer Abbasi wrote: > The only core functionality dependent on scipy.sparse is matrix > multiplication and the like. Everything else is for inter-operability. Thank you for commenting here. As you know, I am enthusiastic about seeing an `sparray` e

Re: [Numpy-discussion] Depreciating asfortranarray and ascontiguousarray

On Thu, 25 Oct 2018 19:02:20 -0700, Stephan Hoyer wrote: > I would also advocate for fixing these functions if possible (removing > ndim=1). ascontiguousarray(...) is certainly more readable than asarray(... > order='C'). I agree; these are widely used, and makes intuitive sense as part of the API

Re: [Numpy-discussion] Reminder: weekly status meeting

On Sat, 27 Oct 2018 10:27:49 +1300, Ralf Gommers wrote: > Just to make sure we're talking about the same things here: Stefan, I think > with "sparray" you mean "an n-D sparse array implementation that lives in > SciPy", nothing more specific? In that case pydata/sparse is the one > implementation,

Re: [Numpy-discussion] Reminder: weekly status meeting 31.10 at 12:00 pacific time

Hi Hameer, On Tue, 30 Oct 2018 21:24:36 +0100, Hameer Abbasi wrote: > If I may make a suggestion, it might be nice to create a separate > calendar and add people to it as needed for better management. Can you clarify what you want? Do you mean we should not announce the meeting agenda here, and

Re: [Numpy-discussion] Reminder: weekly status meeting 31.10 at 12:00 pacific time

On Tue, 30 Oct 2018 23:56:17 +0100, Hameer Abbasi wrote: > I meant we should have a calendar that’s possible to subscribe to, and > in addition announce the agenda here, and that the calendar could > contain a link to the meeting agenda. Here you go: https://calendar.google.com/calendar?cid=YmVya

Re: [Numpy-discussion] Prep for NumPy 1.16.0 branch

On Sun, 04 Nov 2018 17:16:12 -0800, Stephan Hoyer wrote: > On Sun, Nov 4, 2018 at 10:32 AM Marten van Kerkwijk < > m.h.vankerkw...@gmail.com> wrote: > > > For `__array_function__`, there was some discussion in > > https://github.com/numpy/numpy/issues/12225 that for 1.16 we might want > > to follo

Re: [Numpy-discussion] numpy pprint?

On Tue, 06 Nov 2018 12:11:13 -0800, Robert Kern wrote: > Popular, but quite misleading, in the same way that not every 2-dim array > is a matrix. As someone who works on tensor machine learning methods once > complained to me. Are you referring to vectors, structured arrays, or something else? St

[Numpy-discussion] Developer Meeting, Berkeley, 30 Nov / 1 Dec

Hi everyone, On Friday 30 November & Saturday 1 December we will host a NumPy Development Meeting at the Berkeley Institute for Data Science. We will discuss the work being done on dtypes, review NEPs under implementation, and solicit feedback for updating the community roadmap. Please get in to

Re: [Numpy-discussion] Weekly status meeting 8.11 at 12:00 pacific time

On Tue, 06 Nov 2018 16:28:36 -0800, Matti Picus wrote: > We will be holding our weekly BIDS NumPy status meeting on Thurs Nov 8 at > noon pacific time. The meeting notes are now posted at https://github.com/BIDS-numpy/docs/blob/master/status_meetings/status-2018-11-08.md Stéfan __

Re: [Numpy-discussion] Reminder: Numpy dev meeting Fri-Sat Nov 30-Dec 1

On Wed, 28 Nov 2018 22:17:59 +0100, Hameer Abbasi wrote: > Just want to add that I’ll be available remotely for some of the > time. You can reach me via email and we can set up a call. Thank you, Hameer! Stéfan ___ NumPy-Discussion mailing list NumPy-Di

Re: [Numpy-discussion] Reminder: Numpy dev meeting Fri-Sat Nov 30-Dec 1

On Wed, 28 Nov 2018 17:34:51 -0600, Travis Oliphant wrote: > I am particularly interested in how to improve the dtype subsystem --- > potentially using libndtypes from the xnd project. We'd love to hear your opinion on the matter, and can set up a Zoom call for that purpose. Please let me know of

Re: [Numpy-discussion] Adding "maximum difference" to np.testing.assert_array_equal errors

On Wed, 19 Dec 2018 09:47:01 -0800, Stephan Hoyer wrote: > Example behavior: > > >>> x = np.array([1, 2, 3]) > >>> y = np.array([1, 2, 3.0001]) > >>> np.testing.assert_allclose(x, y) > AssertionError: > Not equal to tolerance rtol=1e-07, atol=0 > > (mismatch 33.336%, maximum differenc

Re: [Numpy-discussion] timedelta64 remainder behavior with div by 0

On Tue, 08 Jan 2019 09:57:03 -0800, Tyler Reddy wrote: > np.timedelta64(5) % np.timedelta64(0) -> numpy.timedelta64(0) > > In contrast, np.float64(1) % np.float64(0) -> nan > > There's a suggestion that we should switch to returning NaT for the > timedelta64 case for consistency, and that this pr

Re: [Numpy-discussion] Numpy-discussion

On Tue, 29 Jan 2019 10:15:00 +0200, Matti Picus wrote: > 2000*2000*2000 overflows a 32 bit signed integer, so it wraps around to a > negative value. I was curious about what happens, bit-wise, in this case. We are dealing with a signed integer, so I presume of the 33 bits in 2000**3, only 32 are

[Numpy-discussion] Outreachy internship

Hi everyone, The team at BIDS would like to take on an intern from Outreachy (https://www.outreachy.org), as part of our effort to grow the NumPy developer community. The internship is similar to a GSoC, except that we will pay their salary, as well as do the mentoring. We wanted to check in bef

Re: [Numpy-discussion] NEP-18 comment

It's great to have your input here, Frederic—thank you! On Wed, 06 Mar 2019 12:41:11 -0800, Stephan Hoyer wrote: > I agree, this seems like an easy and worthwhile change. The NEP-18 > implementation has been rewritten in C, so I expect that the typical > overhead will be quite minimal (about 1 us

Re: [Numpy-discussion] NEP-18 comment

Hi Sebastian, Frederic, On Thu, 07 Mar 2019 14:23:10 +, Frederic Bastien wrote: > I like your idea Sebastian. This way it is enabled only when needed and it is > invisible to the user at the same time. > > Stefan, does it solve well enough the potential problem you raised? I don't think so.

[Numpy-discussion] #4808 -- let np.pad default to constant

In PR 4808, I propose changing the default padding mode (for `np.pad`) to constant (0). It was suggested that I mention the change here, in case someone has a use case or argument for not making it. https://github.com/numpy/numpy/pull/4808 Thanks! Stéfan _

[Numpy-discussion] NumPy sprint at BIDS: May 10/11

Hi everyone, On May 10/11, we will host another NumPy sprint at the Berkeley Institute for Data Science. The focus of this meeting will be the design of a new data type system, and to consolidate: - https://github.com/numpy/numpy/pull/12630 [Matti's NEP PR WIP] - https://hackmd.io/ok21UoAQQmOtSV

[Numpy-discussion] prpp report—please help review!

Hi everyone, During the community call today, we drew up a list of open PR counts per developer. We are working towards bringing down their number (around 240 today), and would appreciate it if you could help us review and/or make decisions. NumPy also has 1760 open issues

Re: [Numpy-discussion] prpp report—please help review!

On Wed, Mar 20, 2019, at 13:30, Ralf Gommers wrote: > All the links to PRs below are broken - if you have a script that's easy to > change, could you resend with fixed links? Sorry, looks like I posted the API endpoints. Here's a working version, including everyone with >= 5 PRs: *Top 10 PR con

Re: [Numpy-discussion] proposal of new keywords for np.nan_to_num

On Thu, Apr 4, 2019, at 10:12, kikocorreoso wrote: > I propose to add some keywords to nan_to_num function. The addition do not > modify the actual behavior. Information related with this addition can be > found in these links: > https://github.com/numpy/numpy/pull/13219 > https://github.com/nump

Re: [Numpy-discussion] Behaviour of copy for structured dtypes with gaps

Hi Marten, On Thu, 11 Apr 2019 09:51:10 -0400, Marten van Kerkwijk wrote: > From the discussion so far, it > seems the logic has boiled down to a choice between: > > (1) Copy is a contract that the dtype will not vary (e.g., we also do not > change endianness); > > (2) Copy is a contract that an

Re: [Numpy-discussion] Behaviour of copy for structured dtypes with gaps

On Fri, 12 Apr 2019 12:13:18 -0400, Allan Haldane wrote: > I would be much more in favor of `copy` eliminating padding in the > dtype, if dtypes with different paddings were considered equivalent. > But they are not. This, and the simplicity arguments, are fair points. Option (1) seems like the s

Re: [Numpy-discussion] Adding to the non-dispatched implementation of NumPy methods

On Mon, 15 Apr 2019 08:30:06 -0700, Stephan Hoyer wrote: > We have a proposed a revision to NEP-18 (__array_function__). The proposal > is for an adding an alias to the non-dispatched version of NumPy array > functions in the __numpy_implementation__ function attribute: > https://github.com/numpy/n

Re: [Numpy-discussion] Adding to the non-dispatched implementation of NumPy methods

I thought this was simply a slot to store the NumPy version of the dispatched method, so that you could see easily call through to it and extend it. Stephan, was there a deeper intent here that I missed? Best regards, Stéfan On April 15, 2019 20:32:35 Nathaniel Smith wrote: On Mon, Apr 15,

Re: [Numpy-discussion] Boolean arrays with nulls?

Hi Stuart, On Thu, 18 Apr 2019 09:12:31 -0700, Stuart Reynolds wrote: > Is there an efficient way to represent bool arrays with null entries? You can use the bool dtype: In [5]: x = np.array([True, False, True])

[Numpy-discussion] Sebastian Berg at BIDS

Hi everyone, We are happy to announce that Sebastian Berg has joined the team at BIDS, and will be working full-time on NumPy for the next two years. Sebastian has been a core contributor to the project for seven years already, and we are delighted that he will now be able to spend even more of hi

Re: [Numpy-discussion] Proposed change in construction of structured dtypes with a shape-(1, ) field

Hi Anthony, On Mon, 20 May 2019 16:51:54 +0200, Antony Lee wrote: > In #13112/#13326, I proposed to change the semantics of constructing > structured dtypes with a shape-(1,) field (with a deprecation period). > Currently, a construct like `np.empty(1, ("a", int, 1))` is treated as a > shape-() fi

Re: [Numpy-discussion] Community Call -- May 22 (New time / platform)

Hi all, On Tue, 21 May 2019 10:06:30 -0700, Tyler Reddy wrote: > Hi, > > Starting from this week, the community meetings will be at a new time (11 > am Pacific Time) and on a new meeting platform (see the linked doc). > > Anyone is free to join and edit the work-in-progress meeting notes: > http

Re: [Numpy-discussion] __skip_array_function__ discussion summary

On Thu, 23 May 2019 14:33:17 -0700, Sebastian Berg wrote: > Those two options further have very different goals in mind for the > final usage of the protocol. So that right now the solution is to step > back, not include the addition and rather gain experience with the > NumPy 1.17 release that inc

Re: [Numpy-discussion] numpy.org/neps not refreshing

Hi Matti, On Mon, 27 May 2019 23:05:26 +0300, Matti Picus wrote: > Could someone who is an admin to > the numpy organization try to work out what is going on? It would be nice to > be able to point to the updated roadmap and neps. You should have push rights now; but let's not update the pages ri

Re: [Numpy-discussion] defining a NumPy API standard?

Hi Marten, On Sat, 01 Jun 2019 12:11:38 -0400, Marten van Kerkwijk wrote: > Third, we could actual implementing the logical groupings identified in the > code base (and describing them!). Currently, it is a mess: for the C files, > I typically have to grep to even find where things are done, and w

Re: [Numpy-discussion] Extent to which to work around matrix and other duck/subclass limitations

On Tue, 11 Jun 2019 15:10:16 -0400, Marten van Kerkwijk wrote: > In a way, I brought it up mostly as a concrete example of an internal > implementation which we cannot change to an objectively cleaner one because > other packages rely on an out-of-date numpy API. This, and the comments Nathaniel m

Re: [Numpy-discussion] New release note strategy after branching 1.17.

On Wed, 12 Jun 2019 15:57:48 -0400, Marten van Kerkwijk wrote: > Overall, in favour of splitting the large files, but I don't like that the > notes stop being under version control (e.g., a follow-up PR slightly > changes things, how does the note gets edited/reverted?). > > Has there been any dis

Re: [Numpy-discussion] keeping all meeting notes and docs in new repo?

Yes, that would make sense. The notes are there because of historic reasons, the meetings having originated as BIDS updates to the community, but by now it is much more open and community driven (thanks all!) so +1. Stéfan On September 16, 2019 21:16:18 Zijie Poh wrote: Hi all, I like the i

Re: [Numpy-discussion] Low-level API for Random

On Fri, Sep 20, 2019, at 21:30, Robert Kern wrote: > Given the prevalence of Cython, it's actually really easy to use the Python > API pretty easily in "C", so it's actually a huge waste if the C API matches > the Python API too closely. The power and utility of the C API will be in how > it *di

Re: [Numpy-discussion] Np.genfromtxt Problem

On Fri, Oct 4, 2019, at 10:31, Stephen P. Molnar wrote: > data = np.genfromtxt(files, usecols=(3), dtype=None, skip_header=8, > skip_footer=1, encoding=None) This seems like a good use case for `dask.dataframe.read_csv` [0]. Stéfan [0] https://examples.dask.org/dataframes/01-data-access.html#Re

Re: [Numpy-discussion] Unsupporting python3.5

On Thu, Oct 10, 2019, at 09:34, Charles R Harris wrote: > I think we can support 3.5 as long as we please, the question is how long we > *want* to support it. I don't plan to release 1.18 wheels for 3.5, but I'm > concerned about making 1.18 outright incompatible with 3.5. I would like to > see

Re: [Numpy-discussion] a new grant for NumPy and OpenBLAS!

Hi Ralf, On Thu, Nov 14, 2019, at 15:42, Ralf Gommers wrote: > I'm very pleased to announce that NumPy and OpenBLAS have received a joint > grant for $195,000 from the Chan Zuckerberg Initiative. Congratulations on receiving this grant! I am very happy to see more funded involvement in NumPy, a

[Numpy-discussion] Sprint, this Friday/Saturday (22/23 November)

Hi everyone, This is a reminder of the NumPy sprint that will be happening in Berkeley this Friday and Saturday, 22 and 23 November. The schedule for the sprint is at: https://hackmd.io/@GicvKC4NRbK9X9ElJTixwg/ryEPQyprr Best regards, Stéfan ___ NumPy

Re: [Numpy-discussion] welcome Shaloo Shalini to the NumPy team

On Fri, Nov 15, 2019, at 15:17, Ralf Gommers wrote: > Please welcome Shaloo Shalini to the NumPy team. Shaloo is an experienced > technology marketing consultant with a passion for open source. She has been > contributing graphical content, information mapping and technical writing > since the s

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

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, and we appreciate you taking the time to make it. As we look back ove

[Numpy-discussion] Tensor Developer Summit

Hi all, This has been mentioned on the community calls, but not on the mailing list, so a reminder about the Tensor Developer Summit happening at March in Berkeley: https://xd-con.org/tensor-2020/ We would love to have developers and advanced users of NumPy (or other array libraries with Pytho

Re: [Numpy-discussion] Tensor Developer Summit

Hi Neil, On Wed, Feb 19, 2020, at 11:43, Neal Becker wrote: > Sounds like an exciting group! Will it be streamed? Due to the highly interactive nature of this event, we will not be streaming. Best regards, Stéfan ___ NumPy-Discussion mailing list NumP

  1   2   >