> -----Original Message-----
> From: Victor Stinner <vstin...@python.org>
> Sent: Thursday, October 17, 2019 10:06 AM
> To: Kacvinsky, Tom <tom.kacvin...@vector.com>
> Cc: python-dev@python.org
> Subject: Re: [Python-Dev] PEP for libffi + _ctypes
>
> Hi,
>
> Our bundled copy of libffi has been removed from Python 3.7 by this change
> which should explain the rationale:
> https://bugs.python.org/issue27979
Thanks.
>
> Not all Python changes need a PEP. For Windows builds, we provide prebuilt
> binaries of our dependencies:
> https://github.com/python/cpython-source-deps/blob/master/README.rst
>
I am OK with Windows, it is Linux, as below.
> My notes on Python dependencies:
> https://pythondev.readthedocs.io/files.html
>
Again, thanks for this.
>
> > we support older Linux distributions that don't have libffi
>
> I'm curious, which old Linux distributions don't have libffi? Usually, libffi
> is
> preinstalled on Linux, only the development header files are required (a
> package with a name like "libffi-devel"). Can't you install libffi on these
> old
> distributions? IMHO libffi installation should not be the Python problem,
> bundling a library copy in Python is causing more issues compared to
> advantages.
RHEL/CentOS 5 come to mind. We don't want to get into the use case where
we have to have customers install libffi as we try to minimize the hassles our
customers might have to go through for installing and using our product.
Tom
_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://mail.python.org/archives/list/python-dev@python.org/message/A34TOQS5XBMWO5Q7AOPXDFEI3DDXAUBP/
Code of Conduct: http://python.org/psf/codeofconduct/
