[Python-Dev] PEP 371: Additional Discussion (original) (raw)
Guido van Rossum guido at python.org
Thu Jun 5 19:22:13 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 ]
I've accepted your PEP. I think it still needs some clean-up and perhaps clarification of the agreement reached about API style, but there is nothing now that keeps you from implementing it! Hopefully you'll make the beta release early next week.
--Guido
On Thu, Jun 5, 2008 at 8:10 AM, Jesse Noller <jnoller at gmail.com> wrote:
On Thu, Jun 5, 2008 at 9:53 AM, Nick Coghlan <ncoghlan at gmail.com> wrote:
Jesse Noller wrote:
However, the flip side of this is that no one really "likes" the threading API as-is, so putting the module into the standard library with the matching API simply adds another "broken" API. Provided threading gets a PEP 8 style API in 2.6 (which it looks like it is going to), then I don't see a problem with multiprocessing only providing the new API. Cheers, Nick. Fantastic. If no one has any other arguments to the contrary, I'll run with the new API naming scheme. Now I have a lot of tests and documentation to rewrite. -jesse
-- --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 ]