[pypy-dev] Builtin types

Samuele Pedroni pedronis at bluewin.ch
Mon Jan 27 20:03:40 CET 2003

----- Original Message -----
From: "holger krekel" <hpk at trillke.net>
To: "Armin Rigo" <arigo at tunes.org>; <pypy-dev at codespeak.net>
Sent: Monday, January 27, 2003 6:00 PM
Subject: Re: [pypy-dev] Builtin types

> [Armin Rigo Mon, Jan 27, 2003 at 01:18:00PM +0100]
> > Hello,
> >
> > On Fri, Jan 24, 2003 at 05:48:42PM +0100, Samuele Pedroni wrote:
> > > OTOH I think a higher level of abstraction is necessary to targert more
> > > backends.
> >
> > I agree with Samuele that we should not focus on ctypes or any other kind
> > structs right now.  For all of ctypes' power I believe that it is not
> > to Python-in-Python.  This will become important later, when we target C.
> how do you intend to use any of the existing C-libraries, then?
> Rely on CPython to provide the binding?
> I think that progressing in the ctypes direction can happen in
> parallel with Python-Core pythonifications.  Beeing able to make
> C-library calls (like File-IO) without specialized intermediate C-code
> does seem like an important feature.

The point was whether you want your builtin types "abstractions" to be directly
ctypes based.

Or reformulated as a question:

Is a goal to target some reasonable other virtual machines /languages/object
models  as  execution substrate?
(or do you want to limit yourself to implement some C/native code
reedition/evolution of CPython)

No is obviously a fine anwer.

OTOH I think it is important to answer better sooner than later, because if one
thinks that simply because this is (some) Python in Python the problem is
automatically solved, he is having the wrong intuition.


More information about the Pypy-dev mailing list