Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’m writing some tests using StringIO class and just wonder: I can close StringIO instance, since it is actually mimicking IO, but should I really bother? Should I close StringIO instances as I actually should close files?
Well, reads and writes go straight to the underlying string; there’s no extra buffers to flush, and no OS-level resources to return.
The only reason you might want to close the StringIO is to make subsequent IOs fail or if you needed to make
closed?return true, which could be useful if you gave that StringIO to some other component. On the other hand, if you’re just going to discard the StringIO a moment later, it doesn’t matter in the slightest; the garbage collector doesn’t care if it’s marked as open or closed.