[Numpy-discussion] make nditer also a context manager

When an nditer uses certain op_flags[0], like updateifcopy or readwrite or copy, the operands (which are ndarray views into the original data) must use the UPDATEIFCOPY flag. The meaning of this flag is to allocate temporary memory to hold the modified data and make the original data readonly.

[Numpy-discussion] nditer and updateifcopy semantics - advice needed

I filed issue 9714 trying to get some feedback on what to do with updateifcopy semantics and user-exposed nditer. For those who are unfamiliar with the issue see below for a short summary, issue 7054 for a lengthy discussion, or pull request 9639 (which is still not merged). As I mention in

Re: [Numpy-discussion] deprecate updateifcopy in nditer operand, flags?

On 10/11/17 12:25, numpy-discussion-requ...@python.org wrote: Date: Fri, 10 Nov 2017 02:25:19 -0800 From: Nathaniel Smith To: Discussion of Numerical Python Subject: Re: [Numpy-discussion] deprecate updateifcopy in nditer operand, flags?

Re: [Numpy-discussion] NumPy-Discussion Digest, Vol 134, Issue 10

On 04/11/17 18:00, numpy-discussion-requ...@python.org wrote: Date: Fri, 3 Nov 2017 20:56:38 -0600 From: Charles R Harris To: numpy-discussion Subject: [Numpy-discussion] NumPy 1.14 branch.

Re: [Numpy-discussion] deprecate updateifcopy in nditer operand, flags?

Date: Wed, 8 Nov 2017 18:41:03 +0200 From: Matti Picus <matti.pi...@gmail.com> To: numpy-discussion@python.org Subject: [Numpy-discussion] deprecate updateifcopy in nditer operand flags? Message-ID: <c46bfba8-bad8-5166-e580-456527042...@gmail.com> Content-Type

[Numpy-discussion] deprecate updateifcopy in nditer operand flags?

I filed issue 9714 https://github.com/numpy/numpy/issues/9714 and wrote a mail in September trying to get some feedback on what to do with updateifcopy semantics and user-exposed nditer. It garnered no response, so I am trying again. For those who are unfamiliar with the issue see below for a

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

A reminder - we will take advantage of a few NumPy developers being at Berkeley to hold a two day sprint May 24-25 https://scisprints.github.io/#may-numpy-developer-sprint . We invite any core contributors who would like to attend and

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

On 10/05/18 04:44, Charles R Harris wrote: On Wed, May 9, 2018 at 2:33 PM, Matti Picus <matti.pi...@gmail.com <mailto:matti.pi...@gmail.com>> wrote: A reminder - we will take advantage of a few NumPy developers being at Berkeley to hold a two day sprint May 24-

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

On 09/05/18 13:33, Matti Picus wrote: A reminder - we will take advantage of a few NumPy developers being at Berkeley to hold a two day sprint May 24-25 https://scisprints.github.io/#may-numpy-developer-sprint <https://scisprints.github.io/#may-numpy-developer-sprint>. We invite an

[Numpy-discussion] Splitting MaskedArray into a separate package

MaskedArray is a strange but useful creature. This NEP proposes to distribute it as a separate package under the NumPy brand. As I understand the process, a proposed NEP should be first discussed here to gauge general acceptance, then after that the details should be discussed on the pull

[Numpy-discussion] matmul as a ufunc

I have made progress with resolving the issue that matmul, the operation which implements `a @ b`, is not a ufunc [2]. Discussion on the issue, which prevents the __array_ufunc__ mechanism for overriding matmul on subclasses of ndarray, yeilded two approaches: - create a wrapper that can

[Numpy-discussion] NumPy 1.14.5 released

Hi All, I am pleased to announce the release of NumPy 14.4.5. This is a bugfix release for bugs reported following the 1.14.4 release. The most significant fixes are: * fixes for compilation errors on alpine and NetBSD The Python versions supported in this release are 2.7 and 3.4 - 3.6. The

[Numpy-discussion] Permissions to upload to PyPI

