[Python-Dev] PEP 371: Additional Discussion (original) (raw)
Guido van Rossum guido at python.org
Wed Jun 4 06:37:27 CEST 2008
- Previous message: [Python-Dev] PEP 371: Additional Discussion
- Next message: [Python-Dev] PEP 371: Additional Discussion
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Tue, Jun 3, 2008 at 6:56 PM, Raymond Hettinger <python at rcn.com> wrote:
From: "Mike Klaas" <mike.klaas at gmail.com>
A cleaner way to effectuate the transition would be to leave the camelCase API in 2.6 (for both modules), switch to PEP 8 in py3k (for both modules) +1 That makes good sense.
No. It makes no sense to introduce a new API in 2.6 and change it again in 3.0. That sounds like another foolish consistency.
, and provide threading3k and multiprocessing3k modules in 2.6 that façade the 2.6 API with the PEP 8 API. +0 PEP 8 is nice but it's not that important.
Raymond
Python-Dev mailing list Python-Dev at python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/guido%40python.org
-- --Guido van Rossum (home page: http://www.python.org/~guido/)
- Previous message: [Python-Dev] PEP 371: Additional Discussion
- Next message: [Python-Dev] PEP 371: Additional Discussion
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]