[Numpy-discussion] Py3 merge

David Cournapeau cournape@gmail....
Tue Dec 8 05:13:26 CST 2009

On Tue, Dec 8, 2009 at 8:03 PM, Francesc Alted <faltet@pytables.org> wrote:

> That's true, but at least this can be attributed to a poor programming
> practice.  The same happens with:
> array([1]).dtype == 'int32'  # in 32-bit systems
> array([1]).dtype == 'int64'  # in 64-bit systems
> and my impression is that int32/int64 duality for int default would hit much
> more NumPy people than the "U"/"S" for string defaults.

I have not followed this discussion much so far, but I was wondering
whether it would make sense to write our own fixer for 2to3 to handle
some of those issues ? Encoding issues cannot be fixed in 2to3, but
things like changing dtype name should be doable, no ?

I have not looked at the 2to3 code, so I don't know how much work this would be.



More information about the NumPy-Discussion mailing list