Comments on: One Code Styleguide Per Programming Language Is Not Silly http://lucumr.pocoo.org/cogitations/2007/11/04/one-code-styleguide-per-programming-language-is-not-silly/ Armin Ronacher thinking Sat, 11 Oct 2008 12:02:13 +0000 http://wordpress.org/?v=2.2 By: mq http://lucumr.pocoo.org/cogitations/2007/11/04/one-code-styleguide-per-programming-language-is-not-silly/#comment-717 mq Sat, 10 Nov 2007 16:06:26 +0000 http://lucumr.pocoo.org/cogitations/2007/11/04/one-code-styleguide-per-programming-language-is-not-silly/#comment-717 Fully agreed. The names in the stdlib suck, and it sucks even more that many people and libraries don't adapt the PEP 8 style. Fully agreed. The names in the stdlib suck, and it sucks even more that many people and libraries don’t adapt the PEP 8 style.

]]> By: Brett http://lucumr.pocoo.org/cogitations/2007/11/04/one-code-styleguide-per-programming-language-is-not-silly/#comment-683 Brett Sun, 04 Nov 2007 19:50:14 +0000 http://lucumr.pocoo.org/cogitations/2007/11/04/one-code-styleguide-per-programming-language-is-not-silly/#comment-683 The biggest problem is that PEP 8 was not around when a bunch of stuff went into the stdlib (it didn't come until being until July 2001 which is over 11.5 years after Python's creation). While the module names will get fixed in Python 3.0, changing method and functions are harder as those can't be automated. Hopefully we can, at some point, either rename methods and function slowly, or just replace/remove old modules. The biggest problem is that PEP 8 was not around when a bunch of stuff went into the stdlib (it didn’t come until being until July 2001 which is over 11.5 years after Python’s creation). While the module names will get fixed in Python 3.0, changing method and functions are harder as those can’t be automated.

Hopefully we can, at some point, either rename methods and function slowly, or just replace/remove old modules.

]]>