[Python-Dev] Further PEP 8 compliance issues in threading and multiprocessing (original) (raw)
Benjamin Peterson musiccomposition at gmail.com
Mon Sep 1 17:50:13 CEST 2008
- Previous message: [Python-Dev] Further PEP 8 compliance issues in threading and multiprocessing
- Next message: [Python-Dev] Further PEP 8 compliance issues in threading and multiprocessing
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, Sep 1, 2008 at 10:00 AM, Jean-Paul Calderone <exarkun at divmod.com> wrote:
On Mon, 1 Sep 2008 09:42:06 -0500, Benjamin Peterson
Yes, I believe that pretending that functions are classes is a fairly common idiom in the stdlib and out, so I see no problem leaving them alone. We haven't had any complaints about the threading Event function yet either. :) Here's a complaint. It's surprising that you can't use Event et al with isinstance. This is something I'm sure a lot of people run into (I did, many years ago) when they start to use these APIs. Once you do figure out why it doesn't work, it's not clear how to do what you want, since Event is private.
Does anybody ever complain about not being able to use isinstance on twisted.application.Application? (At least it's documented as a function there.)
Jean-Paul
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/musiccomposition%40gmail.com
-- Cheers, Benjamin Peterson "There's no place like 127.0.0.1."
- Previous message: [Python-Dev] Further PEP 8 compliance issues in threading and multiprocessing
- Next message: [Python-Dev] Further PEP 8 compliance issues in threading and multiprocessing
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]