Seem to be having trouble with Python/Bethon.

[Donn Cave]

Quoth Zoo Keeper <candiazoo at comcast.net>:
...
| Neither did I mean to imply that I was not sure if I wanted to use
| Python/Bethon.  I love Python, and I love BeOS.  Bethon seems to be the way to
| go, altho' I need to learn Bethon.

As far as I know, there's no alternative.  Just wanted to point out
that some limitations and impediments come with this path, compared
to C++.

On the other hand, Python may actually solve one problem that some
people claim is serious defect of BeOS.  When Be was alive, the
pervasively multithreaded architecture was supposed to be a big
advantage, but after they crashed, even Be engineers came out of
the woodwork to claim that the concurrency issues posed too difficult
of a problem for most developers and were thus responsible for a lot
of unreliable software.

I loved the thread-per-window architecture myself and never noticed
any problem, and at first I figured that might have been because
I fastidiously follow a queuing, event I/O model for thread interop
in my own application.  But Python itself takes some of the teeth
out of concurrency problems, because the interpreter doesn't run
in parallel.  So while your program executes in parallel, your code
doesn't - only the library functions are parallel.

	Donn Cave, donn at drizzle.com