2008/9/2 Greg Ewing <greg.ewing at canterbury.ac.nz>: > 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). No. Allowing them to be subclassed makes it harder to replace them on some platforms with equivalent but faster implementations. -- --Guido van Rossum (home page: http://www.python.org/~guido/) -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20080903/8ae51b43/attachment.htm>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4