[issue24553] improve test coverage for subinterpreters

Eric Snow added the comment: Note that bpo-32604 is strongly related. -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue24553] improve test coverage for subinterpreters

Stefan Krah added the comment: +1 for python -m test.subinterpretertest. Based on my experiments, most tests will either fail or leak memory at the very least. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24553

[issue24553] improve test coverage for subinterpreters

Nick Coghlan added the comment: As a possible starting point for this, I'll point to https://hg.python.org/cpython/file/02b81a82a57d/Lib/test/__main__.py Now, I'd expected running that in a process that was *already* running regrtest to fail miserably (it would stomp all over itself). But

[issue24553] improve test coverage for subinterpreters

Stefan Krah added the comment: Nick, this may be a misunderstanding, but you mentioned issues that PEP 489 did not address yet. The only issue left for _decimal is the speed issue. Sub-interpreter tests run fine even with the existing module state API, *if* one is willing to take a speed hit.

[issue24553] improve test coverage for subinterpreters

Nick Coghlan added the comment: Adding Petr Viktorin to the nosy list as well, as the kind of issues Stefan mentions there are the kinds of things that the PEP 489 extension module import issues *didn't* address yet, but we'd like to address in the 3.6 iteration of the multi-phase

[issue24553] improve test coverage for subinterpreters

Stefan Krah added the comment: I think for fast access we need a hybrid solution that allows static types (heap types slowed down _decimal) *and* cache the thread local values (like it's currently done for the thread-local context in _decimal). Caching the context brought an enormous speedup

[issue24553] improve test coverage for subinterpreters

Nick Coghlan added the comment: That's jumping ahead a little - this issue is only about running the regression test suite from a subinterpreter, and establishing what *already* works properly. Dealing with the fallout of any quirks and outright failures we discover that way will be a

[issue24553] improve test coverage for subinterpreters

Stefan Krah added the comment: Now I'm wondering what further test coverage we really need... Ideally we'd test every C module with the tests executing in parallel (sort of) in multiple interpreters. I have done so for _decimal, which is mostly okay due to the thread-local contexts. However,

[issue24553] improve test coverage for subinterpreters

Nick Coghlan added the comment: Sorry about the misleading reference to tracemalloc in my email - it was actually test_atexit I was debugging in the PEP 432 branch. tracemalloc only came up in that context because test.support.run_in_subinterp() automatically skips subinterpreter tests when

[issue24553] improve test coverage for subinterpreters

Eric Snow added the comment: FTR, subinterpreters are already accessible during testing with _testcapi.run_in_subinterp(). * https://hg.python.org/cpython/file/09b223827f63/Modules/_testcapimodule.c#l2615 That function is used here: * Lib/test/test_threading.py *

[issue24553] improve test coverage for subinterpreters

Eric Snow added the comment: Now I'm wondering what further test coverage we really need... -- status: open - pending ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24553 ___

[issue24553] improve test coverage for subinterpreters

Eric Snow added the comment: Also, I was mistaken about test_tracemalloc. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue24553 ___ ___

[issue24553] improve test coverage for subinterpreters

Nick Coghlan added the comment: There are some basic tests in test_capi as well: * https://hg.python.org/cpython/file/09b223827f63/Lib/test/test_capi.py#l344 * https://hg.python.org/cpython/file/default/Programs/_testembed.c -- ___ Python tracker

[issue24553] improve test coverage for subinterpreters

New submission from Eric Snow: We do very little testing of subinterpreters in CPython. About all I'm aware of is in test_tracemalloc. I'll be working on improving test coverage as a precursor to fixing some existing bugs. -- components: Tests messages: 246107 nosy: eric.snow,