STINNER Victor <vstin...@python.org> added the comment:
> Automated testing: In order to prevent regressions, I'm interested in hosting > a buildbot for at least one year, hopefully in perpetuity, on which we call > ./configure with ac_cv_posix_semaphores_enabled=no. Can't you tune an unit test to prevent multiprocessing.synchronize to be imported? For example, sys.modules['multiprocessing.synchronize'] = None ensures that "import multiprocessing.synchronize" fails, even if the module exists and works. $ python3 Python 3.8.3 (default, May 15 2020, 00:00:00) >>> import sys >>> sys.modules['multiprocessing.synchronize'] = None >>> import multiprocessing.synchronize Traceback (most recent call last): File "<stdin>", line 1, in <module> ModuleNotFoundError: import of multiprocessing.synchronize halted; None in sys.modules A whole buildbot sounds like an overkill solution to this problem. On the other hand, multiprocessing tests are already ones of the slowest tests of the test suite *because* they try to test all possible combinations. ---------- nosy: +vstinner _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue40692> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
