[Numpy-discussion] convertcode.py and float defaults

Sasha ndarray at mac.com
Sat Jul 1 15:28:11 CDT 2006

I don't see how that will simplify the transition.  Convertcode will
still need to detect use of the dtype argument (keyword or
positional).  Simple s/zeros/int.zeros/ will not work. I read Ed's
suggestion as retaining current default in intzeros so that
intzeros(n, float) is valid.  On the other hand Tim's int.zeros would
not take dtype argument because dtype is already bound as self.

The bottom line: int.zeros will not work and intzeros(n, float) is
ugly. I would not mind oldnumeric.zeros, but context aware convertcode
is still worth the effort.  Let's see how far I will get with that ...

On 7/1/06, Alan G Isaac <aisaac at american.edu> wrote:
> On Sat, 1 Jul 2006, Ed Schofield apparently wrote:
> > couldn't we make the transition easier and more robust by
> > writing compatibility interfaces for zeros, ones, empty,
> > called e.g.  intzeros, intones, intempty
> I think Robert or Tim suggested int.zeros() etc.
> fwiw,
> Alan Isaac
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Numpy-discussion mailing list
> Numpy-discussion at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/numpy-discussion

More information about the Numpy-discussion mailing list