a Python/C API testing framework (simple simple)

[bdaf8532-ded6-4d4c-9bb3-51fd76040dc1]

BPO	401162
Nosy	@gvanrossum, @tim-one, @smontanaro, @akuchling
Files	None: None

^{Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.}

Show more details

GitHub fields: ```python assignee = None closed_at = created_at = labels = ['build'] title = 'a Python/C API testing framework (simple simple)' updated_at = user = 'https://bugs.python.org/tmick' ``` bugs.python.org fields: ```python activity = actor = 'jhylton' assignee = 'jhylton' closed = True closed_date = None closer = None components = ['Build'] creation = creator = 'tmick' dependencies = [] files = ['2706'] hgrepos = [] issue_num = 401162 keywords = ['patch'] message_count = 13.0 messages = ['33818', '33819', '33820', '33821', '33822', '33823', '33824', '33825', '33826', '33827', '33828', '33829', '33830'] nosy_count = 7.0 nosy_names = ['gvanrossum', 'tim.peters', 'nobody', 'jhylton', 'skip.montanaro', 'akuchling', 'tmick'] pr_nums = [] priority = 'normal' resolution = None stage = None status = 'closed' superseder = None type = None url = 'https://bugs.python.org/issue401162' versions = [] ```

[bdaf8532-ded6-4d4c-9bb3-51fd76040dc1]

[3772858d-27d8-44b0-a664-d68674859f36]

This patch needs to be modified to use setup.py rather then Makefile.pre.in

[gvanrossum]

Randomly reassigned for review now that 2.1 is open and Skip seems to be too busy to look at this.

[akuchling]

Assuming that the _test module doesn't need anything special to compile (and why should it?), the change to setup.py is simple, adding the following line: exts.append( Extension('_test', ['_testmodule.c']) )

[03bde425-37ce-4291-88bd-d6cecc46a30e]

Will it be possible to include this in 2.1a2?

[03bde425-37ce-4291-88bd-d6cecc46a30e]

MAL added the necessary setup.py entry

[tim-one]

Sorry, but there is a rush! Since Python 2.0 is scheduled to have only 1 beta cycle, if this doesn't make it into the beta (\< 2 weeks, according to the schedule), it's for 2.1 at best. It would be very good to have a start at this (no matter how simple) in place for 2.0.

[tim-one]

Duh, yes, this has been a blind spot. Assigned to Jeremy to assign to someone to do the Unix build changes (sounds like Andrew is begging for it \<wink>).

Checked in derived changes, like so:

Modules/_testmodule.c initial revision: 1.1 test_capi.py initial revision: 1.1 output/test_capi initial revision: 1.1 NEWS new revision: 1.117 PCbuild/_test.dsp initial revision: 1.1 PCbuild/pcbuild.dsw new revision: 1.24 PCbuild/readme.txt new revision: 1.18

[bdaf8532-ded6-4d4c-9bb3-51fd76040dc1]

Here is a proposed patch for a Python/C API testing framework. Simple simple.

Basic Overview:

• add a _test C extension module that exports test functions beginning with 'test_'; NULL and a TestError exception indicates a test failure and Py_None indicate a test pass
• add a testcapi.py test module that calls each of the 'test' exported functions in the '_test' module
• changes to the build system files for Win32 and Unix are includes to build _testmodule.c as a shared extension
• new files: Lib/test/test_capi.py, Lib/test/output/test_capi, Modules/_testmodule.c, and PCbuild/_test.dsp

[bdaf8532-ded6-4d4c-9bb3-51fd76040dc1]

don't use C++ style comments

[bdaf8532-ded6-4d4c-9bb3-51fd76040dc1]

Skip, You seemed to have some interest in this the couple of times it came up on python-dev. I wonder if you might want to review this. No rush, I don't expect this to go in anytime soon. Unless, of course, people just *have* to have it. \<wink>

[bdaf8532-ded6-4d4c-9bb3-51fd76040dc1]

re: delaying to 2.1: doesn't bother me much Should it now be "postponed", Tim?

[smontanaro]

postponed until 2.1