[Numpy-discussion] numpy 2.0, what else to do?

David Cournapeau cournape@gmail....
Sat Feb 13 17:23:50 CST 2010


On Sun, Feb 14, 2010 at 1:24 AM, Charles R Harris
<charlesr.harris@gmail.com> wrote:
> Hi All,
>
> Since there has been talk of deprecating the numarray and numeric
> compatibility parts of numpy for the upcoming 2.0 release I thought maybe we
> could consider a few other changes. First, numpy imports a ton of stuff by
> default and this is maintained for backward compatibility. Would this be a
> reasonable time to change that and require explicit imports for things like
> fft? Second, Poly1D has problems that aren't likely to get fixed, I would
> like to both deprecate the old polynomial support and make it not be
> imported by default.

I think that there should be absolutely no change whatsoever, for two reasons:
 - the release is in a few weeks, it is too late to change much. The
whole datetime issue happened because the change came too late, I
would hope that we avoid the same mistake.
 - there was an agreement that with py3k support, nothing would be
changed in a backward incompatible way, that's also the official
python policy for py3k transition.

Deprecations are fine, though,

cheers,

David


More information about the NumPy-Discussion mailing list