Guido van Rossum wrote:
I don't see it the same way; this is a terribly unimportant API, so
let's not mess with it. threading.py is worth fixing (a) because it's
so popular, and (b) because some folks insisted that the new
multiprocessing module have an API that is as similar as possible to
threa
I don't see it the same way; this is a terribly unimportant API, so
let's not mess with it. threading.py is worth fixing (a) because it's
so popular, and (b) because some folks insisted that the new
multiprocessing module have an API that is as similar as possible to
threading. IOW The general mora
Hi,
That's just a flaming-sword thread but I want to mention it nonetheless :-)
Basically I propose getting rid of __future__._Feature.getMandatoryRelease()
in favour of __future__._Feature.mandatory. That's backwards compatibile
and much more pythonic. Getters/Setters are considered unpythonic
