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.

On 7/3/15 16:59, Tim Graham wrote:
> Andriy proposed a patch to close objects like StringIO and BytesIO in
> our test suite [1]. I am not sure how much benefit this gives (frees "a
> few bytes of RAM" according to [2]) and it seems to add a lot of
> verbosity. Looking at Python's own test suite, it doesn't appear these
> objects are closed there (I spot checked BytesIO and StringIO). Any
> thoughts on this?
> 
> [1] https://github.com/django/django/pull/4938
> [2] https://github.com/django/django/pull/4248
> 
> -- 
> 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 [email protected]
> <mailto:[email protected]>.
> To post to this group, send email to [email protected]
> <mailto:[email protected]>.
> 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.

-- 
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 [email protected].
To post to this group, send email to [email protected].
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/559697A3.2010002%40asokolovskiy.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to