Re: [Python-Dev] libffi inclusion in python

2013-04-19 Thread Ronald Oussoren
On 19 Apr, 2013, at 10:13, Dirkjan Ochtman wrote: > On Thu, Apr 18, 2013 at 11:17 PM, Ronald Oussoren > wrote: >> Stripping libffi from python's source tree would be fine by me, but would >> require testing with upstream libffi. AFAIK system libffi on osx wouldn't be >> goog enough, it doesn'

Re: [Python-Dev] libffi inclusion in python

2013-04-19 Thread Dirkjan Ochtman
On Thu, Apr 18, 2013 at 11:17 PM, Ronald Oussoren wrote: > Stripping libffi from python's source tree would be fine by me, but would > require testing with upstream libffi. AFAIK system libffi on osx wouldn't be > goog enough, it doesn't work properly with clang. If you mean http://bugs.python.

Re: [Python-Dev] libffi inclusion in python

2013-04-18 Thread Ronald Oussoren
On 18 apr. 2013, at 18:09, Ned Deily wrote: > In article > , > Benjamin Peterson wrote: >> 2013/4/18 Maciej Fijalkowski : >>> libffi has bugs sometimes (like this >>> http://bugs.python.org/issue17580). Now this is a thing that upstream >>> fixes really quickly, but tracking down issues on bugs

Re: [Python-Dev] libffi inclusion in python

2013-04-18 Thread Maciej Fijalkowski
On Thu, Apr 18, 2013 at 9:22 PM, Thomas Heller wrote: libffi has bugs sometimes (like this http://bugs.python.org/issue17580). Now this is a thing that upstream fixes really quickly, but tracking down issues on bugs.python.org is annoying (they never get commited as quickly as

Re: [Python-Dev] libffi inclusion in python

2013-04-18 Thread Thomas Heller
libffi has bugs sometimes (like this http://bugs.python.org/issue17580). Now this is a thing that upstream fixes really quickly, but tracking down issues on bugs.python.org is annoying (they never get commited as quickly as the upstream). is there a good reason why cpython has it's own copy of lib

Re: [Python-Dev] libffi inclusion in python

2013-04-18 Thread Maciej Fijalkowski
On Thu, Apr 18, 2013 at 2:47 PM, Benjamin Peterson wrote: > 2013/4/18 Maciej Fijalkowski : >> Hi >> >> libffi has bugs sometimes (like this >> http://bugs.python.org/issue17580). Now this is a thing that upstream >> fixes really quickly, but tracking down issues on bugs.python.org is >> annoying (

Re: [Python-Dev] libffi inclusion in python

2013-04-18 Thread Ned Deily
In article , Benjamin Peterson wrote: > 2013/4/18 Maciej Fijalkowski : > > libffi has bugs sometimes (like this > > http://bugs.python.org/issue17580). Now this is a thing that upstream > > fixes really quickly, but tracking down issues on bugs.python.org is > > annoying (they never get commited

Re: [Python-Dev] libffi inclusion in python

2013-04-18 Thread Benjamin Peterson
2013/4/18 Maciej Fijalkowski : > Hi > > libffi has bugs sometimes (like this > http://bugs.python.org/issue17580). Now this is a thing that upstream > fixes really quickly, but tracking down issues on bugs.python.org is > annoying (they never get commited as quickly as the upstream). is > there a g

Re: [Python-Dev] libffi inclusion in python

2013-04-18 Thread Stefan Behnel
Maciej Fijalkowski, 18.04.2013 13:41: > PyPy gets along relying on the system library Depends on what systems you want to support, I guess. Stefan ___ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Uns

[Python-Dev] libffi inclusion in python

2013-04-18 Thread Maciej Fijalkowski
Hi libffi has bugs sometimes (like this http://bugs.python.org/issue17580). Now this is a thing that upstream fixes really quickly, but tracking down issues on bugs.python.org is annoying (they never get commited as quickly as the upstream). is there a good reason why cpython has it's own copy of