How about: "For convenience, when specifying dtypes the standard Python
type objects ``bool``, ``int``, ``float``, and ``complex`` are accepted as
aliases for the corresponding numpy types."


On Mon, Jun 3, 2013 at 9:31 PM, Robert Kern <notifications@github.com>wrote:

> In numpy/doc/basics.py:
>
> >  complex64   Complex number, represented by two 32-bit floats (real
> >              and imaginary components)
> >  complex128  Complex number, represented by two 64-bit floats (real
> >              and imaginary components)
> > -==========  =========================================================
> > +==========  ==============================
> ============================
> > +
> > +Additionally to ``intc`` the platform dependent C integer types ``short``,
> > +``long``, ``longlong`` and their unsigned versions are defined.
> > +
> > +.. note::
> > +    While not equivalent, in many cases the Python type objects ``bool``,
> > +    ``int``, ``float`` and ``complex`` can be used as synonyms for the
> > +    corresponding (underscore appended) NumPy type.
>
> Anything that consumes a dtype should be converting the Python type
> objects to the corresponding dtype. It's fine to use them. You don't say
> why they are "not equivalent", causing unnecessary fear about using them.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/numpy/numpy/pull/3393/files#r4509154>
> .
>