Hi there Andreas.
What kind of socket solution are you using? I.e. I'm assuming that you are
using "tasklet blocking" to juggle IO over sockets. What modules are you
using?
On Linux, that ultimatyly is achieved by using select()/poll() system
calls. It is possible that something changed on the
The stackless run queue is implicit and whenever a tasklet blocks (i.e.
when doing channel operations and sender/receiver isn't available), a
runnable tasklet from the run queue is fetched and switched to.
stackless.run() is a tool to suspend the current tasklet while there are
runnable tasklets
In all cases it is useful to have some sort of tasklet manager that helps
keep track of tasklets.
This can be as simple as a set of weakrefs to tasklets that you create, or
something more complex, like a tasklet manager that creates tasklets for
you and assigns them to different sessions, or
project (
https://github.com/python-greenlet) originally a spinout of Stackless,
has improved platform switching code (in terms of number of platforms and
ease of building).
On Apr 2, 2015, at 6:16 AM, Kristján Valur Jónsson swesk...@gmail.com
wrote:
Interesting. The last time I looked, (some 18
Ah,
When I left CCP I got permission to take StacklessIO and make it open
source. In my last months there, I had been working on a Mac OSX version
of it.
This would port very easily to linux, with some minor work (mac OSX has a
built in thread pool library that linux doesn´t, and threads are
Is this on a unix-like thingie?
IIRC, it is ./configure --with-pydebug
before running the makefile. Exactly the same as for regular python
builds. Look into building CPython for your platform for details.
Errors during PyFinalize usually have to do with two things:
Problems in objects being
Yes, all manner of bad things will happen.
The entire run-time machinery of CPython is protected by the GIL.
The most obvious one is the reference count of objects. Even if not sharing
state you are still sharing common objects such as modules, etc.
Then there is all sorts of internal caching of
documentation or examples on
stacklesslib? ;)
I was fiddling with it the other day and couldn't find any good enough examples
of stacklesslib usage..
Cheers,
alex
On Tue, May 20, 2014 at 12:13 PM, Kristján Valur Jónsson
krist...@ccpgames.commailto:krist...@ccpgames.com wrote:
You may want to take
To: The Stackless Python Mailing List
Subject: Re: [Stackless] goless
On 18.04.14 12:46, Kristján Valur Jónsson wrote:
Hi, I though’t I’d mention here an experimental problem that a few of my
colleagues worked on during PyCon:
Goless!
http://goless.readthedocs.org/en/latest/index.html
It also shows
Hi, I though't I'd mention here an experimental problem that a few of my
colleagues worked on during PyCon:
Goless!
http://goless.readthedocs.org/en/latest/index.html
It also shows how more complex behavior can be built on top of the relatively
simple primitives that stackless provides.
K
Hi there.
At PyCon I was approached by a core developer of CPython who asked me this:
If we had a hypothetical GIL-less CPython, would stackless (tasklets or
co-routines) still be a useful constructs or would real threads be sufficient?
The question is serious and it is possible that a
Hi there.
I've created a WorkFlowy page as a place to think about stackless sprinting at
PyCon.
https://workflowy.com/shared/ae973dae-d19c-c14e-1aff-2985a5ec5dff/
Please feel free to edit the page, adding suggestions and so on. Tag your
edits with your @name for easy reference.
K
Hi.
I'll give this a go tomorrow. Hopefully it is a simple fix.
I have found that the clang compiler does warn a lot :)
K
-Original Message-
From: stackless-boun...@stackless.com [mailto:stackless-boun...@stackless.com]
On Behalf Of Hervé Coatanhay
Sent: 2. apríl 2014 14:20
To: The
Interestingly, I have a mac with latest Xcode sitting on my desk.
But I've actually been having trouble getting our 2.7 to build on it, having to
hardcode SDK paths and other such stuff.
Perhaps we don't properly support the MacOSX10.9.sdk
K
-Original Message-
From:
for me to
handle this.
I believe the fact that f_back == None is also used as a marker of
this frame came fron unpickling.
Without a need to improve this, I would like to keep it this way.
cheers - Chris
On 06/03/14 10:01, Kristján Valur Jónsson wrote:
I'm not sure I
with the way we are pickling? Or is it
related to how unpickling happens?
Cheers,
Richard.
On 3/5/14, Kristján Valur Jónsson krist...@ccpgames.com wrote:
ok, I have fixed it and pushed a new version.
I don't quite understand, why are unpickled frames marked with None in
their f_back? Does
Valur Jónsson krist...@ccpgames.com wrote:
ok, I have fixed it and pushed a new version.
I don't quite understand, why are unpickled frames marked with None in
their f_back? Does that mean that we never pickle frame stacks, but
only single frames?
I looked for other cases where we test
Strike that, seems to be there already.
-Original Message-
From: stackless-boun...@stackless.com [mailto:stackless-
boun...@stackless.com] On Behalf Of Kristján Valur Jónsson
Sent: 5. mars 2014 08:51
To: The Stackless Python Mailing List
Subject: Re: [Stackless] 3.2.5 unittest
ok, I have fixed it and pushed a new version.
I don't quite understand, why are unpickled frames marked with None in their
f_back? Does that mean that we never pickle frame stacks, but only single
frames?
I looked for other cases where we test for this None but didn't find it...
K
to have 3.2.2 and 3.1.3 on the Stackless site for download.
Should I do releases for 3.1.5 and 3.2.5? Or should we remove one or both of
them from the site as irrelevant?
Cheers,
Richard.
On 3/2/14, Kristján Valur Jónsson krist...@ccpgames.com wrote:
Nope. 3.4-slp is still unknown.
K
Hm, possible. I will check.
K
-Original Message-
From: stackless-boun...@stackless.com [mailto:stackless-
boun...@stackless.com] On Behalf Of Richard Tew
Sent: 3. mars 2014 07:32
To: stackless@stackless.com
Subject: [Stackless] 3.2.5 unittest failure
Kristjan, is it possible you
Anyone notice a rather long delay on thus list?
Sent at 21:19 gmt Tuesday.
Sent from the æther.
___
Stackless mailing list
Stackless@stackless.com
http://www.stackless.com/mailman/listinfo/stackless
/14, Kristján Valur Jónsson krist...@ccpgames.com wrote:
I've integrated all changes to the 3.x branches now.
What is the state of 3.4-slp?
Does it exist somewhere? Or do we have to recreate it by merging
from 3.3-slp?
K
___
Stackless mailing list
way. Does my pulling remove these changes from my local repo, or are
these changes a part of my local repo which can only be discarded by doing a
fresh clone, and will be pushed as part of a push otherwise?
On 2/28/14, Kristján Valur Jónsson krist...@ccpgames.com wrote:
Not sure I understand your
no custom changes, but orginated from before the new
line fixes. I've since pulled the latest from the repo, is this enough to
make
my clone safe to push back?
Cheers,
Richard.
On 2/24/14, Kristján Valur Jónsson krist...@ccpgames.com wrote:
I am relatively sure that all stackless
Apparently PyCon 2014 just sold out.
But for those that are going, I was thinking if there would be interest in
sprinting some on Stackless?
I'll aim to stay for two whole days of sprinting myself, as I have been doing
in the past.
So, if there is interest, we might think about what to sprint
So, with the latest burst of activity, I wonder if it is time to redo the
release?
We have restored binary compatibility with Cpython and so pyside and qt should
now work.
K
___
Stackless mailing list
Stackless@stackless.com
: [Stackless] new releases?
Sure. How should we version number it? 2.7.6slp2?
Also, is there an easy way to work out what needs to be done to get
3.x up to date?
Richard.
On Tue, Feb 18, 2014 at 12:29 AM, Kristján Valur Jónsson
krist...@ccpgames.com wrote:
So, with the latest burst of activity, I
Hello there.
I have a question regartding stackless.run()
This function has an ignore_nesting boolean keyword. Individual tasklets
also have a ignore_nesting flag. The keyword arg implies ignore_nesting as
being true for all tasklets.
My question is this:
What is the use case for this?
If
/6/14, Kristján Valur Jónsson krist...@ccpgames.com wrote:
I've updated the code.
Flags are now set only when required, not on all types wholesale.
It is possible to disable this with a new macro,
STACKLESS_NO_TYPEINFO See how this affects your crash scenario
(still runs all
I had to be familiar with that part of the code.
Should your changes have resulted in something that crashes harder and
faster (and more consistently) than the old heap type version?
Cheers,
Richard.
On 2/6/14, Kristján Valur Jónsson krist...@ccpgames.com wrote:
I think that the problem
in the expected places when checking for type flags.
K
-Original Message-
From: stackless-boun...@stackless.com [mailto:stackless-
boun...@stackless.com] On Behalf Of Kristján Valur Jónsson
Sent: 6. febrúar 2014 09:28
To: The Stackless Python Mailing List
Subject: Re: [Stackless
Hi there.
We must be careful not to let 3.2 (and 3.3) become out of sync.
I've just grafted my last changes from 2.7 to 3.2 and merged to 3.3
Anselm has done a bunch of changes in the last month or so that haven't made it
to 3.2.
It's bad to have a backlog of such changes and we really should try
.
It is indeed a pity we can't say we're compatible with all Python extensions,
and it would be good to get it fixed.
Cheers,
Richard.
On 2/4/14, Kristján Valur Jónsson krist...@ccpgames.com wrote:
This is so annoying. Time for another stab at this problem, perhaps?
-Original Message
.
The crashes have become less though since maybe a year ago; maybe some
improvements on the PySide?
I am using stackless python 2.7.5.
CL
On Wed, Feb 5, 2014 at 9:55 AM, Kristján Valur Jónsson
krist...@ccpgames.commailto:krist...@ccpgames.com wrote:
At one point I had a patch going
indicates a bug in
python.exe or any of the DLLs it has loaded.
This may also be due to the user pressing F12 while python.exe has focus.
The output window may have more diagnostic information.
Cheers,
Richard.
On 2/6/14, Kristján Valur Jónsson krist...@ccpgames.com wrote:
Ok, I have a proposed
my code relies on
stackless and PySide.
The crashes have become less though since maybe a year ago; maybe some
improvements on the PySide?
I am using stackless python 2.7.5.
CL
On Wed, Feb 5, 2014 at 9:55 AM, Kristján Valur Jónsson
krist...@ccpgames.commailto:krist...@ccpgames.com wrote
?
As far as I know, the mainline python installer is build without PGO.
Our installer is build with PGO optimisation.
Another question: can you try our 2.7.5 build? It is PGO optimized too.
Cheers
Anselm
Am 03.02.2014 12:13, schrieb Kristján Valur Jónsson:
Hi.
Do you get
We should make a talk submission.
I’m sure that the changes related to threads are interesting.
I’m not certain that I can attend, but if I were to have a talk there, the
chances would improve :)
K
-Original Message-
From: stackless-boun...@stackless.com [mailto:stackless-
-Original Message-
From: stackless-boun...@stackless.com [mailto:stackless-
boun...@stackless.com] On Behalf Of Christian Tismer
Sent: 7. janúar 2014 15:49
To: The Stackless Python Mailing List
Subject: Re: [Stackless] __future__ policy
Hey Kristjan,
you should better post
-Original Message-
From: stackless-boun...@stackless.com [mailto:stackless-
boun...@stackless.com] On Behalf Of Martijn Faassen
Sent: 8. janúar 2014 12:48
To: stackless@stackless.com
Subject: Re: [Stackless] __future__ policy
On 01/08/2014 12:36 PM, Christian Tismer wrote:
I don't mind having it around. I'm just wondering if it is worth the bother of
keeping it up-to-date.
Currently stackless development is don thus:
1) Submit commit to 2.7
2) graft to 3.2
3) merge to 3.3
If we stop supporting 3.2 this will currently change to:
1) submit to 2.7
2) graft to 3.3
Don't forget VS2010 compatibility. That too is a big ticket. Python sadly has
to have one windows compiler version per version, it doesn't support both.
People that want to use python 2.x in modern projects are out of luck.
The vision I have for 2.8 is the following:
1) allow future changes
Nick mentions stackless 2.8 in his updated 3.3 document:
http://python-notes.curiousefficiency.org/en/latest/python3/questions_and_answers.html
-Original Message-
From: stackless-boun...@stackless.com [mailto:stackless-
boun...@stackless.com] On Behalf Of Kristján Valur Jónsson
Sent
try:
from __future__ import nonlocal
except SyntaxError:
pass # aha, we're probably running version 3 already!
K
-Original Message-
From: stackless-boun...@stackless.com [mailto:stackless-
boun...@stackless.com] On Behalf Of Martijn Faassen
Sent: 7. janúar 2014 12:44
To:
Should we close off the 3.2-slp branch?
It looks like a very dead horse, even though merging from 3.2-slp to 3.3-slp is
the single most effortless part of stackless branch management :)
I would also suggest that we create a default-slp branch, to mirror the
current default. Essentially, rename
Valur Jónsson wrote:
Should we close off the 3.2-slp branch?
It looks like a very dead horse, even though merging from 3.2-slp to
3.3-slp is the single most effortless part of stackless branch
management :)
No objection to close that after merging.
Unlike the 2.X series, 3.X seems to have
Hi, I just wanted to discuss our practices on BitBucket.
While the repo is still private, we who have access should probably stick to
some guidelines.
1) Commit comments should include ticket references, so that we get proper
cross-references:
that it should just merge fine.
From: Christian Tismer [mailto:tis...@stackless.com]
Sent: 6. janúar 2014 13:42
To: The Stackless Python Mailing List; Kristján Valur Jónsson
Subject: Re: [Stackless] bitbucket processes
On 06.01.14 13:32, Kristján Valur Jónsson wrote:
Hi, I just wanted to discuss our
You can ignore most of the errors in the test-timeout test, if it is only about
miniscule differences in wakeup time.
It is attempting to verify the precision of a timeout, while in reality,
particularonly on certain platforms, the app may wake up late.
K
From: stackless-boun...@stackless.com
-December/006031.html
Was your reply to the earlier thread, I believe.
Cheers,
Richard.
On 1/3/14, Kristján Valur Jónsson krist...@ccpgames.com wrote:
-Original Message-
From: stackless-boun...@stackless.com [mailto:stackless-
boun...@stackless.com] On Behalf Of Richard
threading._Event is the actual event class.
threading.Event is a factory function. I think the intention of the library
designers was to use factory functions rather than classes directly to have the
freedom to change implementation later.
Why Django is doing it this way, I don't know, but for
.
On Fri, Jan 3, 2014 at 3:56 AM, Kristján Valur Jónsson
krist...@ccpgames.com wrote:
You can ignore most of the errors in the test-timeout test, if it is
only about miniscule differences in wakeup time.
It is attempting to verify the precision of a timeout, while in reality,
particularonly
Not sure, interprocess has so different semantics (objects are not shared but
recreated) that it might be confusing to layer that on top of existing channels.
K
-Original Message-
From: stackless-boun...@stackless.com [mailto:stackless-
boun...@stackless.com] On Behalf Of Richard Tew
-Original Message-
From: stackless-boun...@stackless.com [mailto:stackless-
boun...@stackless.com] On Behalf Of Richard Tew
Sent: 1. janúar 2014 18:45
To: The Stackless Python Mailing List
Subject: Re: [Stackless] HELLO! stackless
2.7.6 is working and passing all unit tests,
Sounds exciting.
I wonder how much of the STM work can be salvaged and made to work for us?
Are you thinking about “automatic parallelism” like Armin Rigo has been
thinking of, or just explicit tasklets that can, by nature of just using
non-shared objects, can operate gil-less?
non-shared is
Alex Gaynor just blogged about the failed state of 3.x and the need to give in
and produce a better 2.x
http://alexgaynor.net/2013/dec/30/about-python-3/
___
Stackless mailing list
Stackless@stackless.com
-boun...@stackless.com]
On Behalf Of Jeff Senn
Sent: 19. desember 2013 19:51
To: The Stackless Python Mailing List
Subject: Re: [Stackless] stackless-for-android
Kristján-
Did you ever make any progress on the Kivy port?
On Nov 22, 2013, at 9:38 AM, Kristján Valur Jónsson krist...@ccpgames.com
,
I'm really sorry, I can't come to Berlin. It's December and that's the busiest
month of the year.
Cheers
Anselm
Am 09.12.2013 21:29, schrieb Christian Tismer:
On 09/12/13 21:08, Kristján Valur Jónsson wrote:
Ok I will let you know.
Actually I arrive on Thursday. Can you send me
: [Stackless] Issue #31: add easy_install to the 2.8 stdlib
(stackless-dev/stackless)
On 04.12.13 19:11, Tim Delaney wrote:
On 4 December 2013 23:25, Kristján Valur Jónsson
issues-re...@bitbucket.orgmailto:issues-re...@bitbucket.org wrote:
New issue 31: add easy_install to the 2.8 stdlib
https
New issue 30: create a build environment for 2.8 so that we can distribute
complete installs for windows.
https://bitbucket.org/stackless-dev/stackless/issue/30/create-a-build-environment-for-28-so-that
Kristján Valur Jónsson:
It would be nice to be able to point to an installable stackless
New issue 31: add easy_install to the 2.8 stdlib
https://bitbucket.org/stackless-dev/stackless/issue/31/add-easy_install-to-the-28-stdlib
Kristján Valur Jónsson:
One of the most annoying parts of any stackless installation is to have to
manually go and fetch an easy_install thing, which
New issue 32: Fix Doc/library/Stackless .rst documentation for new features
https://bitbucket.org/stackless-dev/stackless/issue/32/fix-doc-library-stackless-rst
Kristján Valur Jónsson:
A bunch of new features has been added.
tasklet.throw
tasklet.bind_thread()
tasklet.switch()
stackless.atomic
, 2013 at 12:36 AM, Kristján Valur Jónsson
krist...@ccpgames.commailto:krist...@ccpgames.com wrote:
A bug!
in threadpool.py, replace the final line with:
return tasklet_call(wrapped, dispatcher=dispatcher, timeout=timeout,
onOrphaned=onOrphaned)
Needs more unittests :)
K
stackless.schedule_remove() in that the
former specifies the target
tasklet to which we switch.
K
-Original Message-
From: Anselm Kruis [mailto:a.kr...@science-computing.de]
Sent: 2. desember 2013 15:36
To: stackless@stackless.com; Kristján Valur Jónsson
Subject: stackless run_remove()
Hi
Apart from the bug you found (and crafted by me), your example illustrates some
of the shortcomings of monkeypatching.
The framework you are working with is clearly using socket.select() to do
timeouts when listening to connections. This is fairly common in Python
(socketserver.py does this)
A bug!
in threadpool.py, replace the final line with:
return tasklet_call(wrapped, dispatcher=dispatcher, timeout=timeout,
onOrphaned=onOrphaned)
Needs more unittests :)
K
From: stackless-boun...@stackless.com [stackless-boun...@stackless.com] on
behalf
Good heavens!
I have all but stopped submitting patches because you end up
having to fight all the usual fights with all the usual crew.
Often these are constructive criticisms but often they are just
knee-jerk responses and turf-wars.
Personally I don't enjoy those and most often it gets me so
-Original Message-
From: stackless-boun...@stackless.com [mailto:stackless-
boun...@stackless.com] On Behalf Of Christian Tismer
Sent: 28. nóvember 2013 22:27
To: stackless@stackless.com
Subject: [Stackless] Fwd: Re: [Python-Dev] PEP process entry point and ill
fated initiatives
No, I think that if we are moving to Bitbucket, even if it is only as an
experiment, we should give their defect tracking a go.
Now, what about the wiki? Bitbucket has a wiki too, I'd suggest it as a place
to discuss things, such as what features to backport, etc
-Original
Sure, we ought to update the readme.
What Is more, we should give it the .md suffix to mark it as MarkDown
I'll commit some changes to the 27-slp branch today to document my recent
additions.
K
-Original Message-
From: stackless-boun...@stackless.com [mailto:stackless-
Hello there.
I have only a few comments,:
-Original Message-
From: stackless-boun...@stackless.com [mailto:stackless-
boun...@stackless.com] On Behalf Of Christian Tismer
Sent: 24. nóvember 2013 02:49
To: stackless@stackless.com
Subject: [Stackless] Stackless 2.8 layout (or
-Original Message-
From: Richard Tew [mailto:richard.m@gmail.com]
Sent: 21. nóvember 2013 21:09
To: Christian Tismer
Cc: stackless@stackless.com; Anselm Kruis; Kristján Valur Jónsson
Subject: Re: PEP 0404 and VS 2010 (python-dev)
Let's move forward with this. You're never
-
From: Christian Tismer [mailto:tis...@stackless.com]
Sent: 22. nóvember 2013 00:36
To: The Stackless Python Mailing List
Cc: Anselm Kruis; Kristján Valur Jónsson
Subject: Re: [Stackless] PEP 0404 and VS 2010 (python-dev)
- create a CPython executable, with a different DLL name,
- create
So, I've been toying with kivy (kivy.org) and it is cool.
It would be even cooler if we could make it run stackless for some of the
platforms.
the python-for-android project which was designed to host kivy on android
(https://github.com/kivy/python-for-android)
is currently using python 2.7.2.
chime in.
K
-Original Message-
From: Christian Tismer [mailto:tis...@stackless.com]
Sent: 21. nóvember 2013 08:18
To: stackless@stackless.com
Cc: Anselm Kruis; Kristján Valur Jónsson; Richard Tew
Subject: PEP 0404 and VS 2010 (python-dev)
Hi friends,
I made the attempt to get
It does, inasmuch that the implicit insert that exists on many methods is
indeed annoying.
But it is not really a problem, because:
def set_args(t, args=(), kw={}):
with stackless.atomic():
t.setup(*args, **kw):
t.remove()
A more annoying problem that isn't solvable, and that is
And it is done. I also merged the release versions of 3.2.5 and 3.3.2 into
their respective branches.
Stackless now represents the pinnacle of python development :)
K
From: stackless-boun...@stackless.com [mailto:stackless-boun...@stackless.com]
On Behalf Of Kristján Valur Jónsson
Sent: 13
Python 2.7.6 is upon us.
I'll merge it in presently.
K
___
Stackless mailing list
Stackless@stackless.com
http://www.stackless.com/mailman/listinfo/stackless
p.s. did you notice http://www.stackless.com/ticket/26?
No. I don't get emails from this thing, maybe it is a config issue?
But I saw it myself and I fixed it in
15589a9eff2b0ee93460b8e8c4f0cf0f459c0fcf
(http://hg.python.org/stackless/rev/15589a9eff2b)
Ok, I see it isn't fixed. I'll
I'm working on this stuff, but I noticed another thread bug:
-Original Message-
From: stackless-boun...@stackless.com [mailto:stackless-
boun...@stackless.com] On Behalf Of Anselm Kruis
Sent: 11. nóvember 2013 19:23
To: stackless@stackless.com
Subject: Re: [Stackless] How to
Okay, I have pushed new changes.
bind_thread() now requires the target to be non-runnable.
In the process, I fixed a number of issues:
tasklet.remove() didn't work correctly for a tasklet from a different thread.
new tasklets (that hadn't run yet) were not killed when their thread went away.
I
: Re: [Stackless] How to transfer a tasklet to the current thread
Hi Kristján,
Am 08.11.2013 10:31, schrieb Kristján Valur Jónsson:
-Original Message-
data and decides, that the tasklet shall be run on a worker thread.
Problem: as far as I know, a tasklet bound to a thread
] merging changes
Hi,
Am 26.10.2013 12:51, schrieb Kristján Valur Jónsson:
As long as the features have unittests (stackless/unittests/...) then there
is
no special testing infrastructure needed.
That's perfectly valid as long as everything works as expected. But
sometimes things break
Well, if we just branch stackless 2.7 into 2.8 it is automatically added to
that... It would make sense to keep it in the same repo, or a clone, for easy
integration.
I don't know if there is a reason to host a separate clone repository, the
existence of /stackless at python.org is merely to
We could also implement native pickling for modules, rather than have to use
the reconstructor trick with __import__.
It is, after all, really a hack.
-Original Message-
From: stackless-boun...@stackless.com [mailto:stackless-
boun...@stackless.com] On Behalf Of Christian Tismer
-Original Message-
From: stackless-boun...@stackless.com [mailto:stackless-
boun...@stackless.com] On Behalf Of Christian Tismer
Sent: 28. október 2013 11:12
To: The Stackless Python Mailing List
Subject: Re: [Stackless] Fwd: [Stackless-checkins] stackless (2.7-slp): add a
filter
Subject: Re: [Stackless] Fwd: deepcopying (pickling) channels
On 10/25/13 11:44 AM, Kristján Valur Jónsson wrote:
Did anyone attempt to patch pickle.py as suggested below, to diagnose the
pickling problem?
Once you arrive at a problem, it is useful to know the chain of objects it is
working
of running the test suite.
K
-Original Message-
From: Anselm Kruis [mailto:a.kr...@science-computing.de]
Sent: 25. október 2013 19:09
To: Kristján Valur Jónsson
Cc: stackless@stackless.com
Subject: Re: [Stackless] merging changes
Hi Kristján,
here at s+c we still use Python 2.7 almost
Hello there.
I notice that there have been a number of changes to 2.7 in the last months by
other people than me.
Anselm and Christian mostly.
We should be careful to keep merging these changes to the 3.2 and 3.2 branches.
Merging from 2.7 to 3.2 is best done with the graft extension, I always
] On Behalf Of Kristján Valur Jónsson
Sent: 24. október 2013 14:52
To: The Stackless Python Mailing List
Subject: Re: [Stackless] Fwd: deepcopying (pickling) channels
How about this:
def save(self, obj):
try:
return self._save(obj)
except PickleError:
print pickling obj: %r
-Original Message-
From: stackless-boun...@stackless.com [mailto:stackless-
boun...@stackless.com] On Behalf Of John Ehresman
Sent: 23. október 2013 15:06
To: stackless@stackless.com
Subject: Re: [Stackless] Fwd: deepcopying (pickling) channels
It does look like the __init__
: Christian Tismer [mailto:tis...@stackless.com]
Sent: 13. október 2013 13:01
To: The Stackless Python Mailing List
Cc: Kristján Valur Jónsson
Subject: Re: [Stackless] stacklesslib.async
Hi Kristjan,
thanks for this pointer, very good article!
Maybe we should talk about futures, await and async.
Not sure
the extended pickler form the sPickle library. This pickler can
replace certain resource-objects (i.e. open files) by RPyC-Proxy objects on
the fly.
Cheers
Anselm
Am 05.09.2013 08:48, schrieb Kristján Valur Jónsson:
Hi,
I think this is a better spot to discuss this topic than
The error is weird. It seems to be trying to pickle the function type. It
shouldn't try doing that.
Now, I know that pickling channels with tasklets on them works. This is what
stackless does.
I tried saving your code into a module and just running it from the command
line.
I wonder if there
I've been adding small things and goodies to stacklesslib for the past few
quarters:
http://bitbucket.org/krisvale/stacklesslib
The latest addition is util.cancellable, which is a context manager that can be
used to create a cancellable context for a tasklet.
A tasklet can then call
-Original Message-
From: stackless-boun...@stackless.com [mailto:stackless-
boun...@stackless.com] On Behalf Of Richard Tew
Sent: 25. september 2013 08:26
To: The Stackless Python Mailing List
Subject: Re: [Stackless] stacklesslib.async
Other than that, there's a sense that you
Hi there.
So, progress. I have two pieces of news. First:
I took many of your comments into account, Richard and have a new version of
stackless.async in the repo:
http://bitbucket.org/krisvale/stacklesslib
First, I'd like to address your original points:
-Original Message-
From:
, whether returned or exception raised.
Does there have to be timeout functionality for these calls? I think
there does. How is that handled?
On Wed, Sep 4, 2013 at 1:25 AM, Kristján Valur Jónsson
krist...@ccpgames.commailto:krist...@ccpgames.com wrote:
Thanks for your feedback.
The original
. Perhaps backporting the concurrent.futures stuff to
2.7stackless makes sense .
K
From: stackless-boun...@stackless.com [mailto:stackless-boun...@stackless.com]
On Behalf Of Kristján Valur Jónsson
Sent: 9. september 2013 10:42
To: The Stackless Python Mailing List
Subject: Re: [Stackless
1 - 100 of 246 matches
Mail list logo
