On Sun, Nov 14, 2021 at 9:05 PM Charles R Harris
wrote:
>
>
> On Sun, Nov 14, 2021 at 11:49 AM Ralf Gommers
> wrote:
>
>>
>>
>> On Wed, Nov 10, 2021 at 2:36 PM Aivar Annamaa
>> wrote:
>>
>>> Has it been decided to stop publishing win32 whe
ot surprisingly, MSVC is arguably buggy and does to not compile the
> C99 `islessgreate` to fast byte-code – although plausibly link-time
> optimizer may safe that. But since we have hand coded SSE2/AVX
> versions of comparisons, even that would probably not matter)
>
>
>
> > On
(Apologies for the cross-posting, if you follow more than one of these
lists, you may see this multiple times.)
Hi all,
I'd like to solicit the feedback of maintainers of NumPy, SciPy,
scikit-learn, and scikit-image, and other interested community members on
this blog post and proposed design to
On Tue, Nov 30, 2021 at 3:18 PM Melissa Mendonça
wrote:
> Hello, folks!
>
> As of today, our participation in the Google Season of Docs program for
> 2021 has ended. You can see the case study detailing the work done and some
> key results in the following link:
>
>
> https://github.com/numpy/num
Hi all,
Setuptools is going to re-enable a setting which makes it prefer its
vendored copy of distutils over the distutils code in the stdlib in two
weeks. If you only use setuptools and not numpy.distutils directly, then
you're probably fine. If you do use numpy.distutils, then your build may
bre
Hi Inessa,
Happy holidays to you and everyone on this list!
Also, I'm excited to see what you can do in this new role! It's great that
we have dedicated funded time for improving the contributor experience.
It's been a few months since Melissa announced that we got a new grant
(jointly with SciP
On Sun, Dec 26, 2021 at 2:13 PM Isha Verma wrote:
> Hello I am new to NumPy and I would like to contribute. Can someone please
> help me with the ways I can contribute !
>
Hi Isha, welcome! We have extensive contributor documentation, and guidance
on what types of contributions you can make at h
Hi all,
Anirudh Subramanian has indicated that he is happy to be replaced on the
Code of Conduct committee. Right now the committee is Stefan van der Walt,
Melissa Mendonca, and Anirudh (stepping down). We'd like to add a new third
person. If anyone is interested, could you please reply or reach o
On Sun, Jan 16, 2022 at 9:16 AM Sandro Tosi wrote:
> Hello,
> i'm preparing 1.22.1 for inclusion in Debian, and noticed how the new
> numpy has a git submodule to include numpy/SVML in its source tree.
>
> We are basing the debian package on the github tarball, and that does
> not include any sub
Hi all,
Now that 1.22.0 is out the door, I think it's time to deprecate
`numpy.distutils` completely.
A brief summary for context:
- `distutils` was deprecated in Python 3.10, and will be removed in Python
3.12 (Oct 2023 release date)
- `setuptools` has re-enabled its vendored copy of `distutils`
On Sun, Jan 16, 2022 at 10:40 PM Sandro Tosi wrote:
> > 4. Write a docs page with migration info on how to deal with the
> deprecation, and update it before the 1.23.0 release.
>
> i think this will be extremely important. Just to give you the current
> POV of debian projects using numpy.distutil
On Mon, Jan 17, 2022 at 11:27 AM Oscar Benjamin
wrote:
> On Mon, 17 Jan 2022 at 10:01, Ralf Gommers wrote:
>
>>
>>
>> On Sun, Jan 16, 2022 at 10:40 PM Sandro Tosi
>> wrote:
>>
>>> > 4. Write a docs page with migration info on how to deal wi
tutils to setuptools ? Are people of setuptools already in
> the loop ?
>
Yes, the lead setuptools maintainer has stated that they're happy to accept
any new features that make sense.
Cheers,
Ralf
> Cheers,
>
> Jerome
>
> On Mon, 17 Jan 2022 10:57:40 +0100
> Ralf Gommer
On Tue, Jan 18, 2022 at 3:33 PM wrote:
> Hi,
>
> We are using Openstack zuul ( Openstack CI ) to deploy devstack on IBM
> PPC64el hardware
>
> In
> https://review.opendev.org/c/openstack/requirements/+/824810/2/upper-constraints.txt#124
> commit
> the numpy package version is updated from 1.22.0
On Sun, Jan 16, 2022 at 7:41 PM Ralf Gommers wrote:
> Hi all,
>
> Now that 1.22.0 is out the door, I think it's time to deprecate
> `numpy.distutils` completely.
>
> A brief summary for context:
> - `distutils` was deprecated in Python 3.10, and will be removed in Pytho
On Sat, Jan 29, 2022 at 4:12 PM Melissa Mendonça
wrote:
> Hello, all!
>
> Some of you might be interested to know that we are organizing SciPy
> Community Meetings again. The idea is to have those every two weeks on
> Wednesdays, alternating between times to try and get as many timezones as
> pos
On Sat, Jan 29, 2022 at 6:37 PM Stefan van der Walt
wrote:
> On Sat, Jan 29, 2022, at 07:11, Melissa Mendonça wrote:
>
> The next one will happen this week, on* February 2, at 12 pm UTC*.
>
>
> I just want to confirm that this means "mid-day UTC" or "4am Pacific"?
>
Yes, that is what it should m
On Mon, Jun 14, 2021 at 3:22 AM Charles R Harris
wrote:
>
>
> On Sun, Jun 13, 2021 at 10:47 AM Ralf Gommers
> wrote:
>
>> Hi all,
>>
>> FYI, I noticed this package that claimed to be maintained by us:
>> https://pypi.org/project/numpy-aarch64/. That&#
21 at 5:28 PM Ralf Gommers wrote:
> Hi all,
>
> Anirudh Subramanian has indicated that he is happy to be replaced on the
> Code of Conduct committee. Right now the committee is Stefan van der Walt,
> Melissa Mendonca, and Anirudh (stepping down). We'd like to add a new thi
On Sun, Jan 30, 2022 at 12:44 PM Ralf Gommers
wrote:
>
>
> On Mon, Jun 14, 2021 at 3:22 AM Charles R Harris <
> charlesr.har...@gmail.com> wrote:
>
>>
>>
>> On Sun, Jun 13, 2021 at 10:47 AM Ralf Gommers
>> wrote:
>>
>>> Hi all,
>&
On Thu, Apr 7, 2022 at 5:42 PM Charles R Harris
wrote:
>
>
> On Wed, Apr 6, 2022 at 3:06 PM Aaron Meurer wrote:
>
>> Was the faster CPython release cadence (PEP 602
>> https://peps.python.org/pep-0602/) ever discussed in relation to NEP
>> 29 (https://numpy.org/neps/nep-0029-deprecation_policy.h
On Sat, Apr 30, 2022 at 4:51 PM Sergei Lebedev
wrote:
> Hi everyone,
>
> I've noticed that NumPy currently users separate type stub files for
> specifying types for both pure Python and native modules. For example the
> (untyped) implementation of np.core._asarray is in [1], but the types are
> i
On Sun, May 1, 2022 at 9:08 PM Sergei Lebedev
wrote:
> > I think that's on purpose, because the type annotations are quite
> complex.
> > For reasons of correctness/completeleness, they use protocols, mixins,
> and
> > overloads. Inside pure Python code, that would be harder to read and
> > maint
On Tue, May 3, 2022 at 5:05 PM Renato Fabbri
wrote:
> This is not only for me, but a question for the community in general.
> Do we have an open knowledge base of budget (interested companies or
> individuals, public funding)
> for developing numpy-related packages?
>
Hi Renato, no we don't have
On Sat, May 21, 2022 at 3:40 AM Charles R Harris
wrote:
> Hi All,
>
> I've put up new stable documentation for NumPy 1.22.4. I'd appreciate it
> if those familiar with how they want the documentation to look could take a
> look at it so that fixes can be made while I'm still in the documentation
On Fri, May 20, 2022 at 10:05 AM wrote:
> Thanks for the reply.
>
> To tell the truth, I am working on a trial implementation for SVE.
> https://github.com/kawakami-k/numpy/commits/sve
> At this time, some test patterns still fail, so I'm fixing them. When I
> finish this work, I would like to co
On Mon, May 23, 2022 at 1:31 AM Stephan Hoyer wrote:
> On Sun, May 22, 2022 at 3:52 PM Rohit Goswami
> wrote:
>
>> Being very hard to read should not be reason enough to stop generating
>> them. In places with little to no internet connectivity often the PDF
>> documentation is invaluable.
>>
>
On Mon, May 23, 2022 at 6:51 AM Matti Picus wrote:
>
> On 23/5/22 01:51, Rohit Goswami wrote:
> >
> > Being very hard to read should not be reason enough to stop generating
> > them. In places with little to no internet connectivity often the PDF
> > documentation is invaluable.
> >
> > I persona
;d prefer to not consider it.
You can easily build it locally though if you'd use it personally.
>
> Best regards,
> Lev
>
> On Mon, May 23, 2022 at 1:33 PM Ralf Gommers
> wrote:
>
>>
>>
>> On Mon, May 23, 2022 at 6:51 AM Matti Picus
>> wrote:
&g
On Tue, May 24, 2022 at 3:24 PM Ewout ter Hoeven <
e.m.terhoe...@student.tudelft.nl> wrote:
> Personally I would be in favor of updating NEP 29 to a support timespan in
> which at most 3 (minor) Python versions are supported. The development of
> Python is still at a high pace and NumPy is a high
we will take your patches to un-break
> things as you send them). We would obviously need more thought out
> definitions of the levels as well.
>
Agreed, this would be useful to map out. Starting with what we currently
do, and not mix in any changes in our CI/wheel coverage, in order to
On Thu, May 26, 2022 at 4:41 AM Aaron Meurer wrote:
> > I have seen problems popping up already in a few places with latest
> numpy not supported what is still the most commonly used Python version
> (don't have links, sorry - but they were real packaging-related issues). So
> I don't think it ma
On Thu, May 26, 2022 at 3:19 PM wrote:
> Thank you Gommers
>
> I'd like to discuss this again when I finish SVE implementation. (It may
> be one month later.)
>
Sounds great, thanks Kentaro.
Cheers,
Ralf
> Cheers,
> Kentaro
> ___
> NumPy-Discussion
On Fri, May 27, 2022 at 6:00 AM Aaron Meurer wrote:
>
>
> On Thu, May 26, 2022 at 3:45 AM Matti Picus wrote:
>
>> On 26/5/22 05:40, Aaron Meurer wrote:
>>
>> >> We cannot do that (yet, at least). Failing to publish wheels for a
>> supported Python version on a major OS is far worse than dropping
On Wed, Jun 1, 2022 at 5:51 PM Sebastian Berg
wrote:
>
> An important part of moving forward will be assessing the real world
> impact. To start that process, I have created a branch as a draft PR
> (at this time):
>
> https://github.com/numpy/numpy/pull/21626
>
> It is missing some parts, b
Hi all,
In a few places I noticed recently that it has become harder for Numba to
keep up with NumPy releases. Numba is very popular, so that's not an ideal
situation for end users or for packages which have both NumPy and Numba as
dependencies. If we can do things to make the life of the Numba te
l our build infrastructure is based
> > on `numpy.distutils` which apparently is going to disappear in the
> > coming years. Beside us, the `scipy` project was using it ...
> >
> > Ralf Gommers has ported `scipy` to build with `meson-python` and there
> > are apparently some sh
On Mon, Jun 13, 2022 at 11:52 AM Jerome Kieffer
wrote:
> Hi Evgeni,
>
> Thanks for your input, apparently, you project uses `meson-pep517`
> while scipy uses `meson-python` for interfacing meson with the python
> side of the building.
>
> For now, I am not settled on one version or another but am
On Mon, Jun 6, 2022 at 5:08 PM Niyas Sait wrote:
> > When you say "we could request access to new Volterra machines": how do
> > you see that playing out? Who would provide them, and who would maintain
> > them? Would they be available to the more general scientific python
> > community? Who woul
On Wed, Jun 22, 2022 at 11:35 AM Niyas Sait wrote:
> Hi Niyas, I'd be interested in remote access to a development machine.
>> This will help with NumPy and SciPy; and it would allow testing binaries
>> resulting from a cross-compilation step.
>> I don't have a preference for a Volterra box or an
On Tue, Jun 28, 2022 at 6:33 PM Miles Cranmer
wrote:
> Dear all,
>
> There is a PR that adds a lookup table approach to `unique`, shown below.
> You can get up to ~16x speedup for large integer arrays, at the cost of
> potentially greater memory usage.
>
I've seen multiple requests for not sorti
On Tue, Jun 28, 2022 at 7:21 PM Miles Cranmer
wrote:
> Thanks for the comments Ralf!
>
> > You cannot switch the default behavior, that will break backwards
> compatibility.
>
> The default `kind=None` have no effect on input/output behavior of the
> function. The only changes a user will see are
On Wed, Jun 29, 2022 at 7:10 AM Miles Cranmer
wrote:
> Regarding 2., did you have a particular approach in mind? This new lookup
> table method is already O(n) scaling (similar to a counting sort), so I
> cannot fathom a method that, as you suggest, would get significantly better
> performance fo
On Wed, Jun 29, 2022 at 2:59 PM Miles Cranmer
wrote:
> So, this new method is in fact a hash table as discussed in that blog
> post. However, because it assumes integer arrays, we can go even further
> than that blog, and simply use `np.arange(ar_min, ar_max + 1)` is the "hash
> table". Thus, you
On Thu, Jun 30, 2022 at 10:29 AM Matthew Brett
wrote:
> Hi,
>
> On Thu, Jun 30, 2022 at 12:42 AM Kevin Sheppard
> wrote:
> >>
> >>
> >> Hi,
> >>
> >> I am very sorry - I feel I should know this, or be able to work it
> >> out, but is there a way of setting the flags to the C compiler and the
> >
On Thu, Jun 30, 2022 at 10:47 AM Matthew Brett
wrote:
> Hi,
>
> On Thu, Jun 30, 2022 at 9:40 AM Ralf Gommers
> wrote:
> >
> >
> >
> > On Thu, Jun 30, 2022 at 10:29 AM Matthew Brett
> wrote:
> >>
> >> Hi,
> >>
On Thu, Jun 30, 2022 at 10:57 AM Ralf Gommers
wrote:
>
>
> On Thu, Jun 30, 2022 at 10:47 AM Matthew Brett
> wrote:
>
>> Hi,
>>
>> On Thu, Jun 30, 2022 at 9:40 AM Ralf Gommers
>> wrote:
>> >
>> >
>> >
>> > On Thu, Jun 3
On Thu, Jun 30, 2022 at 11:15 AM Ralf Gommers
wrote:
>
>
> On Thu, Jun 30, 2022 at 10:57 AM Ralf Gommers
> wrote:
>
>>
>>
>> On Thu, Jun 30, 2022 at 10:47 AM Matthew Brett
>> wrote:
>>
>>> Hi,
>>>
>>> On Thu, Jun 30, 2022
On Thu, Jun 30, 2022 at 9:25 PM Matthew Brett
wrote:
> Hi,
>
> On Thu, Jun 30, 2022 at 8:14 PM Matthew Brett
> wrote:
>
> > >> >>
> > >> >> I guess we should change that text to note these do not work on
> Windows.
> > >> >>
> > >> >> I think you can supply extra Fortran flags with the `config_g
On Thu, Jun 30, 2022 at 10:56 PM Warren Weckesser <
warren.weckes...@gmail.com> wrote:
> 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.
> > Esp
On Mon, Jun 27, 2022 at 9:16 PM DavidKorczynski wrote:
> Thanks for the detailed insights Zac!
>
Thanks indeed, this was very helpful.
> Numpy maintainers, are you interested in trying out OSS-Fuzz? The only
> thing needed is some maintainer email for receiving issues and then I
> can get thin
On Mon, Jul 4, 2022 at 4:23 PM Juan Nunez-Iglesias wrote:
> Thanks Matthew!
>
> I will say one thing, I agree that there are major costs, but the longer I
> work in this space the more I appreciate the benefits there might be to
> *not* being on GitHub. I recently (finally) read Nadia Eghbal's Wo
On Mon, Jul 25, 2022 at 7:46 PM Charles R Harris
wrote:
> Hi All,
>
> I propose to remove nose support from numpy/testing/. We moved to pytest
> about five years ago because nose was no longer maintained, but kept the
> outdated nose support for downstream projects who had not yet dropped it.
> N
On Sun, Aug 7, 2022 at 9:59 AM Matti Picus wrote:
> My assumption in advising Ganesh to create a new function was that there
> may be some people who find show_config useful. Personally I do not find
> it useful. If there is agreement that what matters is runtime and not
> build-time then we shou
Hi all,
After setuptools 65.0 was released a few days ago, all users of
numpy.distutils had their builds broken. This is already fixed in
setuptools 65.0.2 because the breakage was particularly bad. However, the
next breakage may not be fixed anymore (and more breakages *are* expected).
So this is
On Fri, Aug 26, 2022 at 5:52 PM Johann Rohwer wrote:
> Hi all,
>
> First of all, I am not sure if this is the correct forum for f2py-related
> questions, but since f2py is part of numpy I thought I'd start here. Please
> point me to the correct place if I am mistaken.
>
This is the right mailing
On Tue, Sep 27, 2022 at 10:58 AM Filippo Tagliacarne <
filippotagliaca...@gmail.com> wrote:
> Hello everyone,
>
> I hope this is the correct place to post this as this is my first
> (potential) contribution to numpy.
>
Hi Filippo, yes this is the correct place. Thanks for your proposal, and
for b
On Thu, Sep 29, 2022 at 10:10 AM Sebastian Berg
wrote:
> On Wed, 2022-09-28 at 16:44 -0700, Stefan van der Walt wrote:
> > Hi Sebastian,
> >
> > On Wed, Sep 28, 2022, at 12:11, Sebastian Berg wrote:
> > > np.array([1, 2], dtype="uint8") + (-1)
> > >
> > > which currently returns an "int16" ar
On Mon, Oct 10, 2022 at 11:02 PM Nick Gerner wrote:
> On Mon, Oct 10, 2022 at 1:35 PM Charles R Harris <
> charlesr.har...@gmail.com> wrote:
>
>>
>>
>> On Mon, Oct 10, 2022 at 12:27 PM Nick Gerner
>> wrote:
>>
>>> I upgraded from 1.21 to 1.23.3 recently and got a variety of mypy
>>> issues. I se
On Fri, Oct 28, 2022 at 10:57 AM Sebastian Berg
wrote:
> Hi all,
>
> As mentioned earlier, I would like to propose changing the
> representation of scalars in NumPy. Discussion and ideas on changes
> are much appreciated!
>
> The main change is to show scalars as:
>
> * `np.float64(3.0)` inste
On Wed, Nov 2, 2022 at 9:30 AM 腾刘 <27rabbi...@gmail.com> wrote:
> Hi everyone! I 'm here again.
>
> Recently I 'm trying to understand the C code with output-debug method,
> inserting many print statements. I was doing well with it until one day: I
> changed a file called loops_utils.h.src located
Hi all,
With distutils now removed from the stdlib in the Python 3.12 release
cycle, the clock is ticking a bit for dealing with our build system
situation. With SciPy's move to Meson now basically complete - there are
always loose ends & improvements, but the 1.9 releases have gone well -
it's ti
On Fri, Nov 11, 2022 at 1:52 PM Sebastian Berg
wrote:
> On Fri, 2022-11-11 at 12:27 +0100, Ralf Gommers wrote:
> > Hi all,
> >
> > With distutils now removed from the stdlib in the Python 3.12 release
> > cycle, the clock is ticking a bit for dealing with our build
On Fri, Nov 11, 2022 at 3:43 PM Sebastian Berg
wrote:
> On Fri, 2022-11-11 at 17:03 +0300, Evgeni Burovski wrote:
> > > (2) a more important one, the `.c.src` format. In SciPy we got rid
> > > of it, and we're not going to make Meson understand an ad-hoc
> > > templating method that only NumPy us
On Fri, Nov 11, 2022 at 10:07 PM Stefan van der Walt
wrote:
> On Fri, Nov 11, 2022, at 06:03, Evgeni Burovski wrote:
> > before: any thoughts to change it to e.g. tempita templating?
>
> With the "e.g." maybe being jinja2. tempita works well, but hasn't been
> worked on since 2013.
>
It actually
On Fri, Nov 11, 2022 at 2:47 PM Sebastian Berg
wrote:
> Hi all,
>
> I want to add a new exception or two. It is a longer story, that you
> can find at the bottom :).
>
> Lets create a namespace for custom errors! I don't want to propose new
> exceptions that just get dumped in to the main names
Hi all,
We have to do something about long double support. This is something I
wanted to propose a long time ago already, and moving build systems has
resurfaced the pain yet again.
This is not a full proposal yet, but the start of a discussion and gradual
plan of attack.
The problem
---
On Wed, Nov 30, 2022 at 10:24 AM Matti Picus wrote:
>
> On 30/11/22 05:47, Stefan van der Walt wrote:
> > On Tue, Nov 29, 2022, at 07:21, i...@markopacak.com wrote:
> >> The debate is whether np.testing.asset_equal should support
> >> collections.Sequence objects.
> > assert list(sequence1) == li
On Wed, Nov 30, 2022 at 7:10 PM Marko Pacak wrote:
> Hi Ralf, thx for replying to this.
>
> > I'd prefer to tell users to use `np.asarray()` on their inputs instead.
>
> How would you do that? Through a warning in the test suite? Or document it
> somewhere?
>
The docstring for array_equal should
On Fri, Nov 25, 2022 at 9:55 PM Serge Guelton
wrote:
> On Fri, Nov 25, 2022 at 08:09:02PM +0100, Sebastian Berg wrote:
> > Thanks for bringing this up again. The Python method exists and it
> > seems like relatively basic functionality.
> >
> > Overall, I am slightly in favor of adding the ufunc
Hi all,
I'm excited to be able to share this announcement on behalf of the NumPy
Steering Council. We have created a new program, the NumPy Fellowship
Program, and offered Sayed Adel the very first Developer in Residence role.
Sayed starts his 1 year tenure in that role today, and we are really
lo
the
beginner/average user, it will have few users right now, and as long as the
correspondence is mentioned in the docstring this should be discoverable
enough. I'd much prefer no alias, we already have way too many of those and
most of them are only noise at this point.
Cheers,
Ralf
> Thank
On Wed, Dec 7, 2022 at 11:51 PM Ilhan Polat wrote:
>
> On matrix_transpose() :
> Every time this discussion brought up, there was a huge resistance to add
> more methods to array object or new functions (I have been involved in some
> of them on the pro .H side, links you have given and more in t
On Mon, Dec 12, 2022 at 4:44 PM 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 part of the array API
> > standard https://d
On Wed, Dec 21, 2022 at 12:04 PM Andrew Nelson wrote:
> On Wed, 21 Dec 2022 at 20:40, Matti Picus wrote:
>
>> Maybe we should have a scientific-python wide discussion of what
>> platforms we wish to support, like NEP 29 for python versions. The NEP
>> should include some mechanism for adding new
On Sun, Dec 25, 2022 at 12:20 AM wrote:
> Hello,
>
> I hope this is the right forum on which to post this, but if not please
> let me know.
>
> I'll be starting a PhD program in mathematics in the fall, and I'm looking
> for something to occupy part of my time until then.
>
> I've been programmin
*: Many users, but hopefully not most as one needs to use
>smaller than default precision types to be affected.
>
> <#m_-4971028583323681657_A-thorough-cleanup-of-the-Python-API>A thorough
> cleanup of the Python API
> The NumPy API is quite messy, with ma
On Mon, Jan 16, 2023 at 3:28 PM Mark Harfouche
wrote:
> I am trying to create a few different duck arrays that are backed by
> different files.
>
> Is there a standard test suite that we can inspire ourselves from that
> helps us assert:
>
> "Arrays should implement all these different functions
On Fri, Feb 10, 2023 at 5:35 PM Nathan wrote:
>
>
> On Fri, Feb 10, 2023 at 3:31 AM Sebastian Berg
> wrote:
>
>> Hi all,
>>
>> I was wondering if we should introduce a new `np.types` namespace. The
>> main reason is that we have the DType classes, that most users don't
>> need to worry about.
On Mon, Feb 13, 2023 at 11:33 AM Sebastian Berg
wrote:
> On Sat, 2023-02-11 at 11:24 +0000, Ralf Gommers wrote:
> > On Fri, Feb 10, 2023 at 5:35 PM Nathan
> > wrote:
> >
>
>
> > > >
> > >
> > > Small bikeshed: the name np.types ind
On Tue, Feb 14, 2023 at 9:08 PM Stefan van der Walt
wrote:
> On Tue, Feb 14, 2023, at 12:27, Ralf Gommers wrote:
>
> Okay, as long as we keep in mind that it should contain all these
> not-for-main-namespace functions/classes, it seems fine with me. We can
> live with two namespac
Hi all,
In https://github.com/numpy/numpy/pull/23314 I am deprecating four
functions: `product`, `cumproduct`, `alltrue`, `sometrue`. These are all
aliases (for `prod`, `cumprod`, `all` and `any`), were already not part of
the API docs, and there was an open issue for deprecating them (
https://gi
On Mon, Mar 6, 2023 at 8:12 AM Sebastian Berg
wrote:
> On Thu, 2023-03-02 at 15:20 +0000, Ralf Gommers wrote:
> > Hi all,
> >
> > In https://github.com/numpy/numpy/pull/23314 I am deprecating four
> > functions: `product`, `cumproduct`, `alltrue`, `sometrue`. These a
On Tue, Mar 7, 2023 at 1:02 PM Sebastian Berg
wrote:
> On Tue, 2023-03-07 at 12:17 +0000, Ralf Gommers wrote:
> > On Mon, Mar 6, 2023 at 8:12 AM Sebastian Berg <
> > sebast...@sipsolutions.net>
> > wrote:
> >
> > > On Thu, 2023-03-02 at 15:20
Hi all,
In https://github.com/numpy/numpy/pull/23364 we touched on the
NUMPY_EXPERIMENTAL_ARRAY_FUNCTION environment variable. This was a
temporary feature during the introduction of `__array_function__` (see NEP
18), but we never removed it. I propose we do so now, since it is
cumbersome to have
e as well.
>
> Von meinem iPhone gesendet
>
> Am 10.03.2023 um 19:10 schrieb Stephan Hoyer :
>
>
> +1 for removing this environment variable. It was never intended to stick
> around this long.
>
> On Fri, Mar 10, 2023 at 6:48 AM Ralf Gommers
> wrote:
>
>&
On Thu, Mar 16, 2023 at 7:57 PM Sergio Callegari
wrote:
> I am trying to use the `clip` method to transform floats to integers with
> clipping. I was expecting to be able to do both the clipping and the type
> conversion at once, passing the `dtype` parameter to `clip`, together with
> a suitable
Hi all,
We received a notification from Docker that there Free Team organization no
longer exists, and that we have until April 14 to upgrade to a paid tier.
We only use Docker to support Gitpod. Gitpod builds have been broken in
main for quite a while (see
https://github.com/numpy/numpy/actions/w
On Tue, Mar 21, 2023 at 12:20 PM Klaus Zimmermann
wrote:
> Hi,
>
> this sounds all reasonable to me, and as mostly a lurker on this list my
> input shouldn't carry too much weight anyway.
>
> I wanted to point out one thing: Docker does continue to offer free
> access for Open Source projects, it
On Thu, Mar 23, 2023 at 1:55 AM Clemens Brunner
wrote:
> Hello!
>
> I recently got a new MacBook Pro with an M2 Pro CPU (ARM64). When I ran
> some numerical computations (ICA to be precise), I was surprised how slow
> it was - way slower than e.g. my almost 10 year old Intel Mac. It turns out
> t
On Thu, Mar 23, 2023 at 10:43 AM Clemens Brunner
wrote:
> Thanks Ralf, this sounds great! Just making sure I understand, this means
> that for macOS 13, we have to enable Accelerate by building NumPy from
> source.
Indeed. Either that, or use a packaging system that's more capable in this
regar
On Mon, Mar 20, 2023 at 9:09 PM Ralf Gommers wrote:
>
> So my proposal is to drop all the Docker Hub and Gitpod related code and
> docs. I have already discussed this with Tania Allard, who did most of the
> heavy lifting on the initial creation of the Gitpod machinery (for SciPy,
Hi all,
As part of this meeting we have reserved a 30 minute slot for lightning
talks. Those can be for topics that are on our tentative roadmap already
(see https://github.com/orgs/numpy/projects/9/views/1), or topics that
you'd like to add to that roadmap and would like to drive and pitch to the
you are still using the old version of the library if you did not do
that. This is not entirely trivial to do now; I expect we'll see a PR to
enable the new libraries quite soon.
Cheers,
Ralf
>
> Best,
> Jerry
>
>
> On Thu, Mar 23, 2023 at 3:52 AM Ralf Gomme
Hi all,
Stéfan and I wrote a NEP about cleaning up the Python API for the NumPy 2.0
release. It was first presented at the NumPy 2.0 developer meeting last
month, and more review comments came in on
https://github.com/numpy/numpy/pull/23537. It seems about ready to propose
for wider review here an
On Tue, May 23, 2023 at 2:26 PM asyropoulos--- via NumPy-Discussion <
numpy-discussion@python.org> wrote:
> Hello,
>
> I am using Python 3.10.0 on OpenIndiana and yesterday I tried to install
> numpy in my system. The command
>
> /opt/gnu/python/bin/python3.10 -m pip install --user numpy
>
> fail
On Wed, May 31, 2023 at 12:28 PM Chris Sidebottom
wrote:
> Matthew Brett wrote:
> > Hi,
> > On Wed, May 31, 2023 at 8:40 AM Matti Picus matti.pi...@gmail.com wrote:
> > > On 31/5/23 09:33, Jerome Kieffer wrote:
> > > Hi Sebastian,
> > > I had a quick look at the PR and it looks like you re-implem
On Wed, May 31, 2023 at 4:19 PM Charles R Harris
wrote:
>
>
> On Wed, May 31, 2023 at 8:05 AM Robert Kern wrote:
>
>> I would much, much rather have the special functions in the `np.*`
>> namespace be more accurate than fast on all platforms. These would not
>> have been on my list for general p
On Fri, Jun 2, 2023 at 1:51 PM Ronald van Elburg
wrote:
> Aha, the unnecessary copy mentioned in the
> https://dbs.ifi.uni-heidelberg.de/files/Team/eschubert/publications/SSDBM18-covariance-authorcopy.pdf.
> paper is a copy of the input. Here it is about discarding a valuable output
> (the mean)
On Mon, Jun 26, 2023 at 6:57 AM Kai Striega wrote:
> Hi Stefan,
>
> I'm interested in going that direction, or rather, getting the functions
> out of NumPy. I'm not sure if it's feasible to rip these functions out of
> NumPy itself – or how much work it would require. Last week I spent some
> tim
601 - 700 of 734 matches
Mail list logo
