On 3/24/06, Nick Coghlan <ncoghlan at gmail.com> wrote: > I do find it somewhat interesting that we're considering moving the standard > containers to a more numpy-ish view of the world, though (i.e. one where > multiple mutable views of a data structure are common in order to avoid > unnecessary copying) > > Would that philosophy be extended to slicing operations, though? That's a question I hadn't though about yet. I'm not sure I like it, but it sure is consistent with other view APIs; like everywhere, if you need a separate object, you can place a list() around it. -- --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4