This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients pakal, pitrou
Date 2010-01-05.19:36:01
SpamBayes Score 0.000139299
Marked as misclassified No
Message-id <1262720218.3289.16.camel@localhost>
In-reply-to <>
> Are there new elements, advocating a status quo on this matter ?

Nothing, it's just lacking a patch from someone interested in the

> On a separate note, I'm confused about the "at most" phrase in the
> current documentation :
> ---
> truncate(size=None)
>     Truncate the file to at most size bytes. size defaults to the
> current file position, as returned by tell()
> ---
> According to what I've read so far, a succesful truncate() call will
> always extend/reduce the file until teh desired size, isn't that so on
> all platforms ?

I suppose it was worded that way because some platforms may not support
extending a file when a parameter larger than the current size is given.
I don't know if such systems are widespread.
Date User Action Args
2010-01-05 19:36:03pitrousetrecipients: + pitrou, pakal
2010-01-05 19:36:01pitroulinkissue6939 messages
2010-01-05 19:36:01pitroucreate