On Fri, Jun 14, 2013 at 6:18 PM, Eric Firing <[email protected]> wrote:
> On 2013/06/14 5:15 AM, Alan G Isaac wrote:
>> On 6/14/2013 9:27 AM, Aldcroft, Thomas wrote:
>>> If I just saw np.values(..) in some code I would never guess what it is
>>> doing from the name
>>
>> That suggests np.fromvalues.
>> But more important than the name I think
>> is allowing broadcasting of the values,
>> based on NumPy's broadcasting rules.
>> Broadcasting a scalar is then a special case,
>> even if it is the case that has dominated this thread.
>
> True, but this looks to me like mission creep. All of this fuss is
> about replacing two lines of user code with a single line. If it can't
> be kept simple, both in implementation and in documentation, it
> shouldn't be done at all. I'm not necessarily opposed to your
> suggestion, but I'm skeptical.
It's another two-liner:
[~]
|1> x = np.empty([3,4,5])
[~]
|2> x[...] = np.arange(5)
[~]
|3> x
array([[[ 0., 1., 2., 3., 4.],
[ 0., 1., 2., 3., 4.],
[ 0., 1., 2., 3., 4.],
[ 0., 1., 2., 3., 4.]],
[[ 0., 1., 2., 3., 4.],
[ 0., 1., 2., 3., 4.],
[ 0., 1., 2., 3., 4.],
[ 0., 1., 2., 3., 4.]],
[[ 0., 1., 2., 3., 4.],
[ 0., 1., 2., 3., 4.],
[ 0., 1., 2., 3., 4.],
[ 0., 1., 2., 3., 4.]]])
It's wafer-thin!
--
Robert Kern
_______________________________________________
NumPy-Discussion mailing list
[email protected]
http://mail.scipy.org/mailman/listinfo/numpy-discussion
