[Stackless] Welcome to the Stackless Python List
thomas at xs4all.net
Sun Oct 8 20:13:43 CEST 2000
On Sun, Oct 08, 2000 at 07:12:33PM +0300, Christian Tismer wrote:
> If I understand you, then you would like to get the current
> Stackless version ported to 2.0, just as it is? Preparing
> a new version which should be merged into Python 2.1 is
> probably a different, more difficult task, since I don't think
> the current version should be the final word.
I don't really care which version should be 'ported' to 2.0. Actually, I do
a bit: the newest version would be best, I think ;) But I'm not sure what
the difference between 1.1 and 1.2 is.
> Would it make sense to use diffs back to original Python 1.5.2?
Not really. I do not have any experience with 1.5.2, except for the
occasional bughunt in modules.
> Oh well, probably it is better to just isolate what exactly
> my changes are, right?
> Should I prepare such a diff, assign "classes" to the changes,
> and then write up a documentation that explains why these
> classes of changes were made and how they work?
Well, I think that would give me at least a clear idea as to how Stackless
works. My main problem is that, though I understand the split of eval_code2
into a _setup and _loop functions, I still don't understand which parts of
standard Python are 'stackful' and should be fixed. Reading the code for one
way of dealing with those 'stackful' parts is not the best way to find out
what parts they are ;)
Alternatively, depending on the age of the CVS tree on which SLP 1.2 is
based, I could incorporate the ceval changes (and the rest, probably) by
hand... If you still have CVS tag/revisions for the files in question that
would be even simpler, I think. Did you ever try doing something like 'cvs
update' on your SLP tree, by the way ?
Thomas Wouters <thomas at xs4all.net>
Hi! I'm a .signature virus! copy me into your .signature file to help me spread!
Stackless mailing list
Stackless at starship.python.net
More information about the Stackless