Hi All,
On behalf of the NumPy team, I am pleased to announce the release of
NumPy 1.23.3. NumPy 1.23.3 is a maintenance release that fixes bugs
discovered after the 1.23.2 release. There is no major theme for this
release, the main improvements are for some downstream builds and some
annotation
On Thu, 2022-09-08 at 23:19 -0700, Stefan van der Walt wrote:
> I am in favor of such a change. It will make what is returned more
> transparent to users (and reduce confusion for newcomers).
>
> With NEP50, we're already adopting a philosophy of explicit scalar
> usage anyway: no longer
On Thu, 2022-09-08 at 21:15 -0400, Warren Weckesser wrote:
> On 9/8/22, Andrew Nelson wrote:
>
> >
> > For many types, this function makes an attempt to return a string
> > that would yield an object with the same value when passed to
> > eval();
>
> Sebastian, is this an explicit goal of
A naive question: what actually are the differences, what an end user need
to worry about when mixing python scalars and numpy scalars? Same question
about a library author.
Or is it mainly about fixed-width integers vs python integers?
Cheers,
Evgeni
пт, 9 сент. 2022 г., 09:58 Kevin Sheppard :
+1 from me. They are a frequent source of confusion when starting, and
there appear to be far fewer now then in earlier releases. It also might
make it easier to spot any inadvertent scalars coming out if these could be
Python floats.
Kevin
On Fri, Sep 9, 2022, 07:23 Stefan van der Walt
I am in favor of such a change. It will make what is returned more transparent
to users (and reduce confusion for newcomers).
With NEP50, we're already adopting a philosophy of explicit scalar usage
anyway: no longer pretending or trying to make transparent that Python floats
and NumPy floats
