Path: csiph.com!fu-berlin.de!uni-berlin.de!not-for-mail
From: Maxime S <maxischmeii@gmail.com>
Newsgroups: comp.lang.python
Subject: Re: UserList - which methods needs to be overriden?
Date: Fri, 10 Jun 2016 12:11:05 +0200
Lines: 31
Sender: maximesteisel@gmail.com
Message-ID: <mailman.133.1465553487.2306.python-list@python.org>
References: <b245d88e-9b90-bb90-bd2a-13ee82f7a5c8@shopzeus.com> <CAGgTfkMakty7MohzRwLPpfRJikKBC0osTE83T0hZ9Scn+1NBOA@mail.gmail.com> <1f4d1918-1e38-abba-aca7-830d91d35bd4@shopzeus.com> <njdu7l$mu4$1@ger.gmane.org> <CAGqiJR8z63vXzxmGta1LFtkadhGBWNt0Bzp=c6kSLfxWOcrHSw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <njdu7l$mu4$1@ger.gmane.org>
Precedence: list
Xref: csiph.com comp.lang.python:109778

2016-06-10 10:37 GMT+02:00 Peter Otten <__peter__@web.de>:
>
> Nagy L=C3=A1szl=C3=B3 Zsolt wrote:
>
> > I'm not sure wich one is the best. Peter wrote that UserList was left i=
n
> > collections only for backward compatiblity. This might be a point
>
> I'll take that back. I looked around and found no evidence for my claim.
> Only MutableString was removed during the transition to Python 3.
>
> Sorry for the confusion.
>
>

Up to Python 2.6, the docs of UserList had a note stating that:

This module is available for backward compatibility only. If you are
writing code that does not need to work with versions of Python earlier
than Python 2.2, please consider subclassing directly from the built-in
list type.

This was changed in Python 2.7 to:

When Python 2.2 was released, many of the use cases for this class were
subsumed by the ability to subclass list directly. However, a handful of
use cases remain.

So I think the intention was that the ability to subclass list would remove
the need to subclass UserList, but it was later realised that it is not
totally the case.