Almost ready to finish the 1.14.5 release, but it seems I need permissions to upload to PyPI (makes sense). My user name there is mattip. Can someone help out? Matti ___ NumPy-Discussion mailing list NumPy-Discussion@python.org

Re: [Numpy-discussion] SciPy 2018

On 12/06/18 14:26, Charles R Harris wrote: Hi All, Thought I'd raise the topic of meeting up at SciPy 2018. I wasn't planning on registering for the main conference, but would be happy to fly down for a couple of days if we plan on a meetup during sprints or some other point in the

[Numpy-discussion] Circle CI moving from 1.0 to 2.0

I stumbled across this notice (only seems to appear in a failed build) "This project is currently running on CircleCI 1.0 which will no longer be supported after August 31, 2018. Please start migrating this project to CircleCI 2.0 ." Here is the

[Numpy-discussion] 1.14.5 bugfix release

If there is a desire to do a bug-fix release 1.14.5 I would like to try my hand at releasing it, using doc/RELEASE_WALKTHROUGH.rst.txt. There were a few issues around compiling 1.14.4 on alpine and NetBSD. Since 1.15 will probably be released soon, do we continue to push

Re: [Numpy-discussion] rackspace ssl certificates

On 19/06/18 09:58, Charles R Harris wrote: > What I was curious about is that there were no more "daily" builds of > master.

Re: [Numpy-discussion] NEP: Dispatch Mechanism for NumPy’s high level API

On 05/06/18 14:11, Stephan Hoyer wrote: On Tue, Jun 5, 2018 at 12:35 PM Marten van Kerkwijk mailto:m.h.vankerkw...@gmail.com>> wrote: Things would, I think, make much more sense if `ndarray.__array_ufunc__` (or `*_function__`) actually *were* the implementation for array-only.

Re: [Numpy-discussion] rackspace ssl certificates

On 19/06/18 10:57, Matthew Brett wrote: Hi, On Tue, Jun 19, 2018 at 6:27 PM, Matti Picus wrote: On 19/06/18 09:58, Charles R Harris wrote: What I was curious about is that there were no more "daily" builds of master. Is that right? That there were daily builds of master, on A

Re: [Numpy-discussion] Extending ufunc signature syntax for matmul, frozen dimensions

On 01/05/18 21:08, Marten van Kerkwijk wrote: Just for completeness: there are *four* gufuncs (matmat, matvec, vecmat, and vecvec). I remain torn about the best way forward. The main argument against using them inside matmul is that in order to decide which of the four to use, matmul has to

Re: [Numpy-discussion] Extending ufunc signature syntax for matmul, frozen dimensions

On 01/05/18 01:45, Allan Haldane wrote: On 04/29/2018 05:46 AM, Matti Picus wrote: In looking to solve issue #9028 "no way to override matmul/@ if __array_ufunc__ is set", it seems there is consensus around the idea of making matmul a true gufunc, but matmul can behave d

Re: [Numpy-discussion] Extending ufunc signature syntax for matmul, frozen dimensions

around one with axis insertion) - this is similar to how np.linalg already works. Eric ​ On Mon, 30 Apr 2018 at 14:34 Stephan Hoyer <sho...@gmail.com <mailto:sho...@gmail.com>> wrote: On Sun, Apr 29, 2018 at 2:48 AM Matti Picus <matti.pi...@gmail.com <mailto:matti.pi...

[Numpy-discussion] summary of "office Hours" open discusison April 25

Office Hours 25April 2018 12:00 -13:00 PDT Present: Matti Picus, Allan Haldane, Ralf Gommers, Matthew Brett, Tyler Reddy, Stéfan van der Walt, Hameer Abbasi Some of the people were not present for the entire discussion, audio was a little flaky at times. Topics: Grant background overview

[Numpy-discussion] Extending ufunc signature syntax for matmul, frozen dimensions

In looking to solve issue #9028 "no way to override matmul/@ if __array_ufunc__ is set", it seems there is consensus around the idea of making matmul a true gufunc, but matmul can behave differently for different combinations of array and vector: (n,k),(k,m)->(n,m) (n,k),(k) -> (n)

