On 6/12/10 12:21 AM, Martin v. Loewis wrote:
>> Otherwise it makes certain windows-workarounds very problematic. You
>> basically /have/ to write a C extension :|
> 
> That's not problematic at all, for the standard library. Just write that
> C extension.

Come now, of course it is. It may not be problematic for *you*, but it
*is* problematic for a lot of people.

The pool of people competent to write solid, Pythonic, capable Python
code and contribute it-- then add a few lines of ctypes for a
windows-specific workaround-- is surely larger then the pool of people
competent to write a safe C extension.

I know I only *barely* fit into the latter category.

Maybe Cython'll be mature enough eventually that the stdlib could accept
Cython-based "C" extensions for such cases.

-- 

   Stephen Hansen
   ... Also: Ixokai
   ... Mail: me+list/python (AT) ixokai (DOT) io
   ... Blog: http://meh.ixokai.io/

Attachment: signature.asc
Description: OpenPGP digital signature

-- 
http://mail.python.org/mailman/listinfo/python-list

Reply via email to