[New-bugs-announce] [issue34446] ambiguous _max_size parameter in SpooledTemporaryFile

jcc2220 report at bugs.python.org
Mon Aug 20 15:47:35 EDT 2018

New submission from jcc2220 <jcc2220 at columbia.edu>:

When _max_size is set to 0, the _check method will never call rollover, as the conditional for a rollover is never satisfied.  However, in the truncate method, the _max_size is not checked against 0, and so a rollover could be called when it is 0.  This is more of an issue of consistency - should 0 mean that it will never rollover?  If so, truncate should be modified.  Should 0 be interpreted as 'always rollover'?  If so, the _check should be modified.  Personally, I'd rather have something like -1 mean never, 0 mean always, and >0 mean only when greater than specified size.


components: Library (Lib)
messages: 323809
nosy: jcc2220
priority: normal
severity: normal
status: open
title: ambiguous _max_size parameter in SpooledTemporaryFile
type: behavior
versions: Python 3.7

Python tracker <report at bugs.python.org>

More information about the New-bugs-announce mailing list