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 pitrou
Recipients brett.cannon, pitrou, r.david.murray
Date 2011-02-10.19:41:56
SpamBayes Score 1.1115392e-09
Marked as misclassified No
Message-id <1297366914.3719.8.camel@localhost.localdomain>
In-reply-to <1297362052.02.0.152444972819.issue10966@psf.upfronthosting.co.za>
Content
> 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).

Ah, thanks for pointing that out to me. That's certainly better than
what I thought :)

> I mean do we really think ctypes is optional at this point?

Why wouldn't it be? It doesn't offer any essential functionality, and
most applications and libraries certainly don't depend on it.
It's far more optional than zlib (which a bunch of stdlib functionality
relies on) IMO.

What's more, standard C isn't enough to compile ctypes (as you witnessed
with LLVM). So, really, making absence of ctypes a failure sounds too
severe to me.
History
Date User Action Args
2011-02-10 19:41:57pitrousetrecipients: + pitrou, brett.cannon, r.david.murray
2011-02-10 19:41:57pitroulinkissue10966 messages
2011-02-10 19:41:56pitroucreate