[Python-Dev] Further PEP 8 compliance issues in threading and multiprocessing (original) (raw)
Greg Ewing greg.ewing at canterbury.ac.nz
Wed Sep 3 02:38:40 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 ]
Steven D'Aprano wrote:
Why not expose the class directly, instead of making it private and then exposing it via a factory function that does nothing else?
This option would also have the advantage of not changing the API (unless there's code out there that actually depends on them not being classes, and that seems rather unlikely).
-- Greg
- 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 ]