[Python-Dev] pep8ity __future__
Armin Ronacher
armin.ronacher at active-4.com
Sat Jun 7 23:10:14 CEST 2008
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 and the
getting rid of all that Java-like naming sounds like a good idea to me :)
If threading/processing gets a pep8ified API with 2.6, why not __future__?
Proposed patch: http://paste.pocoo.org/show/64512/
Regards,
Armin
More information about the Python-Dev
mailing list