[Numpy-discussion] Remove sctypeNA and typeNA from numpy core

numpy.core has many ways to catalogue dtype names: sctypeDict, typeDict (which is precisely sctypeDict), typecodes, and typename. We also generate sctypeNA and typeNA but, as issue 11241 shows, it is sometimes wrong. They are also not documented and never used inside numpy. Instead of fixing

Re: [Numpy-discussion] Remove sctypeNA and typeNA from numpy core

On 21/06/18 09:25, Matti Picus wrote: numpy.core has many ways to catalogue dtype names: sctypeDict, typeDict (which is precisely sctypeDict), typecodes, and typename. We also generate sctypeNA and typeNA but, as issue 11241 shows, it is sometimes wrong. They are also not documented and never

[Numpy-discussion] NEP 15, 20 implementations waiting for review

Two largish pull requests that implement approved NEPS are waiting for review: https://github.com/numpy/numpy/pull/11175 for expanded gufunc signatures (NEP 20) https://github.com/numpy/numpy/pull/10915 for merging multiarray and umath c-extension modules (NEP 15) I realize reviewer time

Re: [Numpy-discussion] pytest, fixture and parametrize

On 08/08/18 17:34, Juan Nunez-Iglesias wrote: A NumPy document on preferred testing practices would be very valuable even to projects beyond NumPy, just like HOW_TO_DOCUMENT.txt was valuable to the entire ecosystem. We have these guidelines

Re: [Numpy-discussion] Proposal to accept NEP-18, __array_function__ protocol

On 15/08/18 19:44, Matthew Brett wrote: My suspicion is, to the extent that Matti and Tyler can devote time and energy to shepherding the discussion, these will become quicker and more productive. Since my name was mentioned .. Even if we could implement pull

[Numpy-discussion] Taking back control of the #numpy irc channel

Over the past few days spambots have been hitting freenode's IRC channels[0, 1]. It turns out the #numpy channel has no operator, so we cannot make the channel mode "|+q $~a"[2] - i.e. only registered freenode users can talk but anyone can listen. I was in touch with the freenode staff, they

Re: [Numpy-discussion] Proposal to accept NEP-18, __array_function__ protocol

On 29/08/18 10:37, Nathaniel Smith wrote: it's easy to imagine scenarios where the people being broken aren't the ones who had a chance to read the docs – e.g. if a major package starts relying on __array_function__, then it's all*their* users who we'd be breaking, even though they had nothing

[Numpy-discussion] we held an impromptu dtype brainstorming sesison at SciPy

The stars all aligned properly and some of the steering committee suggested we put together a quick brainstorming session over what to do with dtypes. About 20 people joined in the discussion which was very productive. We began with user stories and design requirements, and asked some present

Re: [Numpy-discussion] Commit privileges

On 19/07/18 14:08, Charles R Harris wrote: Hi All, The NumPy Steering Council has been looking at commit rights for the NumPy developers hired at BIDS. We would like them to be able to label PRs, close issues, and merge simple fixes; doing that requires commit privileges. OTOH, it is also

Re: [Numpy-discussion] Fwd: [NumFOCUS Projects] NumFOCUS Summit Registration

On 06/07/18 00:54, Ralf Gommers wrote: Hi all, In September the NumFOCUS Summit for 2018 will be held in New York. NumPy can send one representative (or a couple, but costs are only covered for one person). We opened this opportunity up to members of the Steering Council first, however it

Re: [Numpy-discussion] Looking for description/insight/documentation on matmul

On 09/07/18 09:48, jeff saremi wrote: Is there any resource available or anyone who's able to describe matmul operation of matrices when n > 2? The only description i can find is: "If either argument is N-D, N > 2, it is treated as a stack of matrices residing in the last two indexes and

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

I would love to join but I will be at the PyPy yearly sprint in Switzerland from Saturday to Wednesday, and traveling back to Israel on Thursday. I can join virtually Wednesday, my evening will be your morning. I begin traveling Thurs morning which is sometime Wed afternoon for you and will be

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

