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 ncoghlan
Recipients eric.snow, ncoghlan, petr.viktorin
Date 2015-08-25.05:51:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1440481888.38.0.825081560944.issue24932@psf.upfronthosting.co.za>
In-reply-to
Content
Programs/_testembed (invoked by test_capi to test CPython's embedding support) is currently a very simple application with only two different embedding tests: https://hg.python.org/cpython/file/tip/Programs/_testembed.c

In light of proposals like PEP 432 to change the interpreter startup sequence and make it more configurable, it seems desirable to be better able to test more configuration options directly, without relying on the abstraction layer provided by the main CPython executable.

The specific unit testing library that prompted this idea was cmocka, which is used by libssh, sssd and cwrap: https://cmocka.org/

cwrap in turn is used by the Samba team to mock out network interfaces and other operations using LD_PRELOAD: https://cwrap.org/

We don't necessarily have to use those particular libraries, I'm just filing this issue to capture the idea of improving our C level unit testing capabilities, and then updating regrtest to better capture and report those results (currently there are just a couple of tests in test_capi that call the _testembed executable)
History
Date User Action Args
2015-08-25 05:51:28ncoghlansetrecipients: + ncoghlan, petr.viktorin, eric.snow
2015-08-25 05:51:28ncoghlansetmessageid: <1440481888.38.0.825081560944.issue24932@psf.upfronthosting.co.za>
2015-08-25 05:51:28ncoghlanlinkissue24932 messages
2015-08-25 05:51:27ncoghlancreate