➜

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 vstinner, zach.ware
Date 2017-10-18.15:22:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1508340179.09.0.213398074469.issue31810@psf.upfronthosting.co.za>
In-reply-to
Content 
Recently, a new "cell_set_contents()" public symbol was added by mistake: see bpo-30486. It was quickly noticed by doko, and fixed by me (commit 0ad05c32cc41d4c21bfd78b9ffead519ead475a2).

The problem is that we already have a "make smelly" command to check if Python "leaks" symbols, but this check is not run on our CIs (Travis CI or buildbots).

It would be nice to run automatically this test.
History
Date User Action Args
2017-10-18 15:22:59vstinnersetrecipients: + vstinner, zach.ware
2017-10-18 15:22:59vstinnersetmessageid: <1508340179.09.0.213398074469.issue31810@psf.upfronthosting.co.za>
2017-10-18 15:22:58vstinnerlinkissue31810 messages
2017-10-18 15:22:58vstinnercreate