My vision of that was to have clean code (even if these are few bytes).
Python allows to have memory leaks like this, without throwing warnings,
but if we know that we can close it, I think we should do that.
We're usually writing new tests by copying logic from sibling test (if
new test need to do similar thing).
If that test have unclosed stream or file, new test likely also will not
close streams and files, so this old test is a "bad example",
which causing more unclean code.
So, it question about code style than about bytes savings.
> --
> You received this message because you are subscribed to the Google
> Groups "Django developers (Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to
django-develop...@googlegroups.com
> <mailto:
django-develop...@googlegroups.com>.
> To post to this group, send email to
django-d...@googlegroups.com
> <mailto:
django-d...@googlegroups.com>.
> Visit this group at
http://groups.google.com/group/django-developers.
> To view this discussion on the web visit
>
https://groups.google.com/d/msgid/django-developers/7579ee1c-ecc6-48d1-9002-733810e64754%40googlegroups.com
> <
https://groups.google.com/d/msgid/django-developers/7579ee1c-ecc6-48d1-9002-733810e64754%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit
https://groups.google.com/d/optout.