[issue13171] Bug in tempfile module

2011-10-13 Thread Alexander Steppke
New submission from Alexander Steppke : The tempfile module shows strange behavior under certain conditions. This might lead to data leaking or other problems. The test session looks as follows: Python 2.7.2 (default, Jun 12 2011, 15:08:59) [MSC v.1500 32 bit (Intel)] on win32 Type "

[issue13171] Bug in tempfile module

2011-10-14 Thread Alexander Steppke
Alexander Steppke added the comment: Hi David, I followed your suggestion and tried to reproduce the problem without the tempfile module. It turns out that is indeed an underlying issue. I am not sure what the root cause is but now this is even a bigger problem: read() returns information

[issue13171] Bug in file.read(), can access unknown data.

2011-10-14 Thread Alexander Steppke
Changes by Alexander Steppke : -- components: +IO title: Bug in tempfile module -> Bug in file.read(), can access unknown data. ___ Python tracker <http://bugs.python.org/issu

[issue13171] Bug in file.read(), can access unknown data.

2011-10-14 Thread Alexander Steppke
Alexander Steppke added the comment: Additionally after calling tmp.close() the file 'tmp' contains the string 'test', which is followed by about 4kB of binary data similar to the previous output of tmp.read(). -- ___ P

[issue13171] Bug in file.read(), can access unknown data.

2011-10-14 Thread Alexander Steppke
Alexander Steppke added the comment: Thank you for the update Victor. It seems to me that this is exactly the same issue. At the moment the current documentation says (http://docs.python.org/library/stdtypes.html#bltin-file-objects): "Note: This function is simply a wrapper fo