This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author serhiy.storchaka
Recipients ezio.melotti, georg.brandl, serhiy.storchaka
Date 2012-11-16.11:07:16
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1353064036.99.0.24139295359.issue16478@psf.upfronthosting.co.za>
In-reply-to
Content
> The patch looks OK, buy can you provide a way to reproduce the error (if you get any)?

No, I have not any. I am even not sure tabnanny works at all. But this bug is obvious. So, let's fix it and go on.

> Should we add tests for tabnanny?

This will be good, but it is a different issue. I'm not ready to write a test.

> I tried to get an error from tabnanny but the only thing I got was a ResourceWarning (that can be easily fixed by a finally: f.close() near the end of the check() method).

I can't see a ResourceWarning. A "finally: f.close()" already exists near the end of the check() method.
History
Date User Action Args
2012-11-16 11:07:17serhiy.storchakasetrecipients: + serhiy.storchaka, georg.brandl, ezio.melotti
2012-11-16 11:07:16serhiy.storchakasetmessageid: <1353064036.99.0.24139295359.issue16478@psf.upfronthosting.co.za>
2012-11-16 11:07:16serhiy.storchakalinkissue16478 messages
2012-11-16 11:07:16serhiy.storchakacreate