On Thu, Jul 23, 2009 at 8:57 AM, Jean-Paul Calderone<exar...@divmod.com> wrote: > On Thu, 23 Jul 2009 14:23:56 +0200, Christian Heimes <li...@cheimes.de> > wrote: >> >> Nick Coghlan wrote: >>> >>> I see ctypes as largely useful when you want to call a native DLL but >>> don't have any existing infrastructure for accessing native code from >>> your project. A few lines of ctypes code is then a much better solution >>> than adding a C or C++ compilation dependency just to access a couple of >>> functions. >>> >>> Of course, that definitely isn't the case for CPython - we not only have >>> plenty of existing C infrastructure, but in the specific case of >>> subprocess on Windows we already have a dedicated extension module >>> (PC/_subprocess.c). >> >> You've hit the nail on the head! That's it. >> > > True, CPython has C infrastructure. What about the other Python runtimes, > though? At the language summit, there was a lot of discussion (and, I > thought, agreement) about moving the standard library to be a collaborative > project between several of the major runtime projects. A ctypes-based > solution seems more aligned with this goal than more C code. > > Jean-Paul
Yeah, I remember that too - all of us discussed "breaking out" the stdlib post mercurial migration to be shared amongst all of the implementations, marking CPython things as "CPython only" and so on. That way we all have a common base to work from. jesse _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
