[Python-Dev] testing in a Python --without-threads build (original) (raw)

Nicholas Bastin nick.bastin at gmail.com
Sun Sep 9 05:05:23 CEST 2007

Might expected skips instead be based on your current configuration instead of what someone statically decided what would be appropriate for your platform? Every new release I have to go through the 'unexpected skips' to determine that they're perfectly fine for how I configured python.

It seems that we ought to provide a mechanism for querying python for how the build was configured (although for non-unittest cases, failing to import some modules is usually sufficient information - knowing why they fail probably doesn't matter)

On 9/8/07, "Martin v. Löwis" <martin at v.loewis.de> wrote:

>> I can't seem to run the regression tests in a --without-threads build. >> Might be interesting to configure a buildbot this way to keep >> ourselves honest. > > Because regrtest.py was importing testsocketssl without catching the > ImportError exception:

If that is the reason you cannot run it, then it seems it works just fine. There is nothing wrong with tests getting skipped. > So, is this an "expected skip" or not? No. IIUC, "expected skips" are a platform property. For your platform, support for threads is expected (whatever your platform is as log as it was built in this millenium). Regards, Martin

Python-Dev mailing list Python-Dev at python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/nick.bastin%40gmail.com

More information about the Python-Dev mailing list