[Python-Dev] Rationale for NamedTemporaryFile? (original) (raw)
Gustavo Carneiro gjcarneiro at gmail.com
Wed Mar 21 12:14:29 CET 2007
- Previous message: [Python-Dev] Rationale for NamedTemporaryFile?
- Next message: [Python-Dev] Rationale for NamedTemporaryFile?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 3/21/07, Scott Dial <scott+python-dev at scottdial.com> wrote:
Greg Ewing wrote: > A tangential question -- why are TemporaryFile and > NamedTemporaryFile named in TitleCase, when they're > functions and not classes? > I wondered the same. At first draft of my email I wrote "class" operating under the assumption that only classes got to be camel-cased. If I had to guess, the rationale was that they are simply wrappers a class. Nevertheless, tempfile dates well back before the PEP 8 style guidelines. I think consistency would dictate that a newly added function should match the other ones, but I have no strong feelings about this.
I wouldn't bet on that. The ElementTree XML module was added to Python 2.5 and it does not follow PEP 8 style (method names are not words separated by underscores).
-- Gustavo J. A. M. Carneiro "The universe is always one step beyond logic." -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/python-dev/attachments/20070321/fd423d0d/attachment.htm
- Previous message: [Python-Dev] Rationale for NamedTemporaryFile?
- Next message: [Python-Dev] Rationale for NamedTemporaryFile?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]