9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "John Barham" <jbarham@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] python
Date: Thu,  4 Jan 2007 20:14:59 -0800	[thread overview]
Message-ID: <4f34febc0701042014p7e13c951gc20bd80f44aa44b6@mail.gmail.com> (raw)
In-Reply-To: <13426df10701041431w2272898eu3b620dd2b33086ff@mail.gmail.com>

> One problem concerns extensions. PYthon loves .so files. Plan 9,
> obviously, does not.
>
> Lots of tools are structured in a way that's going to be a real pain
> in the ass to fix. Python doesn't do 'make'. what it does is a
> standard python setup.py build type of thing...

The consensus seems to be that Python's setuptools works well for
relatively simple extensions on supported platforms, but beyond that
you have to hack.

> Either that or we finally get around to implementing loadable modules .

Longer term that would be ideal, as you wouldn't have to rebuild
Python itself for every C extension module you wanted to use.  There's
also the simplifying requirement that Python extension module foo.so
must define an initialization function initfoo().

However, I think a bigger advantage to implementing dynamic module
loading for Python on Plan 9 would be that you could then use the new
"ctypes" foreign function library recently introduced w/ Python 2.5
which allows you to wrap C libraries in pure Python, dispensing w/
tedious boiler-plate wrapping C code--at the expense of some
type-safety. ;)

  John


  reply	other threads:[~2007-01-05  4:14 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-04 22:31 ron minnich
2007-01-05  4:14 ` John Barham [this message]
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
  -- 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
2006-12-23 21:50 [9fans] python 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-06  7:29 Russ Cox
2001-12-06  7:17 ` Lucio De Re
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=4f34febc0701042014p7e13c951gc20bd80f44aa44b6@mail.gmail.com \
    --to=jbarham@gmail.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).