On Saturday 28 October 2006 14:28, Travis Oliphant wrote: > > Hmm.... I know that the code was changed at some point a few months ago > specifically to this behavior because of some concerns Perry, Chris > (people at STScI) had. Originally, field names came first, but we > changed it so they could set known attributes of a record array even if > they were also field names.
So that I could have a field named 'shape', and modifying r.shape would change the shape of the array, not the content of the field ? That makes sense, but isn't it a bit dangerous ? Shouldn't we have a list of reserved keywords (dtype, shape...) that would raise an exception if used as field names ? ------------------------------------------------------------------------- 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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/numpy-discussion