> This has been fixed on the trunk in response to issue 2021, but I'm not
> sure of the current status of the 2.5 maintenance branch. Should I wait
> until after 2.5.2 is released before backporting? Or backport it now?
Please backport it now. The code freeze for the 2.5 branch will come
Wednesd
Assuming the fix isn't going to break other things, I'd say now is the
time, unless Martin says otherwise. Waiting until after 2.5.2 doesn't
make a lot of sense -- either it is a backportable fix, or it isn't.
If it is backportable, it can go in as long as the 2.5.2 code freeze
isn't in effect.
On
In 2.5, tempfile.NamedTemporaryFile passes requests for __enter__ and
__exit__ through to the underlying file object, which ends up breaking
in a couple of different ways (by a fortuitous coincidence, it actually
works in most respects on Windows, so tempfile.TemporaryFile will mostly
do the ri