On 3/9/2018 8:26 AM, Ralf Gommers wrote: So my suggestion is discussion should happen on the list, and NEP updates should be merged promptly, or just self-merged. Sound good? Agreed that overall (1) is better than (2),

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

On 08/04/18 21:02, 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, Stefan, What is the best way to provide this, and how will the decisions be made? Eric

[Numpy-discussion] NumPy sprint May 24-25 at BIDS and virtual meetup tomorrow

at the discussion. Thanks, Matti Picus . ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion

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

On 18/04/18 21:21, Stefan van der Walt wrote: Hi Matthew, On Wed, 18 Apr 2018 16:42:49 +0100, Matthew Brett wrote: I was thinking about the engage community part, because it seems to me it would be good to spend time on that first, and if it was me, I think I'd go for more regular public

[Numpy-discussion] nditer as a context manager

|Hello all, PR #9998 (https://github.com/numpy/numpy/pull/9998/) proposes an update to the nditer API, both C and python. The issue (link) is that |||sometimes nditer uses temp arrays via the "writeback" mechanism, the data is copied back to the original arrays "when finished". However "when

Re: [Numpy-discussion] nditer as a context manager (reformatted?)

Hello all, PR #9998 (https://github.com/numpy/numpy/pull/9998/) proposes an update to the nditer API, both C and python. The issue (https://github.com/numpy/numpy/issues/9714) is that sometimes nditer uses temp arrays via the "writeback" mechanism, the data is copied back to the original

Re: [Numpy-discussion] Revised NEP-18, __array_function__ protocol

On 28/06/18 17:18, Stephan Hoyer wrote: On Thu, Jun 28, 2018 at 1:12 PM Marten van Kerkwijk mailto:m.h.vankerkw...@gmail.com>> wrote: For C classes like the ufuncs, it seems `__self__` is defined for methods as well (at least, `np.add.reduce.__self__` gives `np.add`), but not a

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

In PR 12166 https://github.com/numpy/numpy/pull/12166 we revived an old wiki document discussing the implementation of 0-dimensional arrays. This became informational NEP-27 http://www.numpy.org/neps/nep-0027-zero-rank-arrarys.html. There was fruitful discussion of the NEP and the need for

[Numpy-discussion] Removing priority labels from github

We currently have highest, high, normal, low, and lowest priority labels for github issues/PRs. At the recent status meeting, we proposed consolidating these to a single "high" priority label. Anything "low" priority should be merged or closed since it will be quickly forgotten, and no

[Numpy-discussion] asanyarray vs. asarray

