Some initial thoughts about the past week's discussions
![](https://secure.gravatar.com/avatar/c7976f03fcae7e1199d28d1c20e34647.jpg?s=120&d=mm&r=g)
Impressions so far on various issues raised regarding numarray interfaces 1) We are mostly persuaded that rank-0 arrays are the way to go. We will pursue the issue of whether it is possible to have Python accept these as indices for sequence objects with python-dev. 2) We are still mulling over the axis order issue. Regardless of which convention we choose, we are almost certainly going to make it consistent (always the same axis as default). A compatibility module will be provided to replicate Numeric defaults. 3) repr. Finally, a consensus! Even unanimity. 4) Complex comparisons. Implement equality, non-equality, predictable sorting. Make >,<,>=,<= illegal. 5) Copy vs view. Open to more input (but no delayed copying or such). Perry
![](https://secure.gravatar.com/avatar/aeed615c41c6957795dd3546882d5bb2.jpg?s=120&d=mm&r=g)
My preference would be Copy semantics for a=b View semantics for a=b.view (or some other explicit syntax) Bernie
![](https://secure.gravatar.com/avatar/eb281ac8437ba6df4ef5f0f9686e7c3e.jpg?s=120&d=mm&r=g)
Bernard Frankpitt <frankpit@erols.com> writes:
Although I have been arguing for copy semantics for a=b[c:d], what you want is not really possible (a=b creates and always will create an alias in python -- and this is really a good design decision; just compare it to other languages that do different things depending on what you are assigning). alex -- Alexander Schmolck Postgraduate Research Student Department of Computer Science University of Exeter A.Schmolck@gmx.net http://www.dcs.ex.ac.uk/people/aschmolc/
![](https://secure.gravatar.com/avatar/aeed615c41c6957795dd3546882d5bb2.jpg?s=120&d=mm&r=g)
My preference would be Copy semantics for a=b View semantics for a=b.view (or some other explicit syntax) Bernie
![](https://secure.gravatar.com/avatar/eb281ac8437ba6df4ef5f0f9686e7c3e.jpg?s=120&d=mm&r=g)
Bernard Frankpitt <frankpit@erols.com> writes:
Although I have been arguing for copy semantics for a=b[c:d], what you want is not really possible (a=b creates and always will create an alias in python -- and this is really a good design decision; just compare it to other languages that do different things depending on what you are assigning). alex -- Alexander Schmolck Postgraduate Research Student Department of Computer Science University of Exeter A.Schmolck@gmx.net http://www.dcs.ex.ac.uk/people/aschmolc/
participants (3)
-
Alexander Schmolck
-
Bernard Frankpitt
-
Perry Greenfield