9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: [9fans] python
Date: Thu,  6 Dec 2001 02:29:29 -0500	[thread overview]
Message-ID: <20011206072931.90885199E8@mail.cse.psu.edu> (raw)

g% 8.out
'import site' failed; use -v for traceback
Python 2.0.1 (#0, Dec  6 2001, 02:11:16) [C] on unknown
Type "copyright", "credits" or "license" for more information.
>>> from plan9 import *
>>> from plan9 import _exits		# underscore hides from *
>>> read(open("/dev/sysname", OREAD), 100)
'17genr'
>>> if rfork(RFPROC)==0:
... 	write(2, "child\n")
... 	_exits("")
... else:
... 	write(2, "parent\n")
...
child
parent
7
>>>

it's still rough, but i'm willing to put it into
lucio's cvs repository so people can hack
on getting it up to speed.  send me mail if you're
interested.

unlike the other os-specific modules, i think the plan9
one should include just the system calls and
then have the rest implemented as python code
rather than the fairly difficult c layering.

the eventual goal is to bring in the ``stackless
python'' patches, so we can have really cheap
continuations and build a csp-style threading
module that has neither stack overflow concerns
nor ridiculously large stacks.

russ



             reply	other threads:[~2001-12-06  7:29 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-06  7:29 Russ Cox [this message]
2001-12-06  7:17 ` Lucio De Re
2001-12-06 16:12 ` [9fans] My "plan9" stuff for Linux (last reference, I promise) Ronald G Minnich
2001-12-06 16:53   ` Boyd Roberts
2001-12-06 16:57   ` Matt
  -- strict thread matches above, loose matches on Subject: below --
2010-10-10 14:06 [9fans] Python Michaelian Ennis
2010-10-10 14:21 ` Federico G. Benavento
2010-10-11  1:30   ` Michaelian Ennis
2010-10-11  1:55     ` Steve Simon
2010-10-11 23:59       ` Michaelian Ennis
2007-01-04 22:31 [9fans] python ron minnich
2007-01-05  4:14 ` John Barham
2007-01-05  6:18   ` erik quanstrom
2007-01-05  7:03     ` Dave Lukes
2007-01-05  7:09       ` Bruce Ellis
2007-01-05  7:26       ` Skip Tavakkolian
2006-12-23 21:50 Bad-Santa
2006-12-23 23:54 ` ron minnich
2006-12-24  1:00   ` Russ Cox
2006-12-25  0:28     ` LiteStar numnums
2006-12-30  5:06       ` John Floren
2006-12-23  5:10 ron minnich
2006-12-23  5:27 ` Russ Cox
2006-12-23  5:31   ` ron minnich
2006-12-23  6:19     ` Russ Cox
2006-12-23  7:13       ` arisawa
2006-12-23 13:29   ` LiteStar numnums
2006-12-23 14:23     ` arisawa
2006-12-23 20:20       ` Russ Cox
2006-12-23 11:57 ` Matt
2003-11-03 16:11 matt
2003-11-03 15:20 ` Russ Cox
2002-03-11 18:51 Russ Cox
2002-03-18 13:21 ` Boyd Roberts
2002-02-08 13:51 Boyd Roberts
2001-12-02  9:39 Russ Cox
2001-12-02 12:08 ` Boyd Roberts
     [not found] ` <rsc@plan9.bell-labs.com>
2001-12-02 16:05   ` Jonathan Sergent
2001-12-03 22:24 ` Laura Creighton
2000-11-06  8:26 [9fans] Python Jonathan Sergent
1999-01-16  5:53 arisawa
1998-12-30  0:17 arisawa

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20011206072931.90885199E8@mail.cse.psu.edu \
    --to=rsc@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).