A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2015-March/138751.html below:

[Python-Dev] libffi embedded in CPython

[Python-Dev] libffi embedded in CPython [Python-Dev] libffi embedded in CPythonAntoine Pitrou solipsis at pitrou.net
Wed Mar 11 23:28:18 CET 2015
On Wed, 11 Mar 2015 22:20:58 +0000
Brett Cannon <brett at python.org> wrote:
> 
> You're ignoring that it's not maintained,

According to which metric/criterion?

changeset:   94932:86c9ef950288
user:        Steve Dower <steve.dower at microsoft.com>
date:        Tue Mar 10 09:56:38 2015 -0700
summary:     Issue #23606: Disable ctypes.util.find_library("c") on
Windows so tests are skipped while we figure out how best to approach
the CRT change

changeset:   94756:7c6e3358221a
user:        Serhiy Storchaka <storchaka at gmail.com>
date:        Thu Feb 26 15:27:57 2015 +0200
summary:     Silenced minor GCC warnings.

changeset:   94653:a84ae2ccd220
user:        Serhiy Storchaka <storchaka at gmail.com>
date:        Mon Feb 16 20:52:17 2015 +0200
summary:     Issue #23450: Fixed possible integer overflows.

[etc.]

> Who knows what
> improvements, bugfixes, etc. exist upstream in libffi that we lack because
> no one wants to go through and figure it out.

Well, who knows? How about you enlighten us about that?
And why do you think cffi, which *also* requires libffi, would be
better served in that regard?

Regards

Antoine.


More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4