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 terry.reedy
Recipients terry.reedy
Date 2009-06-17.00:01:49
SpamBayes Score 1.9373256e-06
Marked as misclassified No
Message-id <1245196911.61.0.437199244327.issue6294@psf.upfronthosting.co.za>
In-reply-to
Content
When (at least sometimes) exceptions occur during shutdown, warnings
like the following appear:
Exception TypeError: "'NoneType' object is not callable" in  ignored

This is apparently meant to be read as 
Exception <<TypeError: "'NoneType' object is not callable" in ...>>
[was] ignored

instead of, for instance
Exception TypeError: "'NoneType' object is not callable" in ignored

Even when parsed correctly, it is a bit mysterious (who/what ignored the
exception?) to one not in the know and has generated more than one
python-list thread.

Suggestion (from John Machin): reword to something like

Shutdown ignored this exception: TypeError: "'NoneType' object is not
callable"

This would tell people that they might need to find out more about the
shutdown process.

Would it be permissible to change this in 3.1?
History
Date User Action Args
2009-06-17 00:01:52terry.reedysetrecipients: + terry.reedy
2009-06-17 00:01:51terry.reedysetmessageid: <1245196911.61.0.437199244327.issue6294@psf.upfronthosting.co.za>
2009-06-17 00:01:50terry.reedylinkissue6294 messages
2009-06-17 00:01:49terry.reedycreate