Was there discussion around which of `asarray` or asanyarray` to prefer? PR 11162, https://github.com/numpy/numpy/pull/11162, proposes `asanyarray` in place of `asarray` at the entrance to `_quantile_ureduce_func` to preserve ndarray subclasses. Should we be

[Numpy-discussion] Reminder: weekly status meeting

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

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

The draft agenda is at https://hackmd.io/D3I3CdO2T9ipZ2g5uAChcA?both. Everyone is invited to join. Matti, Tyler and Stefan ___ NumPy-Discussion mailing list NumPy-Discussion@python.org

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

We will be holding our weekly BIDS NumPy status meeting on Thurs Nov 8 at noon pacific time. We moved the meeting to Thursday because of a scheduling conflict. Please join us. The draft agenda, along with details of how to join, is up at https://hackmd.io/TTurMvviSkarcxf8vURq-Q?both

Re: [Numpy-discussion] asarray/anyarray; matrix/subclass

On 9/11/18 5:09 pm, Nathaniel Smith wrote: On Fri, Nov 9, 2018 at 4:59 PM, Stephan Hoyer wrote: On Fri, Nov 9, 2018 at 6:46 PM Nathaniel Smith wrote: But matrix isn't the only problem with asanyarray. np.ma also violates Liskov. No doubt there are other problematic ndarray subclasses out

[Numpy-discussion] Weekly status meeting Nov 14 at 12:00 Pacific time

We will be holding our weekly BIDS NumPy status meeting on Wed Nov 14 at noon Pacific time. Please join us. The draft agenda, along with details of how to join, is up at https://hackmd.io/H0x6z5uYSgex2FA6p5nlvw?both Previous sessions' notes are available at

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

On 4/11/18 8:04 pm, Charles R Harris wrote: Hi All, Time to begin looking forward to the NumPy 1.16.x branch. I think there are three main topics to address: 1. current PRs that need review and merging, 2. critical fixes that need to be made, 3. status of `__array_function__`. The last

[Numpy-discussion] Adding a hex version like PY_VERSION_HEX

In PR 12074 https://github.com/numpy/numpy/pull/12074 I propose adding a function `version.get_numpy_version_as_hex()` which returns a hex value to represent the current NumPy version MAJOR.MINOR.MICRO where v = hex(MAJOR << 24 | MINOR << 16 | MICRO) so the current 1.15.0 would become

Re: [Numpy-discussion] Determining NPY_ABI_VERSION statically in compiled extensions

On 08/10/18 23:31, Robert T. McGibbon wrote: Is anyone aware of any tricks that can be played with tools like `readelf`, `nm` or `dlopen` / `dlsym` in order to statically determine what version of numpy a fully-compiled C extension (for example, found inside a wheel) was compiled against? Even

Re: [Numpy-discussion] Adding a hex version like PY_VERSION_HEX

On 05/10/18 11:46, Jerome Kieffer wrote: On Fri, 5 Oct 2018 11:31:20 +0300 Matti Picus wrote: In PR 12074 https://github.com/numpy/numpy/pull/12074 I propose adding a function `version.get_numpy_version_as_hex()` which returns a hex value to represent the current NumPy version

[Numpy-discussion] Reminder: weekly status meeting Jan 16 at 12:00 pacific time

The draft agenda is at https://hackmd.io/D_0X2QCjRpS-ENiFWokc-g?both# There is a section for community suggested topics, feel free to join the conversation and add in topics that need attention. The BIDS team ___ NumPy-Discussion mailing list

[Numpy-discussion] Reminder: weekly status meeting Dec 19 at 12:00 pacific time

The draft agenda is at https://hackmd.io/6N3r7yUtSHqUsijC-CEbJA?both Everyone is invited to join. Matti, Tyler and Stefan ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] three-dim array

On 27/12/18 3:21 am, Benjamin Root wrote: Ewww, kinda wish that would be an error... It would be too easy for a typo to get accepted this way. On Wed, Dec 26, 2018 at 1:59 AM Eric Wieser mailto:wieser.eric%2bnu...@gmail.com>> wrote: In the latest version of numpy, this runs without an

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

The draft agenda is at https://hackmd.io/Gn1ymjwkRjm9WVY5Cgbwsw?both Everyone is invited to join. Matti, Tyler and Stefan ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion

[Numpy-discussion] Warn or immidiately change readonly flag on broadcast_arrays return value?

In PR 12609 https://github.com/numpy/numpy/pull/12609 I added code to emit a DepricationWarning when broadcast_arrays returns an array where the output is repeated. While this is a minimal fix to the problem, perhaps we should consider making the output readonly immediately instead? - A

[Numpy-discussion] There will be no developer status meeting this week

I am traveling, so we decided to cancel this week's developer online meeting. The next one will be Wed Dec 19. Matti ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion

[Numpy-discussion] Weekly status meeting Nov 28 at 12:00 Pacific time

We will be holding our weekly BIDS NumPy status meeting on Wed Nov 28 at noon Pacific time. Please join us. The draft agenda, along with details of how to join, is up at https://hackmd.io/Gn1ymjwkRjm9WVY5Cgbwsw?both Previous sessions' notes are available at

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

We will be meeting at BIDS 9:00AM Friday for a two-day NumPy developer meeting. All are welcome, if you haven't already please let Stefan know you are coming so we can plan for space. A tentative schedule is here https://hackmd.io/gFqjPUSvSmm-0gmBDbrTBw?both Feel free to add content (just

[Numpy-discussion] Reminder: weekly status meeting Jan 9 at 12:00 pacific time

The draft agenda is at https://hackmd.io/D_0X2QCjRpS-ENiFWokc-g?both# There is a section for community suggested topics, feel free to join the conversation and add in topics that need attention. The BIDS team ___ NumPy-Discussion mailing list

Re: [Numpy-discussion] Debugging NumPy development build in conda environment

On 4/1/19 3:34 pm, Lars Grueter wrote: Unfortunately the last two commands stopped working out of the blue with my existing environment and fail with RuntimeError: Broken toolchain: cannot link a simple C program The compiler error is a few lines above this (copied below). When I have

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

A new contributor submitted a PR[0] to add `max_rows`[1] to `loadtxt`, like is done in 'genfromtxt', (which is used under the hood for 'ndfromtxt', 'mafromtxt', and 'recfromtxt`).  Any thoughts? [0] https://github.com/numpy/numpy/pull/11962 [1] Well, actually `maxlines`, but I asked to change

