[Stackless] Stackless 3.3

Kristján Valur Jónsson kristjan at ccpgames.com
Sat Jul 21 14:34:58 CEST 2012


Well, that was easy.

It turned out that the problem was a mere error.

I have fixed stuff and all appears to be well.



Please give the 3.3-slp beta a whirl.



K

________________________________
Frá: stackless-bounces at stackless.com [stackless-bounces at stackless.com] fyrir hönd Kristján Valur Jónsson [kristjan at ccpgames.com]
Sent: 21. júlí 2012 11:19
To: The Stackless Python Mailing List
Efni: Re: [Stackless] Stackless 3.3


Ok, I have continued further.  Compliance is now pretty good, but there is one bit failing:

Pep380 support, yield from, is not working correctly

test_pep380 is failing.

I'm not super surprised.



I have updated the repo with all my latest fixes, but this needs fixing too.  I will take a look but I'm not super super optimistic that it will be a breeze...  Even though it just might.



So, I invite you who are intimately familiar with stacklesseval.c and know how stackless does its iterator magic, to take a look.



K

________________________________
Frá: stackless-bounces at stackless.com [stackless-bounces at stackless.com] fyrir hönd Kristján Valur Jónsson [kristjan at ccpgames.com]
Sent: 20. júlí 2012 08:39
To: The Stackless Python Mailing List
Efni: Re: [Stackless] Stackless 3.3


Ok, I've finally gotten around to do this.

In http://hg.python.org/stackless there is now a new branch 3.3-slp.

This compiles and runs on windows and displays the command prompt.



Todo:

1) Make sure it runs all the unittests

2) Remove redundant pickling support, e.g. for list/dict iterators, that stackless added.



I also updated the other slp branches by merging in recent cpython changes.



K

________________________________
Frá: stackless-bounces at stackless.com [stackless-bounces at stackless.com] fyrir hönd Hervé Coatanhay [herve.coatanhay at gmail.com]
Sent: 26. júní 2012 10:50
To: The Stackless Python Mailing List
Efni: Re: [Stackless] Stackless 3.3

Yes pull cpython is the first step as stated in Richard email.

Anyway I think we should wait the creation of the "3.3" branch in cpython repo too. I suppose we want to apply stackless changes on 3.3 branch right ?

Hervé
On Tue, Jun 26, 2012 at 12:10 PM, Kristján Valur Jónsson <kristjan at ccpgames.com<mailto:kristjan at ccpgames.com>> wrote:
I haven’t started yet, actually :)
Probably a first step would be to “pull” the cpython repository, to get the full cpython version in, right?
K

From: stackless-bounces at stackless.com<mailto:stackless-bounces at stackless.com> [mailto:stackless-bounces at stackless.com<mailto:stackless-bounces at stackless.com>] On Behalf Of Hervé Coatanhay
Sent: 26. júní 2012 09:29
To: The Stackless Python Mailing List
Subject: Re: [Stackless] Stackless 3.3

Hi all.
Kristjan, I don't know if you are done with the merge. But as I gave a try to what said Richard,  I think a 3.3-slp branch should be created after update and before merge.

If naming is done as usual it gives:

hg up -C 3.2-slp
hg branch 3.3-slp
hg merge 3.3 (this would be 3.3 Maintenance branch from cpython)
--> fix conflicts
hg commit
hg tag "v3.3.0-slp"

Hervé
On Sun, Jun 24, 2012 at 6:36 AM, Richard Tew <richard.m.tew at gmail.com<mailto:richard.m.tew at gmail.com>> wrote:
On Sat, Jun 23, 2012 at 12:04 PM, Richard Tew <richard.m.tew at gmail.com<mailto:richard.m.tew at gmail.com>> wrote:
>> The time approaches when a stackless version 3.3 needs to be prepared.
>>
>> Now, what is the right and proper way to do it in this Hg day and age?
>>
>>
> No idea, even though I've done this!  I do recall that the documentation was
> ambiguous and unclear.  Please post the process when you work it out :-)
>
> I'll look to see if I made notes when I did this, but I am pretty certain I
> didn't.
>From my notes it looks like the following:

 hg pull [cpython repo url]

Choose the branch to be merged into and the branch to be merged from.

 hg up [branch to be merged into, may include "-r <revisionid>"]
 hg merge [branch to be merged from, may include "-r <revisionid>"]

Watch mercurial bring in all the changesets from the point of common history.

 hg commit.
 hg tag "v3.3.0-slp"

Be absolutely sure you did it right, and aren't going to push
unremovable changes.

 hg push [stackless repo url]

It should be that easy.  In my case, I got the "into" and "from"
branches backwards to begin with and the merge was messy.  After
reversing them, it was pretty straightforward.  That wasn't in my
notes, just a vague recollection.

Anyway, good luck,
Richard.

_______________________________________________
Stackless mailing list
Stackless at stackless.com<mailto:Stackless at stackless.com>
http://www.stackless.com/mailman/listinfo/stackless


_______________________________________________
Stackless mailing list
Stackless at stackless.com<mailto:Stackless at stackless.com>
http://www.stackless.com/mailman/listinfo/stackless

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.stackless.com/pipermail/stackless/attachments/20120721/32ad6c4f/attachment-0001.html>


More information about the Stackless mailing list