[Numpy-discussion] Re: How does Numpy model non-float arrays?

On 22/8/23 02:25, Dylon Edwards wrote: It is my understanding that Numpy accelerates array operations with BLAS where possible, but BLAS does not support all the dtypes that Numpy does. How does Numpy model non-float arrays like arrays of dtype=bool or dtype=object? Numpy only uses BLAS wher

[Numpy-discussion] Re: JSON format for multi-dimensional data

On 20/2/24 01:24, phili...@loco-labs.io wrote: Hi community, This memo is a proposal to implement a compact and reversible (lossless round-trip) JSON interface for multi-dimensional data and in particular for Numpy (see issue #12481). The links to the documents are at the end of the memo. Th

[Numpy-discussion] Re: builing numpy on windows

On 27/2/24 06:09, Ganesh Rajora via NumPy-Discussion wrote: Hi Team, I am Ganesh working for an MNC here in India and I am working on customised Python where I build set of python modules with python. I do not install them directly from web but I build each and everything from source code. 

[Numpy-discussion] Change in behaviour: broadcasting rules for np.solve

API changes should hit the mailing list, so I am copying from PR https://github.com/numpy/numpy/pull/25914 by Aaron Meurer: Previously the np.linalg.solve documentation stated: |a : (..., M, M) array_like Coefficient matrix. b : {(..., M,), (..., M, K)}, array_like | however, this is inhe

[Numpy-discussion] Re: Arrays of variable itemsize

I am not sure what kind of a scheme would support various-sized native ints. Any scheme that puts pointers in the array is going to be worse: the pointers will be 64-bit. You could store offsets to data, but then you would need to store both the offsets and the contiguous data, nearly doubling

[Numpy-discussion] Re: Accelerated NumPy with Weld compiler

On 20/3/24 15:13, Hemant Singh via NumPy-Discussion wrote: Stanford and MIT jointly developed the Weld language and compiler to run NumPy and Pandas significantly faster, 10x-250x. My company has changed the compiler to be production ready. Anyone interested in trialing this compiler, please

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

Could we move the weekly community/triage meetings one hour later? Some participants have a permanent conflict, and the current time is inconvenient for my current time zone. Matti ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To u

[Numpy-discussion] Re: Making show_runtime and show_config enable file output

On 09/04/2024 2:42, Matan Addam wrote: Hello, I find the information printed by the above mentioned functions to be useful for understanding performance context on installed machines, as well as variability across machines when troubleshooting. How would the maintainers view a pull request a

[Numpy-discussion] Re: New feature

On 25/04/2024 23:16, Alexei Lisitsa wrote: Waiting for answer What kind of answer would you like? I took a look at numpy_list[0] and if it serves your needs, that is great, but I don't think such ndarray generation routines should be added to NumPy until they become more commonly known, us

[Numpy-discussion] Re: Please consider dropping Python 3.9 support for Numpy 2.0

On 05/05/2024 11:32, Mark Harfouche wrote: I know this is somewhat the 11th hour for the numpy 2.0 release but as downstream packager and user of numpy, I would really like to ask that Numpy strives to adhere to NEP29, and SPEC0 SEPC0 makes it pretty clear that Python 3.9 should not be includ

[Numpy-discussion] Re: New feature

For a start you could share the link for the stand-alone package here, with a short description of what it does. Additional steps would be to write a blog post about it, write it up on reddit's python subreddit, give a talk about it at a conference. Matti On 25/04/2024 23:36, Alexei Lisitsa

[Numpy-discussion] Re: Build NumPy with Debugging Symbols with Meson

On 15/05/2024 23:55, Robert McLeod wrote: | | Hi everyone, | | Is there a gist or similar guide anywhere on the steps required to build NumPy with debugging symbols on the Windows platform using the new Meson build system? In general, I would try to avoid using python_d.exe. It requires the entir

[Numpy-discussion] Re: Unexpected return values for np.mod with x2=np.inf and similar

What operating system? If I recall correctly, NumPy tries to be compatible with CPython for these edge cases. The actual implementation is a bit scattered. I think it would be nice if we could have an "explain" decorator to ufuncs that would return the name of the inner loop used in practi

[Numpy-discussion] Re: Generate documentation for the 2.0.0 release

I will make a PR to https://github.com/numpy/doc Matti On 16/06/2024 19:04, Charles R Harris wrote: PS, you will need to check out `.spin/cmds.py` from the main branch in order to build the documentation. Chuck On Sun, Jun 16, 2024 at 9:59 AM Charles R Harris wrote: Hi All, Cou

[Numpy-discussion] Re: Windows 11 arm64 wheel

On 12/08/2024 11:55, slobodan.miletic--- via NumPy-Discussion wrote: As the bug fix is merged we are starting the investigation on the CI job. I have a few questions about this: 1) Are there some additional instructions for making and running the numpy CI jobs and cross compilation available in

