Message 298281 - Python tracker

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.

Content
I'll accept this as a backport for 3.4.  I'm convinced that, although the sample programs don't crash in release builds, the behavior is wrong and could be exploited.

Will someone have time to create the PR in the next day or two?  (It's not that it's necessary, but it seems that Victor and Serhiy are very quick, which is nice.  And adding it sooner will make it more comfortable to tag and release 3.4.7rc1 next weekend, which I think I'm going to do.)