This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author brett.cannon
Recipients brett.cannon, pitrou, r.david.murray
Date 2011-02-10.18:20:49
SpamBayes Score 1.0985551e-08
Marked as misclassified No
Message-id <1297362052.02.0.152444972819.issue10966@psf.upfronthosting.co.za>
In-reply-to
Content
So os.name is also supported. But the point is that if a platform wants to be considered supported then they need to give us a patch to update the tests to make them acceptable to skip.

As for test_ttk and such, those that have a third-party dependency are still optional no matter what. This change is **only** for modules we expect to always build on certain platfoms (e.g., winreg under Windows or crypt on UNIX systems). I mean do we really think ctypes is optional at this point? In general no, only on select platforms where libffi support is lacking. So having the test skip because of a build failure under OS X (like I had for LLVM 2.8 for a while) should not be left behind but instead be considered a failure as ctypes is **supposed** to be supported under darwin. Extension build failure should not always be considered a non-failure.
History
Date User Action Args
2011-02-10 18:20:52brett.cannonsetrecipients: + brett.cannon, pitrou, r.david.murray
2011-02-10 18:20:52brett.cannonsetmessageid: <1297362052.02.0.152444972819.issue10966@psf.upfronthosting.co.za>
2011-02-10 18:20:50brett.cannonlinkissue10966 messages
2011-02-10 18:20:50brett.cannoncreate