[Python-Dev] pep8ity future (original) (raw)
Armin Ronacher armin.ronacher at active-4.com
Sat Jun 7 23:10:14 CEST 2008
- Previous message: [Python-Dev] Deprecate parser's "ast" functions?
- Next message: [Python-Dev] pep8ity __future__
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
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
- Previous message: [Python-Dev] Deprecate parser's "ast" functions?
- Next message: [Python-Dev] pep8ity __future__
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]