On Fri, 2022-10-28 at 10:54 +0200, 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)` in
On Mon, 2022-10-31 at 13:49 -0600, Aaron Meurer wrote:
> I like this. NumPy scalar printing is confusing to new users, who
> might think they are Python scalars. And even if you understand them,
> it's always been annoying that you have to do further introspection
> to
> see the dtype. I also like
On Mon, Oct 31, 2022 at 12:51 PM Aaron Meurer wrote:
> I like this. NumPy scalar printing is confusing to new users, who
> might think they are Python scalars. And even if you understand them,
> it's always been annoying that you have to do further introspection to
> see the dtype. I also like th
I like this. NumPy scalar printing is confusing to new users, who
might think they are Python scalars. And even if you understand them,
it's always been annoying that you have to do further introspection to
see the dtype. I also like the longdouble change (the name float128
has misled me in the pas
On Fri, Oct 28, 2022, at 01:54, Sebastian Berg wrote:
> The main change is to show scalars as:
>
> * `np.float64(3.0)` instead of just `3.0`
> * `np.True_` instead of `True`
> * `np.void((3, 5), dtype=[('a', ' `(3, 5)`
> * Use `np.` rather than `numpy.` for datetime/timedelta.
I very much like
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
