On Sat, Oct 7, 2017 at 11:29 AM, Charles R Harris wrote:
> Hi All,
>
> The current NumPy implementation of the truncated zipf distribution has
> several drawbacks.
>
>
>- Extremely poor performance when the parameter `a` is near 1. For
>instance, when `a = 1.01` a simple change in the
On Wed, Mar 14, 2018 at 4:05 AM, Kulick, Johannes
wrote:
> Hi,
>
>
>
> I regularly need the softmax function (https://en.wikipedia.org/
> wiki/Softmax_function) for my code. I have a quite efficient pure python
> implementation (credits to Nolan Conaway). I think it would be a valuable
> enhancem
On Thu, May 10, 2018 at 10:53 PM, Hameer Abbasi
wrote:
> Yes, that I know. I meant given a dtype string such as 'uint8' or a
> dtype object. I know I can possibly do np.array(scalar,
> dtype=dtype)[()] but I was looking for a less hacky method.
Apparently the `dtype` object has the attribute `
On Sat, Jun 2, 2018 at 3:04 PM, Robert Kern wrote:
> As promised distressingly many months ago, I have written up a NEP about
> relaxing the stream-compatibility policy that we currently have.
>
> https://github.com/numpy/numpy/pull/11229
> https://github.com/rkern/numpy/blob/nep/rng/doc/neps/
>
On Sun, Jun 3, 2018 at 11:20 PM, Ralf Gommers
wrote:
>
>
> On Sun, Jun 3, 2018 at 6:54 PM, wrote:
>
>>
>>
>> On Sun, Jun 3, 2018 at 9:08 PM, Robert Kern
>> wrote:
>>
>>> On Sun, Jun 3, 2018 at 5:46 PM wrote:
>>>
On Sun, Jun 3, 2018 at 8:21 PM, Robert Kern
wrote:
>
On Mon, Sep 17, 2018 at 7:38 AM Matthew Brett
wrote:
> Hi,
>
> Is there any reason that np.count_nonzero should not take an axis
> argument? As in:
>
> >>> np.better_count_nonzero([[10, 11], [0, 3]], axis=1)
> array([2, 1])
>
>
It already does (since version 1.12.0):
https://docs.scipy.org/doc/
On 12/10/18, Ralf Gommers wrote:
> On Sun, Dec 9, 2018 at 2:00 PM Alan Isaac wrote:
>
>> I believe this was proposed in the past to little enthusiasm,
>> with the response, "you're using a library; learn its functions".
>>
>
> Not only that, NumPy and the core libraries around it are the standard
On Tue, Dec 11, 2018 at 10:32 AM Ralf Gommers
wrote:
>
>
> On Mon, Dec 10, 2018 at 10:27 AM Warren Weckesser <
> warren.weckes...@gmail.com> wrote:
>
>>
>>
>> On 12/10/18, Ralf Gommers wrote:
>> > On Sun, Dec 9, 2018 at 2:00 PM Alan Isaac wrot
On Tue, Dec 11, 2018 at 1:37 PM Warren Weckesser
wrote:
>
>
> On Tue, Dec 11, 2018 at 10:32 AM Ralf Gommers
> wrote:
>
>>
>>
>> On Mon, Dec 10, 2018 at 10:27 AM Warren Weckesser <
>> warren.weckes...@gmail.com> wrote:
>>
>>>
>>&g
On Tue, Dec 11, 2018 at 2:27 PM Stephan Hoyer wrote:
> On Tue, Dec 11, 2018 at 10:39 AM Warren Weckesser <
> warren.weckes...@gmail.com> wrote:
>
>> There is no bug, just a limitation in the API.
>>
>> When I draw without replacement, say, three values from a
On 3/13/19, Stefan van der Walt wrote:
> In PR 4808, I propose changing the default padding mode (for `np.pad`)
> to constant (0).
+1
Warren
>
> 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/pu
* Conner DiPaolo +
> * Dowon
> * Michael Dunphy +
> * Peter Andreas Entschev +
> * Gökçen Eraslan +
> * Johann Faouzi +
> * Yu Feng
> * Piotr Figiel +
> * Matthew H Flamm
> * Franz Forstmayr +
> * Christoph Gohlke
> * Richard Janis Goldschmidt +
> * Ralf Gommers
>
On 6/24/19, Marten van Kerkwijk wrote:
> Hi Eric,
>
> The easiest definitely is for the mask to just propagate, which that even
> if just one point is masked, all points in the fft will be masked.
>
> On the direct point I made, I think it is correct that since one can think
> of the Fourier trans
en
the functions were added to NumPy in 2008. I recommend reviewing those
threads before commenting here.
Warren
-
==
NEP 32 — Remove the financial functions from NumPy
==========
:Author: Warren W
ebastian Berg
>> wrote:
>>>
>>> On Tue, 2019-09-03 at 08:56 -0400, Warren Weckesser wrote:
>>> > Github issue 2880 ("Get financial functions out of main namespace",
>>>
>>> Very briefly, I am absolutely in favor of this.
>>>
On 9/9/19, D.S. McNeil wrote:
> [coming over from the pydata post]
>
> I just checked about ~150KLOC of our Python code in a financial context,
> written by about twenty developers over about four years. Almost every
> function uses numpy, sometimes directly and sometimes via pandas.
>
> It seems
On 9/3/19, Warren Weckesser wrote:
> Github issue 2880 ("Get financial functions out of main namespace",
> https://github.com/numpy/numpy/issues/2880) has been open since 2013. In a
> recent community meeting, it was suggested that we create a NEP to propose
> the re
On 7/4/19, Kexuan Sun wrote:
> Hi,
>
> I would like to request a code review. The random.permutation and
> random.shuffle functions now can only shuffle along the first axis of a
> multi-dimensional array. I propose to add an axis argument for the
> functions and allow them to shuffle along a give
NEP 32 is available at
https://numpy.org/neps/nep-0032-remove-financial-functions.html
Recent timeline:
- 30-Aug-2019 - A pull request with NEP 32 submitted.
- 03-Sep-2019 - Announcement of the NEP 32 pull request on the
NumPy-Discussion mailing list, with the text of the NEP included in
On 9/18/19, 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).
That works for me.
among the NumPy developers, it would be best
to continue the conversation in a NumPy venue, either the github issue
or the NumPy mailing list. I've cc'ed this email to the NumPy mailing
list.
Warren
>
> On Thursday, September 19, 2019 at 8:25:52 AM UTC-7, Warren Weckesser
> wrote:
&g
NumPy devs,
NEP 32 to remove the financial functions
(https://numpy.org/neps/nep-0032-remove-financial-functions.html) has
been accepted. The next step is to create the numpy-financial package
that will replace them. The repository for the new package is
https://github.com/numpy/numpy-financial.
On 9/27/19, Warren Weckesser wrote:
> NumPy devs,
>
> NEP 32 to remove the financial functions
> (https://numpy.org/neps/nep-0032-remove-financial-functions.html) has
> been accepted.
CI gurus: the web page containing the rendered NEPs,
https://numpy.org/neps/, has not updated
I'm experimenting with gufuncs, and I just created a simple one with
signature '(i)->()'. Is there a way to configure the gufunc itself so
that an empty array results in an error? Or would I have to create a
Python wrapper around the gufunc that does the error checking?
Currently, when passed an
On 9/28/19, Sebastian Berg wrote:
> On Sat, 2019-09-28 at 13:15 -0400, Warren Weckesser wrote:
>> On 9/27/19, Warren Weckesser wrote:
>> > NumPy devs,
>> >
>> > NEP 32 to remove the financial functions
>> > (https://numpy.org/neps/nep-0032-remove
ence function just for the case '(i)->()', maybe
something like PyUFunc_OneDReduction_FromFuncAndData (ugh, that's
ugly, but I think you get the idea), and that function can have an
argument to specify that the length must be at least 1.
I'll see if that is feasible, but I w
On 9/29/19, Warren Weckesser wrote:
> On 9/28/19, Eric Wieser wrote:
>> Can you just raise an exception in the gufuncs inner loop? Or is there no
>> mechanism to do that today?
>
> Maybe? I don't know what is the idiomatic way to handle errors
> detected in an
This is a new thread to address the question of error handling in a ufunc
loop that was brought up in the thread on handling core dimensions of
length zero. I'm attempting to answer my own question about the idiomatic
way to handle an error in an inner loop.
The use of the GIL with a ufunc loop i
On 9/29/19, Warren Weckesser wrote:
> On 9/28/19, Eric Wieser wrote:
>> Can you just raise an exception in the gufuncs inner loop? Or is there no
>> mechanism to do that today?
>
> Maybe? I don't know what is the idiomatic way to handle errors
> detected in an
On 9/29/19, Warren Weckesser wrote:
> This is a new thread to address the question of error handling in a ufunc
> loop that was brought up in the thread on handling core dimensions of
> length zero. I'm attempting to answer my own question about the idiomatic
> way to handle an
On 11/15/19, Marcelo Gasparian Gosling wrote:
> Hi everyone!
>
> So, np-financial is being phased out of mainline Numpy, right? I have a
> patch for the IRR function that I'd like to submit, is it just as easy as
> making a PR on Github?
Hi Marcelo,
The new home for the NumPy financial function
It looks like the repo https://github.com/numpy/windows-wheel-builder
is defunct. Could someone with the appropriate access privileges
merge Matti's pull request to update README.rst
(https://github.com/numpy/windows-wheel-builder/pull/7), and add a
one-line description to the main repo page that
Gina Helfrich +
> * Alex Henrie +
> * Francisco J. Hernandez Heras +
> * Andreas Hilboll
> * Lindsey Hiltner
> * Thomas Hisch
> * Min ho Kim +
> * Gert-Ludwig Ingold
> * jakobjakobson13 +
> * Todd Jennings
> * He Jia
> * Muhammad Firmansyah Kasim +
> * Andrew Knyazev +
Hi all,
Our bi-weekly triage-focused NumPy development meeting is tomorrow
(Wednesday, December 18) at 11 am Pacific Time. Everyone is invited
to join in and edit the work-in-progress meeting topics and notes:
https://hackmd.io/68i_JvOYQfy9ERiHgXMPvg
Best regards,
Warren
On 12/19/19, Tyler Reddy wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hi all,
>
> On behalf of the SciPy development team I'm pleased to announce
> the release of SciPy 1.4.1, which is a bug fix release.
Thanks for the quick fix, Tyler!
Warren
>
> Sources and binary wheels c
eWithSteak
>- Charles Harris
>- Chris Burr
>- Eric Wieser
>- Fernando Saravia
>- Lars Grueter
>- Matti Picus
>- Maxwell Aladago
>- Qiming Sun
>- Warren Weckesser
>
>
> *Pull requests merged*
>
> A total of 14 pull requests were
In response to some work on improving the documentation of `numpy.linalg`
and how it compares to `scipy.linalg`, Kevin Sheppard suggested that the
documentation of the module `numpy.dual` should also be improved. When I
mentioned this suggestion in the community meeting on December 11, it was
sugg
On 1/3/20, Sebastian Berg wrote:
> On Fri, 2020-01-03 at 07:11 -0500, Warren Weckesser wrote:
>> In response to some work on improving the documentation of
>> `numpy.linalg` and how it compares to `scipy.linalg`, Kevin Sheppard
>> suggested that the documentation of the modul
I'm doing some work on the travis-ci scripts, and I'd like to remove
some redundant calls of 'pip install'. The scripts should get the
build dependencies from a configuration file instead of having
hard-coded pip commands. Is pyproject.toml the appropriate file to
use for this? (Note: we also ha
On 1/8/20, Warren Weckesser wrote:
> I'm doing some work on the travis-ci scripts, and I'd like to remove
> some redundant calls of 'pip install'. The scripts should get the
> build dependencies from a configuration file instead of having
> hard-coded pip
se pyproject.toml?
Warren
>
> On Wed, Jan 8, 2020 at 4:38 PM Warren Weckesser
>
> wrote:
>
>> On 1/8/20, Warren Weckesser wrote:
>> > I'm doing some work on the travis-ci scripts, and I'd like to remove
>> > some redundant calls of 'pip in
On 3/20/20, Gunter Meissner wrote:
> Dear Programmers,
>
>
>
> This is Gunter Meissner. I am currently writing a book on Forecasting and
> derived the regression coefficient with Numpy:
>
>
>
> import numpy as np
> X=[1,2,3,4]
> Y=[1,8000,5000,1000]
> print(np.cov(X,Y))
> print(np.var(X))
> Be
It would be handy if in scipy we can use the function
`numpy.lib.shape_base.normalize_axis_index` as a consistent method for
validating an `axis` argument. Is this function considered part of
the public API?
There are modules in numpy that do not have leading underscores but
are still usually con
On 4/4/20, Warren Weckesser wrote:
> It would be handy if in scipy we can use the function
> `numpy.lib.shape_base.normalize_axis_index` as a consistent method for
> validating an `axis` argument. Is this function considered part of
> the public API?
>
> There are modules in
On 4/5/20, Sebastian Berg wrote:
> On Sun, 2020-04-05 at 00:43 -0400, Warren Weckesser wrote:
>> On 4/4/20, Warren Weckesser wrote:
>> > It would be handy if in scipy we can use the function
>> > `numpy.lib.shape_base.normalize_axis_index` as a consistent method
>&g
of how many
>> downstream projects are already using it.
>>
>> Eric
>>
>> On Sun, 5 Apr 2020 at 15:06, Sebastian Berg
>> wrote:
>>
>>> On Sun, 2020-04-05 at 00:43 -0400, Warren Weckesser wrote:
>>> > On 4/4/20, Warren Weckesser wrote:
On 4/19/20, Charles R Harris wrote:
> Hi All,
>
> On behalf of the NumPy team I am pleased to announce that NumPy 1.18.3 has
> been released. This release contains various bug/regression fixes for the
> 1.18 series
Thanks Chuck!
Warren
>
> The Python versions supported in this release are 3.5-
On 5/2/20, Ralf Gommers wrote:
> On Thu, Apr 23, 2020 at 11:38 PM Sebastian Berg
>
> wrote:
>
>> Hi all,
>>
>> it has come up in the last community call that many of our committee
>> membership lists have not been updated in a while.
>> This is not a big issue as such. But, while these committee
On 5/24/20, Inessa Pawson wrote:
> The NumPy web team is excited to announce the launch of the newly
> redesigned numpy.org. To transform the website into a comprehensive, yet
> user-centric, resource of all things NumPy was a primary focus of this
> months-long effort. We thank Joe LaChance, Ralf
son
> * Charles Jekel +
> * Julien Jerphanion +
> * Jiacheng-Liu +
> * Christoph Kecht +
> * Paul Kienzle +
> * Reidar Kind +
> * Dmitry E. Kislov +
> * Konrad +
> * Konrad0
> * Takuya KOUMURA +
> * Krzysztof Pióro
> * Peter Mahler Larsen
> * Eric Larson
> * Anton
Hi all,
Sorry for the short notice--Sebastian is off this week, and the rest
of us forgot to send the email reminder.
Our bi-weekly triage-focused NumPy development meeting is in 10
minutes (today, Wednesday, July 29th, at 11 am Pacific Time (18:00
UTC)). Everyone is invited to join in and edit
In one of the previous weekly zoom meetings, it was suggested
to ping the mailing list about an updated PR that implements
the `permuted` method for the Generator class in numpy.random.
The relevant issue is
https://github.com/numpy/numpy/issues/5173
and the PR is
https://github.com/nump
On 10/15/20, Madhulika Jain Chambers wrote:
> Hello all,
>
> I opened a PR to add a function which returns the broadcasted shape from a
> given set of shapes:
> https://github.com/numpy/numpy/pull/17535
>
> As this is a proposed change to the API, I wanted to see if there was any
> feedback from t
sue with XCode 12 has
> been fixed.
>
> Authors
> ==
>
> * Peter Bell
> * CJ Carey
> * Thomas Duvernay +
> * Gregory Lee
> * Eric Moore
> * odidev
> * Dima Pasechnik
> * Tyler Reddy
> * Simon Segerblom Rex +
> * Daniel B. Smith
> * Will Tirone +
&g
On 10/28/20, Charles R Harris wrote:
> Hi All,
>
> On behalf of the NumPy team I am pleased to announce that NumPy 1.19.3 has
> been released. NumPy 1.19.3 is a small maintenance release with two major
> improvements:
>
>- Python 3.9 binary wheels on all supported platforms,
>- OpenBLAS fi
On 3/6/21, zoj613 wrote:
> Hi All,
>
> I noticed that the transformed rejection method for generating Poisson
> random variables used in numpy makes use of the `random_loggam` function
> which directly calculates the log-gamma function. It appears that a
> log-factorial lookup table was added a fe
Hey all,
If you've ever tried to inspect a file on github with the `.rst`
extension, there's a good chance that you were frustrated by GitHub
providing a rendered view *only* of the file, with no option to view
the source code like any other text file. It is certainly nice to
have a rendered vie
On 12/28/21, Lev Maximov wrote:
> On Tue, Dec 28, 2021 at 3:43 PM Evgeni Burovski
>
> wrote:
>
>> Very nice overview!
>>
>> One question and one suggestion:
>>
>> 1. Is integer wraparound guaranteed for signed ints, or is it an
>> implementation detail? For unsigned ints, sure, it's straight from
In the script below, the evaluation of the expression `z.real**2 +
z.imag**2` is timed using the `timeit` module. `z` is a 1D array of
random samples with dtype `np.complex128` and with length 25.
The mystery is the change in performance of the calculation from the
first array to which it is a
approach probably uses
> more memory, specially when large arrays need to be handled.
>
> All in all, this is testimonial of how much memory handling can affect
> performance in modern computers. Perhaps it is time for testing different
> memory allocation strategies in N
On 6/30/22, Ewout ter Hoeven wrote:
> A function to get the minimum and maximum values of an array simultaneously
> could be very useful, from both a convenience and performance point of view.
> Especially when arrays get larger the performance benefit could be
> significant, and even more if the
On 9/8/22, Andrew Nelson wrote:
> On Thu, 8 Sept 2022, 19:42 Sebastian Berg,
> wrote:
>
>>
>> TL;DR: NumPy scalars representation is e.g. `34.3` instead of
>> `float32(34.3)`. So the representation is missing the type
>> information. What are your thoughts on changing that?
I like the idea,
On 12/12/22, Aaron Meurer wrote:
> On Mon, Dec 12, 2022 at 8:46 AM Sebastian Berg
> wrote:
>>
>> On Wed, 2022-12-07 at 14:21 -0700, Aaron Meurer wrote:
>> > Hi all.
>> >
>> > As discussed in today's community meeting, I plan to start working on
>> > adding some useful functions to NumPy which are
On 4/20/23, Sebastian Berg wrote:
> Hi all,
>
> Unlike conversions of 0-d arrays via:
>
> float(np.array([1]))
>
> conversions of 1-D or higher dimensional arrays with a single element
> are a bit strange:
>
> float(np.array([1]))
>
> And deprecating it has come up often enough with many i
On 4/21/23, Sebastian Berg wrote:
> On Thu, 2023-04-20 at 20:17 +0200, Sebastian Berg wrote:
>> On Thu, 2023-04-20 at 13:59 -0400, Warren Weckesser wrote:
>> > On 4/20/23, Sebastian Berg wrote:
>> > > Hi all,
>> > >
>> > >
>>
&
On Fri, Aug 18, 2023 at 4:59 AM Ronald van Elburg <
r.a.j.van.elb...@hetnet.nl> wrote:
> I was trying to get a feel for how often the work around occurs. I found
> three clear examples in Scipy and one unclear case. One case in holoviews.
> Two in numpy. One from soundappraisal's code base.
>
See
On Sun, Aug 20, 2023 at 7:33 AM Doug Turnbull
wrote:
> First of all, I really love the docs of the C API :) It's way above what I
> would expect!
>
> I was reviewing the signature possibilities for generalized UFuncs, and
> had a question
>
> https://numpy.org/doc/stable/reference/c-api/generaliz
On Mon, Aug 21, 2023 at 4:37 AM Ralf Gommers wrote:
> Hi all,
>
> On behalf of the steering council, I am very happy to announce that Andrew
> is joining the Maintainers team. Andrew has been contributing to our CI
> setup in particular for the past year, and has contributed for example the
> Cir
On Tue, Aug 29, 2023 at 10:09 AM Nathan wrote:
>
> The NEP was merged in draft form, see below.
>
> https://numpy.org/neps/nep-0055-string_dtype.html
>
> On Mon, Aug 21, 2023 at 2:36 PM Nathan wrote:
>>
>> Hello all,
>>
>> I just opened a pull request to add NEP 55, see
https://github.com/numpy/n
On Mon, Sep 11, 2023 at 12:25 PM Nathan wrote:
>
>
> On Sun, Sep 3, 2023 at 10:54 AM Warren Weckesser <
> warren.weckes...@gmail.com> wrote:
>
>>
>>
>> On Tue, Aug 29, 2023 at 10:09 AM Nathan
>> wrote:
>> >
>> > The NEP was merged
On Fri, Sep 15, 2023 at 3:18 PM Warren Weckesser
wrote:
>
>
>
> On Mon, Sep 11, 2023 at 12:25 PM Nathan wrote:
>>
>>
>>
>> On Sun, Sep 3, 2023 at 10:54 AM Warren Weckesser <
warren.weckes...@gmail.com> wrote:
>>>
>>>
>>>
>&g
On Mon, May 20, 2024 at 9:06 AM Raquel Braunschweig via
NumPy-Discussion wrote:
>
> Hello everyone,
>
> My colleague and I will be opening a Pull Request (PR) about adding bfill()
> (backward fill) function to NumPy. This function is designed to fill NaN
> values in an array by propagating the n
I have implemented quite a few generalized ufuncs over in ufunclab
(https://github.com/WarrenWeckesser/ufunclab), and in the process I
have accumulated a gufunc "wish list". Two items on that list are:
(1) the ability to impose constraints on the core dimensions that are
checked when the gufunc is
On Fri, Jul 12, 2024 at 7:47 AM Sebastian Berg
wrote:
>
> (You won't be able to know these relations from reading the signature,
> but I doubt it's worth worrying about that.)
After creating the gufunc with `PyUFunc_FromFuncAndDataAndSignature`,
the gufunc author could set the `core_signature` f
On Fri, Jul 12, 2024 at 2:35 PM Sebastian Berg
wrote:
>
> On Fri, 2024-07-12 at 09:56 -0400, Warren Weckesser wrote:
> > On Fri, Jul 12, 2024 at 7:47 AM Sebastian Berg
> > wrote:
> > >
> >
> > > (You won't be able to know these relations from read
On Mon, Aug 19, 2024 at 6:45 AM Sebastian Berg
wrote:
>
> Hi all,
>
> please join me in welcoming Joren (https://github.com/jorenham) to the
> NumPy maintainers team.
>
Welcome Joren!
Warren
> Joren has done a lot of work recently contributing, reviewing, and
> maintaining typing related improv
On Mon, Aug 26, 2024 at 5:42 PM Sebastian Berg
wrote:
>
> On Mon, 2024-08-26 at 11:26 -0400, Marten van Kerkwijk wrote:
> > I think a NEP is a good idea. It would also seem to make sense to
> > consider how the dtype itself can hold/calculate this type of
> > information, since that will be the o
77 matches
Mail list logo
