Message transféré --------
> Sujet : Re: Progress migrating cffi and pycparser to libclang
> Date : Thu, 4 Jan 2018 21:25:27 +
> De : Paul Moore
> Pour : Etienne Robillard
> Copie à : Python
>
> On 4 January 2018 at 21:02, Etienne Robillard
> wrote:
> &g
Hi Etienne,
On 5 January 2018 at 10:15, Etienne Robillard wrote:
> Forwarding this thread to the CFFI developers...
>
If you're asking whether we could add libclang as a dependency to CFFI, the
answer is no, sorry.
I feel that I've already explained exactly this to you several times in
private
Forwarding this thread to the CFFI developers...
Re Paul: Thanks for your feedback.
My intended audience are developers who can use hg to fetch/build source
code without pip.
Best regards,
Etienne
Message transféré
Sujet : Re: Progress migrating cffi and
On 4 January 2018 at 21:02, Etienne Robillard wrote:
>> As a fork/extension for cffi, I have no particular opinion (I'm
>> unlikely to ever use it). But the advantage of pycparser is that it's
>> cross-platform and pure Python, so I doubt this will be acceptable for
>> inclusion into CFFI itself.
Hi Paul,
Le 2018-01-04 à 06:41, Paul Moore a écrit :
Presumably that will introduce a dependency on some clang module? You
mention clang.cindex - but the only clang package I can find on PyPI
says "OBSOLETE. LLVM-CLANG NOW PUBLISHES PYTHON PACKAGE.
JUST ADD THE OFFICIAL llvm-3.7 repo in your ap
On 4 January 2018 at 09:50, Etienne Robillard wrote:
> Hi,
>
> I will be creating a repository for this:
> https://bitbucket.org/tkadm30/cffi-libclang
>
> The goal is to generate a AST object from a C header by preprocessing with
> clang -E then compile the python bindings with CFFI...
>
> ffi.cde
