Hi,
I've been following this thread and the specific issue of the strong
negative reaction to the name "Stackless Python 2.8", and I'm a bit
bothered by the whole experience.
Was there any concern about the name "Stackless Python 0.x" when
Christian released his original versions? More important
On 2/13/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Tristan is correct: this should be a patch against Twisted, or perhaps as a
> separate library that could implement a reactor.
I think there is some confusion here.
I am not writing a competing event driven mechanism. What I was doing
wa
On 2/13/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Steve Holden schrieb:
> > The only things that concern me are a) whether it could make sense to
> > add Stackless in bits and pieces and b) whether the BDFL (or even the
> > developer community en masse) would object in principle, thereby
>
On 2/12/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Armin Rigo schrieb:
> > The history as I remember it is that Christian tried hard to integrate
> > the first versions of Stackless with CPython, but was turned town by
> > python-dev.
>
> Are there public records of that? As I remember it,
On 2/12/07, Tristan Seligmann <[EMAIL PROTECTED]> wrote:
> * Richard Tew <[EMAIL PROTECTED]> [2007-02-12 13:46:43 +]:
> > Perhaps there is a better way. And I of course have no concept of
> > how this might be done on other platforms.
>
> Building on an existi
On 2/11/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Richard Tew schrieb:
> > If these generator coroutine microthreads went ahead and part
> > of it was improving the support for asynchronous calls in the
> > runtime and standard library, this w
On 2/11/07, "Martin v. Löwis" <[EMAIL PROTECTED]> wrote:
> Brett Cannon schrieb:
> >> Of course Stackless isn't quite fully integrated with 2.5 (yet).
> >>
> >> When did someone last suggest that Stackless become part of the core
> >> CPython implementation, and why didn't that ever happen?
> >>
>
Hi,During the sprint period after PyCon, we are planning on sprinting to bring Stackless up to date and to make it more current and approachable. A key part of this is porting it and the recently completed 64 bit changes that have been made to it to the latest version of Python. At the end of the