[Numpy-discussion] Search not working on www.numpy.org/devdocs/search.html

I can enter a search term (say `ndarray`) in www.numpy.org/devdocs/search.html, but the result is empty. It worked yesterday. My firefox javascript debug console for the remote search says: jQuery.Deferred exception: Search is not defined

[Numpy-discussion] Reminder: weekly status meeting Dec 19 at 12:00 pacific time

The draft agenda is at https://hackmd.io/Gn1ymjwkRjm9WVY5Cgbwsw?both This will be our last meeting of 2018. The BIDS team ___ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Beginner Help: Generating HTML using Sphinx

On 31/3/19 10:56 pm, Mbeng Tanyi wrote: Hello I also got an error the first time I tried $ make file as follows: mkdir -p build/html build/doctrees LANG=C sphinx-build -b html -WT --keep-going -d build/doctrees source build/html /bin/sh: 1: sphinx-build: not found

Re: [Numpy-discussion] My introduction to NumPy community

On 27/3/19 5:14 pm, Arpita Dash wrote: Hello, My name is Arpita Dash and I'm an Outreachy Applicant. I'm a CSE undergraduate. I am interested in contributing to the Numpy project "Improve C API documentation for Numpy." I am looking forward to working with Numpy and contributing to the

Re: [Numpy-discussion] Introducing Myself

On 25/3/19 4:08 pm, Vrinda Narayan wrote: Heyy, My name is Vrinda Narayan and I'm an Outreachy Applicant. I'm a CSE undergraduate and I know python, C, JavaScript and git. I am interested in contributing to the Numpy project Improve C API documentation for Numpy. I have used Numpy for various

Re: [Numpy-discussion] Outreachy Applicant

On 28/3/19 11:37 pm, Sargam Monga wrote: Hello everyone, I am Sargam, an undergrad from India.I am an outreachy applicant and would like to contribute to this project. On 28/3/19 7:37 pm, Aishwarya Dash wrote: Hi, I'm Aishwarya Dash, an applicant for Outreachy. I am quite interested to work

[Numpy-discussion] Removing undocumented __buffer__ attribute lookup

In digging around the code, I found a gem in PyArray_FromBuffer (exposed to python as numpy.frombuffer). If a PyObject* does not have a tp_as_buffer->bf_getbuffer function, we check if the python object has a __buffer__ attribute. If so we use that as buf in PyObject_GetBuffer(buf, ...).

[Numpy-discussion] Reminder: weekly status meeting Feb 27 at 12:00 pacific time

The draft agenda is at https://hackmd.io/TtqnUDvPQgaGeej7zR8seA?both# There is a section for community suggested topics, feel free to join the conversation and add in topics that need attention. Past meeting notes can be seen at https://github.com/BIDS-numpy/docs/tree/master/status_meetings

Re: [Numpy-discussion] Testing your contributions

On 16/3/19 9:59 am, Sandy wrote: Hey there, I am new to numpy. I just wanted to know, suppose I make a code contribution to the repo https://github.com/numpy/numpy how do I test its working? ___ Welcome. You should add a test. Running `python

