I've noticed, but it just seems like they are trying to do multiple things with one function, which doesn't look like to be in the zen of python. . I'd reckon they should've supported extended slicing with the __getslice__ method.
On Thu, Apr 19, 2012 at 5:10 PM, Ronald Oussoren <ronaldousso...@mac.com>wrote: > > On 19 Apr, 2012, at 16:10, Dexter wrote: > > > Hi, > > > > So they're re-factoring python a bit, some backwards (incompatible) > changes to fix certain inconsistencies. > > And I also knew that some other inconsistencies aren't gonna be changed, > because of backwards incompatibility. > > But I didn't know that they were also introducing inconsistencies, which > is also breaking backwards compatibility. > > > > getslice is being depricated, if you wanna use that, you should use > getitem in p3k. So now, you should check if your argument is an index or a > slice. > > Can anyone explain why? > > __getslice__ doesn't support extended slicing (obj[start:stop:step]) > > Ronald > > > _______________________________________________ > Python-nl mailing list > Python-nl@python.org > http://mail.python.org/mailman/listinfo/python-nl > >
_______________________________________________ Python-nl mailing list Python-nl@python.org http://mail.python.org/mailman/listinfo/python-nl
