| Jim Gallacher 2005-10-25, 5:46 pm |
| Nick wrote:
> More info:
>
> Python 2.4.2 on Linux:
> <open file '<fdopen>', mode 'w+b' at 0xb7df07b8>
> <type 'file'>
> ['__class__', '__delattr__', '__doc__', '__getattribute__', '__hash__',
> '__init__', '__iter__', '__new__', '__reduce__', '__reduce_ex__',
> '__repr__', '__setattr__', '__str__', 'close', 'closed', 'encoding',
> 'fileno', 'flush', 'isatty', 'mode', 'name', 'newlines', 'next', 'read',
> 'readinto', 'readline', 'readlines', 'seek', 'softspace', 'tell',
> 'truncate', 'write', 'writelines', 'xreadlines']
>
> Python 2.4.1 on windows:
> <open file '<fdopen>', mode 'w+b' at 0x0099FBA8>
> <type 'instance'>
> ['__doc__', '__getattr__', '__init__', '__module__', '__repr__',
> 'close_called', 'file', 'name']
>
> So this is an inconsistency within Python. Should mod_python attempt to
> correct it, or just claim a Python bug?
I think we should correct it. I'm sure users don't care that we
implement this with TemporaryFile. That being said, I wonder how many
applications on Windows we may break by fixing this? Version 3.1.4 also
used TemporaryFile, so this is not a new bug.
Jim
[vbcol=seagreen]
> Nick wrote:
>
|