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 vstinner
Recipients Dormouse759, docs@python, miss-islington, ncoghlan, petr.viktorin, pitrou, scoder, vstinner
Date 2018-05-25.15:48:02
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
This particular kind of bad traverse is quite easy to write if an extension author doesn't read docs carefully, or has read an old version of them (before the fix here). And resulting errors aren't too obvious. So, there's code to crash early and loudly in "--with-pydebug" for simple oversight cases. See comment at the call site of bad_traverse_test in Objects/moduleobject.c
And since there's code, there's a test to make sure it works :)

Oh ok, it makes sense. Maybe the test should test at least just before spec.loader.create_module(). Maybe using a print().

"Thanks! Didn't know about that one, will keep it in mind for next time!"

The problem is that by default, on Linux, we don't dump core files on the current directory. So such bug is silent on Linux. But it's commonly detected on FreeBSD since I configured the test runner to fail if it leaves a new file.
Date User Action Args
2018-05-25 15:48:02vstinnersetrecipients: + vstinner, ncoghlan, pitrou, scoder, petr.viktorin, docs@python, Dormouse759, miss-islington
2018-05-25 15:48:02vstinnersetmessageid: <>
2018-05-25 15:48:02vstinnerlinkissue32374 messages
2018-05-25 15:48:02vstinnercreate