On Thu, Dec 18, 2014, at 15:36, Jim J. Jewett wrote:
>
>
> On Thu, Dec 18, 2014, at 14:13, Maciej Fijalkowski wrote:
> > ... http://bugs.python.org/issue23085 ...
> > is there any reason any more for libffi being included in CPython?
>
> [And why a fork, instead of just treating it as an exter
On Fri, Dec 19, 2014 at 12:24 PM, Terry Reedy wrote:
> PEP 3 is listed in PEP 0 under Abandoned, Withdrawn, and Rejected PEPs
> If this is proper, it does not make sense to update it.
> If this is not, the header should be updated.
Guido passed the request on to the pep-editors list, which I too
On 12/18/2014 4:19 PM, Chris Angelico wrote:
On Fri, Dec 19, 2014 at 5:39 AM, Guido van Rossum wrote:
-- Forwarded message --
From: Victor Stinner
Hi,
Yes, the link is dead. It looks like the following link contains the same
info:
https://docs.python.org/devguide/triaging.htm
Hi Facunda,
you should either write to webmas...@pycon.org, the
conference ML or me directly, since I'm managing these the
pycon.org subdomains.
> On Thu, Dec 18, 2014, at 10:59, Facundo Batista wrote:
>> Hi!
>>
>> Don't remember where to ask for changing the redirection of that
>> domain name. S
On Fri, Dec 19, 2014 at 5:39 AM, Guido van Rossum wrote:
>-- Forwarded message --
> From: Victor Stinner
>
> Hi,
>
> Yes, the link is dead. It looks like the following link contains the same
> info:
> https://docs.python.org/devguide/triaging.html
>
> Dead page:
> https://web.arch
done - http://bugs.python.org/issue23084
On 12/17/14 8:20 PM, Eric Snow wrote:
On Wed, Dec 17, 2014 at 7:52 PM, Matthieu Bec wrote:
Attached patch defines a new type struct_timespec for the time module. A new
capsule exports the type along with to/from converters - opening a bridge
for C, an
On Thu, Dec 18, 2014, at 14:13, Maciej Fijalkowski wrote:
> ... http://bugs.python.org/issue23085 ...
> is there any reason any more for libffi being included in CPython?
[And why a fork, instead of just treating it as an external dependency]
Benjamin Peterson responded:
> It has some sort of
On Thu, Dec 18, 2014, at 10:59, Facundo Batista wrote:
> Hi!
>
> Don't remember where to ask for changing the redirection of that
> domain name. Somebody knows?
Seems DNS for that is controlled by eGenix, so ccing mal.
(We should move pycon.org DNS to use the PSF's normal DNS
infrastructure.)
On Thu, Dec 18, 2014, at 14:50, Maciej Fijalkowski wrote:
> well, the problem is essentially that libffi gets patched (e.g. for
> ARM) and it does not make it's way to CPython quickly. This is
> unlikely to be a security issue (for a variety of reasons, including
> ctypes), but it's still an issu
On Thu, Dec 18, 2014, at 14:50, Maciej Fijalkowski wrote:
> well, the problem is essentially that libffi gets patched (e.g. for
> ARM) and it does not make it's way to CPython quickly. This is
> unlikely to be a security issue (for a variety of reasons, including
> ctypes), but it's still an issu
well, the problem is essentially that libffi gets patched (e.g. for
ARM) and it does not make it's way to CPython quickly. This is
unlikely to be a security issue (for a variety of reasons, including
ctypes), but it's still an issue I think. Segfaults related to e.g.
stack alignment are hard to deb
On Thu, Dec 18, 2014, at 14:13, Maciej Fijalkowski wrote:
> After reading this http://bugs.python.org/issue23085 and remembering
> struggling having our own patches into cpython's libffi (but not into
> libffi itself), I wonder, is there any reason any more for libffi
> being included in CPython?
On Thu, Dec 18, 2014 at 9:17 PM, Steve Dower wrote:
> Maciej Fijalkowski wrote:
>> After reading this http://bugs.python.org/issue23085 and remembering
>> struggling
>> having our own patches into cpython's libffi (but not into libffi itself), I
>> wonder, is there any reason any more for libffi
Maciej Fijalkowski wrote:
> After reading this http://bugs.python.org/issue23085 and remembering
> struggling
> having our own patches into cpython's libffi (but not into libffi itself), I
> wonder, is there any reason any more for libffi being included in CPython?
We use it for ctypes, so there'
After reading this http://bugs.python.org/issue23085 and remembering
struggling having our own patches into cpython's libffi (but not into
libffi itself), I wonder, is there any reason any more for libffi
being included in CPython?
Cheers,
fijal
___
Pyth
Hi!
Don't remember where to ask for changing the redirection of that
domain name. Somebody knows?
I need for the redirection to be to pycon.python.org.ar (and we'll
take care of proper year-by-year redirection from there).
Thanks!
--
.Facundo
Blog: http://www.taniquetil.com.ar/plog/
PyAr:
Hi,
Yes, the link is dead. It looks like the following link contains the same info:
https://docs.python.org/devguide/triaging.html
Dead page:
https://web.archive.org/web/20090704040931/http://www.python.org/dev/workflow/
"Core Development > Issue Workflow"
Victor
2014-12-18 6:57 GMT+01:00 Raymo
17 matches
Mail list logo
