[Numpy-discussion] bug in ndarray.resize?

Sebastian Haase seb.haase at gmail.com
Thu Mar 18 04:56:21 EDT 2010

On Wed, Mar 17, 2010 at 10:56 PM, Charles R Harris
<charlesr.harris at gmail.com> wrote:
> On Wed, Mar 17, 2010 at 8:42 AM, Alan G Isaac <aisaac at american.edu> wrote:
>> On 3/17/2010 10:16 AM, josef.pktd at gmail.com wrote:
>> > numpy.resize(a, new_shape)
>> > Return a new array with the specified shape.
>> >
>> > If the new array is larger than the original array, then the new array
>> > is filled with repeated copied of a. Note that this behavior is
>> > different from a.resize(new_shape) which fills with zeros instead of
>> > repeated copies of a.
>> Yes indeed.  Sorry, I must have scrolled the help without realizing it,
>> and this part was at the top.
>> So my follow up: why is this desirable/necessary?  (I find it surprising.)
> IIRC, it behaved that way in Numeric.
How would people feel about unifying the function vs. the method behavior ?
One could add an addition option like
`repeat` or `fillZero`.
One could (at first !?) keep opposite defaults to not change the
current behavior.
But this way it would be most visible and clear what is going on.

Sebastian Haase

More information about the NumPy-Discussion mailing list