[Python-ideas] discouraging direct use of the C-API

[Florian Bruhin]

* Guido van Rossum <guido at python.org> [2015-05-06 12:28:35 -0700]:
> On Wed, May 6, 2015 at 11:56 AM, Paul Moore <p.f.moore at gmail.com> wrote:
> 
> > On 6 May 2015 at 17:41, Guido van Rossum <guido at python.org> wrote:
> > > As for CFFI, is the ownership/maintenance issue solved yet? IIRC we have
> > > some really outdated versions in the CPython tree and nobody wants to
> > step
> > > in and upgrade these to the latest CFFI, for some reason (such as that
> > that
> > > would actually break a lot of code because the latest version is so
> > > different from the version we currently include?).
> >
> > I think you are referring to libffi (used by ctypes) here rather than cffi.
> >
> 
> Oh dear. I think you're right. :-(
> 
> Forget I said anything. Naming is hard.
> 
> I'm still not sure how realistic it is to try and deprecate the C API.

I don't think it should be *deprecated*, but I agree the documentation
should point out the (probably better) alternatives.

From time to time, in the #python IRC channel there are people who
want to use C libraries with Python and try doing so with the C API
because they aren't aware of the alternatives.

Florian

-- 
http://www.the-compiler.org | me at the-compiler.org (Mail/XMPP)
   GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
         I love long mails! | http://email.is-not-s.ms/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/python-ideas/attachments/20150506/6264037f/attachment.sig>