From: Jeff Sickel <jas@corpus-callosum.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Python cleverness
Date: Sat, 17 Mar 2007 14:07:28 -0500 [thread overview]
Message-ID: <0A23717C-0401-45EC-852A-D54113AD52FE@corpus-callosum.com> (raw)
In-Reply-To: <13426df10701171309w65f11042l413cbcad22e7993f@mail.gmail.com>
Has there been any progress on this? I'd really like to see Python
2.4* or 2.5 on Plan 9 since a lot of the Python code I deal with on a
regular basis these days requires a more recent version than we have
out there on Plan 9.
jas
On Jan 17, 2007, at 3:09 PM, ron minnich wrote:
>
> But, if I can get this, we should have dynamic modules in Python, and
> I get to check that box, since python and dynamic modules have become
> very important to supercomputer applications writers. There, I said
> that without grimacing :-)
next prev parent reply other threads:[~2007-03-17 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-17 21:09 ron minnich
2007-03-17 19:07 ` Jeff Sickel [this message]
2007-03-17 19:35 ` Federico Benavento
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=0A23717C-0401-45EC-852A-D54113AD52FE@corpus-callosum.com \
--to=jas@corpus-callosum.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).