Re: [Numpy-discussion] Outreachy applicant: Improve C API Documentation for Numpy

On 17/3/19 3:33 pm, Nisha Aggarwal wrote: Hello, I am an Outreachy applicant interested in the project: Improve C API Documentation for Numpy, but I am unsure of how to proceed. Can someone guide me here? Thanks Hi and welcome. The relevant issues have the DOC tag, you can see them via

Re: [Numpy-discussion] Outreachy applicant

On 12/3/19 2:22 pm, asish kr wrote: Hi,  i am an outreachy applicant and would like to contribute to this project.  Is there anyone who could guide me here. Thanks I responded privately to the applicant. More information about our Outreachy mentoring is here

[Numpy-discussion] Reminder: weekly status meeting Tues Feb 19 12:00 PST

This week the status meeting will be on Tues Feb 19 at 12:00 PST, not at the usual time The draft agenda is at https://hackmd.io/TtqnUDvPQgaGeej7zR8seA?both Everyone is invited to join. Matti, Tyler and Stefan ___ NumPy-Discussion mailing list

Re: [Numpy-discussion] Numpy-discussion

On 29/1/19 9:22 am, Yuping Wang wrote: Dear Nmupy developers and users:         I am a new user of Numpy ,I have encountered a question about Numpy recently, which need your help. The question is below:      I don  know why there are negative numbers      can somebody explain to me why

[Numpy-discussion] Reminder: weekly status meeting Jan 30 at 12:00 pacific time

The draft agenda is at https://hackmd.io/UnnvbPNpSm-gRpbfTK7cmg?both# There is a section for community suggested topics, feel free to join the conversation and add in topics that need attention. The BIDS team ___ NumPy-Discussion mailing list

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

When we merge a PR, a CI job on circleCI updates both https://github.com/numpy/neps and https://github.com/numpy/devdocs. These are meant to be served as github pages at http://www.numpy.org/neps/ and http://www.numpy.org/devdocs respectively. For some reason the devdocs is updating but the

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

On 1/6/19 7:31 pm, Charles R Harris wrote: I generally agree with this. The most useful aspect of this exercise is likely to be clarifying NumPy for its own developers, and maybe offering a guide to future simplification. Trying to put something together that everyone agrees to as an official

Re: [Numpy-discussion] (Value Based Promotion) Current Behaviour

On 14/6/19 1:37 am, Sebastian Berg wrote: For such a scalar object instead what would seem necessary is to call a `dtype.__coerce_pyvalue__(scalar, casting="safe")`, or a `__can_coerce_pyvalue__` method/slot. It would replace the current `PyArray_CanCastArrayTo`, which can only handle the

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

On 27/4/19 6:51 am, Marten van Kerkwijk wrote: Maybe it is best to just stick with __wrapped__ +1 for simplicity, clarity (since __wrapped__ is part of the |documented @functools.wraps() interface)|, and lowering expectations. Matti ___

Re: [Numpy-discussion] Contributing: NumPy Documentation

On 6/5/19 10:22 pm, Bhanu Bhandari wrote: Hello, I’m Bhanu, a third year student of Electronics and Computers Engineering. I’d like to get started with contributing into the NumPy documentation. I’m a writer who is actively machine learning research as well, and have used NumPy extensively

Re: [Numpy-discussion] GSoD'19 project discussion

On 6/5/19 4:51 pm, Oishika Pradhan wrote: Hi, I am Oishika Pradhan, a research student at IIIT Hyderabad, India. I am interested in machine learning and neural networks and hence have used numpy very regularly in my projects and

[Numpy-discussion] overhauling numpy.random and randomgen

Thanks to the work of Kevin Sheppard, Robert Kern and others, the branch to merge randomgen https://github.com/bashtage/randomgen into numpy is ready for final review. The branch is here https://github.com/numpy/numpy/pull/13163. It is fully backward compatible: numpy.random.mtrand,

