Dave Opstad wrote:
> I'm happy to submit a feature request, once I figure out how to do it!
http://sourceforge.net/projects/python/
Follow the RFE link.
--
Michael Hoffman
--
http://mail.python.org/mailman/listinfo/python-list
In article <[EMAIL PROTECTED]>,
Michael Hoffman <[EMAIL PROTECTED]> wrote:
> Perhaps you should submit a feature request? It must be time to get rid
> of __setslice__, if not now, then maybe by Python 3.0.
I'm happy to submit a feature request, once I figure out how to do it!
Dave
--
http://m
Dave Opstad wrote:
> There's a workaround for this, namely to include this method:
>
> def __setslice__(self, i, j, seq):
> self.__setitem__(slice(i, j), seq)
>
> That way any custom code I need to include in __setitem__ doesn't have
> to be duplicated in __setslice__. But just out
According to the documentation the __setslice__ method has been
deprecated since Python 2.0. However, if I'm deriving classes from the
builtin list class, I've discovered I can't really ignore __setslice__.
Have a look at this snippet:
>>> cl
