2.6, 3.0, and truly independent intepreters

[Patrick Stinson]

Close, I work currently for EastWest :)

Well, I actually like almost everything else about CPython,
considering my audio work the only major problem I've had is with the
GIL. I like the purist community, and I like the code, since
integrating it on both platforms has been relatively clean, and
required *zero* support. Frankly, with the exception of some windows
deployment issues relating to static linking of libpython and some
extensions, it's been a dream lib to use.

Further, I really appreciate the discussions that happen in these
lists, and I think that this particular problem is a wonderful example
of a situation that requires tons of miscellaneous opinions and input
from all angles - especially at this stage. I think that this problem
has lots of standing discussion and lots of potential solutions and/or
workarounds, and it would be cool for someone to aggregate and
paraphrase that stuff into a page to assist those thinking about doing
some patching. That's probably something that the coder would do
themselves though.

On Fri, Oct 24, 2008 at 10:25 AM, Andy O'Meara <andy55 at gmail.com> wrote:
>>
>> So we are sitting this music platform with unimaginable possibilities
>> in the music world (of which python does not play a role), but those
>> little CPU spikes caused by the GIL at low latencies won't let us have
>> it. AFAIK, there is no music scripting language out there that would
>> come close, and yet we are sooooo close! This is a big deal.
>
>
> Perfectly said, Patrick.  It pains me to know how widespread python
> *could* be in commercial software!
>
> Also, good points about people being longwinded and that "code talks".
>
> Sadly, the time alone I've spend in the last couple days on this
> thread is scary, but I'm committed now, I guess.  :^(   I look at the
> length of the posts of some of these guys and I have to wonder what
> the heck they do for a living!
>
> As I mentioned, however, I'm close to just blowing the whistle on this
> crap and start making CPythonES (as I call it, in the spirit of the
> "ES" in "OpenGLES").  Like you, we just want the core features of
> python in a clean, tidy, *reliable* fashion--something that we can
> ship and not lose sleep (or support hours) over.  Basically, I imagine
> developing an interpreter designed for dev houses like yours and mine
> (you're Ableton or Propellerhead, right?)--a python version of lua, if
> you will.  The nice thing about it is that is could start fresh and
> small, but I have a feeling it would really catch on because every
> commercial dev house would choose it over CPython any day of the week
> and it would be completely disjoint form CPython.
>
> Andy
>