[Numpy-discussion] Re: Welcome Joren Hammudoglu to the NumPy Maintainers Team

Welcome Joren, thanks for all the work Matti On Mon, Aug 19, 2024 at 1:41 PM Sebastian Berg wrote: > > Hi all, > > please join me in welcoming Joren (https://github.com/jorenham) to the > NumPy maintainers team. > > Joren has done a lot of work recently contributing, reviewing, and > maintaining

[Numpy-discussion] Re: Documentation for the 2.0.0 release.

Done. Thanks for the release. Matti On Mon, 19 Aug 2024 at 02:59, Charles R Harris wrote: ___ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-le...@python.org https://mail.python.org/mailman3

[Numpy-discussion] Re: What should remain on PyPi

I would prefer we never delete packages once we upload them to PyPI, unless there are security issues with them. As Sean demonstrated, someone somewhere is going to be using them, and deleting packages will inevitably break something. Matti On Tue, Sep 3, 2024 at 7:44 PM Sean Gillies wrote: > >

[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 th

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. Message-ID: Content-Type: text/plain; charset="utf-8" Hi All,

[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 sh

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

Date: Wed, 8 Nov 2017 18:41:03 +0200 From: Matti Picus To: numpy-discussion@python.org Subject: [Numpy-discussion] deprecate updateifcopy in nditer operand flags? Message-ID: Content-Type: text/plain; charset=utf-8; format=flowed I filed issue 9714 https://github.com

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? Message-ID: Content-Type: text/plain; ch

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), rejec

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 offl

[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 fin

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 arrays

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 ___

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 meetin

[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

[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) (k),(k,m)->

[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

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 diffe

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 <mailto:sho...@gmail.com>> wrote: On Sun, Apr 29, 2018 at 2:48 AM Matti Picus mailto:matti.pi...@gmail.com>> wrote: The proposed solution

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 have

[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 can

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 <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-25 https://scisprints.github.io/#

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] 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 convi

[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 requ

Re: [Numpy-discussion] Allowing broadcasting of code dimensions in generalized ufuncs

On 31/05/18 08:23, Allan Haldane wrote: Re: implenetation complexity, I just want to bring up multiple-dispatch signatures again, where the new signature syntax would just be to join some signatures together with "|", and try them in order until one works. I'm not convinced it's better myself, I

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

At the recent NumPy sprint at BIDS (thanks to those who made the trip) we spent some time brainstorming about a roadmap for NumPy, in the spirit of similar work that was done for Jupyter. The idea is that a document with wide community acceptance can guide the work of the full-time developer(s)

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. But

[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] 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 conference

[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 https://mail.python.org/

[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 P

[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 origi

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.

[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 it

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

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] 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 `

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 broa

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 doe

[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 t

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 the

[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 i

[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 r

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 http://www.numpy.org/devdocs/reference/testing.ht

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 requ

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 t

[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 i

[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 @http://www.numpy.org/devdocs/search.html?q=ndarray:34:

[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 '0x10f00

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

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

[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 both

[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 "normal"

[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 looking

[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 therefore

[Numpy-discussion] Attribute hiding APIs for PyArrayObject

TL;DR - should we revert the attribute-hiding constructs in ndarraytypes.h and unify PyArrayObject_fields with PyArrayObject? Background NumPy 1.8 deprecated direct access to PyArrayObject fields. It made PyArrayObject "opaque", and hid the fields behind a PyArrayObject_fields structure ht

[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 https://mail.python.org/ma

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] 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 Previous

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 ther

[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 https://github.com/BIDS-numpy/docs/tre

[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 https://github.com/BIDS-numpy/docs/tre

[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 ta

[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] 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] 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

[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 depre

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 e

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 got

[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 NumPy

[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-

[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] 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 these

[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-

[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 NumP

[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

[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, ...). Thi

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 https://www.outreachy.org/may-

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 runt

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 Program Aspirant

On 20/3/19 12:20 pm, rishab lamba wrote: Hi, I am Rishab Lamba undergoing my B.Tech from BVCOE, India. As an applicant from Outreachy, I was going through this project https://www.outreachy.org/may-2019-august-2019-outreachy-internships/communities/numpy/#improve-c-api-documentation-for-numpy

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

On 20/3/19 10:09 pm, Stefan van der Walt wrote: 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.

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

  1   2   3   >