ANN: Stackless Python 0.3

[Michael Hudson]

On Tue, 13 Jul 1999, Christian Tismer wrote:

> 
> 
> Michael Hudson wrote:
> 
> > Very nice, but
> 
> > >>> apply(l.sort,())
> > Traceback (innermost last):
> >   File "<stdin>", line 1, in ?
> > SystemError: error return without exception set
> > >>> l
> > [0, 1, 2, 3, 4, 5, 6, 7, 8, 9]
> 
> Here is the patch.
> It was one of those "=" instead of "==" bugs.
> 
> Line 131 of bltinmodule.c should read now
> 
> 	if (retval == Py_UnwindToken) {
> 	-----------!!------------------
> 
> I'm updating the files right now, without changing the version number.
> 
> Thanks, Michael!
> 
> 

More problems, I'm afraid.

It would seem to be impossible for a script executed from the commandline
(ie, like

stackless-python foo.py

) to exit with any exit status other than 1, except by reaching the end.

I'm sorry, I'm not explaining this very well. If a script tries to exit by
calling sys.exit, sys._exit or raising SystemExit the exit status is
always 1. os._exit works as advertised, I've just noticed.

They all work when interactive too.

Another, maybe connected phenomenon is that

echo "fudge" | stackless-python

does *not* print an error!

echo "fudge" | stackless-python -i

does!

As you can see I have built stackless python into an executable called
stackless-python. This required extensive hackery of the build process, so
that could be at fault. This makes even less sense to me.

A consequence of all this is that stackless-python cannot install itself
without error on my system (compileall.py "fails").

Ideas?

TIA
Michael

PS: Did you see stackless python got a mention on Linux Weekly News Today?
Cool.

-- 
Oh, very funny. Very sar-cah-stic.         http://www.ntk.net
http://www.ntk.net/doh/options.html - ho ho