On Fri, Oct 27, 2017 at 01:59:01PM -0700, Ilya Kulakov wrote:
> Since one of the legit use-cases of using the Thread class is subclassing,
> I think it's __init__ should call super() to support cooperative inheritance.
>
> Or perhaps there is a good reason for not doing so?
Are you talking about
You can subclass Thread just fine, you just can't have it in a multiple
inheritance hierarchy except at the end of the MRO (before object). That
shouldn't stop you from doing anything you want though -- you can define
e.g.
class MyThread(Thread):
def __init__(self, *args, **kwds):
Thre
Since one of the legit use-cases of using the Thread class is subclassing,
I think it's __init__ should call super() to support cooperative inheritance.
Or perhaps there is a good reason for not doing so?
Best Regards,
Ilya Kulakov
___
Python-ideas mai
We’ve made a small change to the PEP process which may affect readers of
python-list and python-ideas, so I’d like to inform you of it. This change was
made to PEP 1 and PEP 12.
PEPs must have a Post-History header which records the dates at which the PEP
is posted to mailing lists, in order t
