First steps for creating an API for portage
 

On Fri, Jun 18, 2010 at 10:08 AM, Brian Harring <ferringb@gmail.com> wrote:
>
> On Fri, Jun 18, 2010 at 12:55:37PM +0200, Rennn 'Necoro' Neumann wrote:
> > Am 18.06.2010 09:55, schrieb Brian Harring:
> > > While I'm not generally a fan of embedding python, in this case it's
> > > what makes sense. *That said I'm not hugely convinced the proposal on
> > > the table is accurate- knocking out a public portage API needs to
> > > occur, but a c-api is a very large and seperate beast from a public
> > > python API- namely due to crossing the vm, having to do FFI
> > > conversions, etc. *It's not the simplest thing.
> >
> > Well - there a tools like Cython which will take large parts of this
> > burden from your shoulder.
>
> Cython is for extending python, embedding python. *Cython doesn't do
> jack for embedding... frankly very little does.

Pardon, just to be clear I meant "Cython is for extending python, not
embedding python".

Need coffee...
~harring