[Numpy-discussion] Shippable builds are broken - I filed an issue with them

For the past few days shippable (arm builds) CI has been failing. I opened an issue with them https://github.com/Shippable/support/issues/4882 ___ NumPy-Discussion mailing list NumPy-Discussion@python.org

[Numpy-discussion] Using a pyproject.toml file

In PR #13908 I implemented the previously-discussed new method of creating the release notes: writing separate fragments and then combining them at release time via towncrier. Towncrier requires a PEP-508/PEP-517/PEP-518 pyproject.toml file for configuration, and

[Numpy-discussion] Top level release index page

In PR 13886 I reworked the way the link to the release notes is generated. The current page is http://www.numpy.org/devdocs/release.html and  the new page is https://8001-908607-gh.circle-artifacts.com/0/home/circleci/repo/doc/build/html/release.html I don't like the "wall of text" in

Re: [Numpy-discussion] Numpy twitter handle?

On 18/8/19 7:36 am, Abdur-Rahmaan Janhangeer wrote: Poor me a paper has been published citing numpy in the top 10 imports (the others being from the std lib), it was a great event as it was the conclusion after analysing ALL of pypi. A ping would have sufficed to notify. From the tweet:

Re: [Numpy-discussion] Allowing Dependabot access to the numpy repo

ion seems to be to be able to work with private repos: https://github.com/dependabot/feedback/issues/22 There doesn't seem to be any way around it... :( Ryan On Thu, Aug 29, 2019 at 12:04 AM Matti Picus mailto:matti.pi...@gmail.com>> wrote: In PR 14378 https://g

[Numpy-discussion] Using hypothesis in testing

We have discussed using the hypothesis package to generate test cases at a few meetings informally. At the EuroSciPy sprint, kitchoi took up the challenge and issued a pull request https://github.com/numpy/numpy/pull/14440 that actually goes ahead and does it.

[Numpy-discussion] Reformat the wall-of-text release notes

Our Release Note page https://numpy.org/devdocs/release.html is one long litany of all the releases ever. While this is convenient for searching with CTRL-F, it is not conducive to browsing. I suggested splitting it into pages with a TOC page

[Numpy-discussion] Kriti (our Outreachy intern) has published a blog post about being accepted to the program

https://github.com/kritisingh1/numpy/wiki/Now-You-Know-It! Worth a read, see what applicants go through to get accepted. Feel free to re-publish it. There will be more coming as she progresses through the summer. ___ NumPy-Discussion mailing list

Re: [Numpy-discussion] DType Roadmap/NEP Discussion

On 19/9/19 2:34 am, Sebastian Berg wrote: Hi all, to try and make some progress towards a decision since the broad design is pretty much settling from my side. I am thinking about making a meeting, and suggest Monday at 11am Pacific Time (I am open to other times though). My hope is to get

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

On 20/9/19 6:25 am, Robert Kern wrote: Well, we must because one's used by the legacy RandomState and one's used by Generator. :-) I would prefer not to create a legacy C-API at all. Are we required to from the NEP? Matti ___

[Numpy-discussion] Numpy community meeting TODAY !!!

Hi all, Sorry for the late notice There will be a NumPy Community meeting Wednesday Nov 13 (today) at 11 am Pacific Time. Everyone is invited to join in and edit the work-in- progress meeting topics and notes:

[Numpy-discussion] "Proposal to accept NEP 34: Disallow inferring dtype=object from sequence

I propose to move the NEP https://numpy.org/neps/nep-0034.html from "draft" to "accepted" status. There were no objections (actually there were no responses at all) to the mail proposing the NEP https://mail.python.org/pipermail/numpy-discussion/2019-October/080200.html. PR 14794

Re: [Numpy-discussion] Disallow Accelerate as a LAPACK backend for NumPy

On Tue, Nov 12, 2019 at 12:41 AM Matti Picus wrote: Apple has dropped support for Accelerate. It has bugs that have not been fixed, and is closed source so we cannot fix them ourselves. We have been getting a handful of reports from users who end up building NumPy on macOS

  1   2   3   >