[Python-Dev] Testing C API (original) (raw)
Victor Stinner vstinner at redhat.com
Mon Jul 30 18:32:00 EDT 2018
- Previous message (by thread): [Python-Dev] Testing C API
- Next message (by thread): [Python-Dev] Using Python on a fork-less POSIX-like OS
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Actually, I mean -m test --match 'test_*_capi' where --match can also be written -m.
It may catch false positive since the filter is also applied to test case names and test method names.
Maybe 'test_*_capi.*' is better, I didn't try.
You may using use "ls Lib/test/test_*_capi.py > tests; ./python -m test --fromfile tests".
There are different options.
By the way, running the full test suite just takes 5 min on my laptop, it isn't so long ;-)
Victor
Le lundi 30 juillet 2018, Nick Coghlan <ncoghlan at gmail.com> a écrit :
On 30 July 2018 at 21:23, Victor Stinner <vstinner at redhat.com> wrote:
Or maybe testcapi.py so you can more easily discover testunicodecami while working on Unicode. You can use -m "test*capi" to run all C API tests. Missing word there: -m test "test*capi" I think between this approach and expanding testcapi to be a test package, not just a test file, I think it would be possible to make these parts of the test a fair bit more discoverable and maintainable. Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-dev/attachments/20180731/1681b70f/attachment.html>
- Previous message (by thread): [Python-Dev] Testing C API
- Next message (by thread): [Python-Dev] Using Python on a fork-less POSIX-like OS
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]