[forwarded submission from a non-member address -- rjk]
From: Mitchell N Charity <[EMAIL PROTECTED]> Date: Wed, 6 Feb 2002 17:07:50 -0500 Subject: Re: [Boston.pm] February tech meeting? - pyinline To: [EMAIL PROTECTED] I *think* that Neil Watkis or Ken Simpson have taken a first stab at inline.py, which is a Python equivalent to Inline. It probably just does C code at the moment, [...] Well, there's pyinline <http://ttul.org/~ksimpson/PyInline/>, by Ken Simpson. It's just C. Last release in August. Minimal documentation. It seems to work (at least inside of Inline::Python :), though I haven't been pressing it very hard. I'm playing run-time code generation games with Inline::C and Perl objects with auxiliary C API's, and pyinline was sufficient to do a first cut at making them usable from python. Neil Watkis has, on the Inline::Python todo list, the concept of allowing Python to be the "outer" program. One might drop him a line, expressing interest / asking how it's going. [...] but theoretically you could shim in Perl and a couple of modules through that mechanism with significantly less effort (and significantly less osmosis) than pyperl. :) There was a recent postin on the inline mailinglist, an "inline poetry" program which called Java/Tcl/Python/C using Inline::mumble, to generate "Perl calling Mumble" strings, each language contributing its own name. A natural extension might be a "drunken walker", to generating strings like "From Perl to Python to C to Perl to C to Python to C to TCL". It's still on my todo list, but sinking fast... Cheers, Mitchell Charity (Never noticed the Boston.pm before. Oh well.) * From: Adam Turoff * Subject: Re: [Boston.pm] February tech meeting? * Date: Sun, 03 Feb 2002 11:27:25 -0800 On Sat, Feb 02, 2002 at 02:41:17PM -0500, Dan Sugalski wrote: > On Sat, 2 Feb 2002 [EMAIL PROTECTED] wrote: > > Zope wound up being something content > > department found appropriate for their needs, and the software > > development found to be a good toolkit to work with. > > We'll just have to whip up a Python-equivalent of Inline::Python for > you. :) I *think* that Neil Watkis or Ken Simpson have taken a first stab at inline.py, which is a Python equivalent to Inline. It probably just does C code at the moment, but theoretically you could shim in Perl and a couple of modules through that mechanism with significantly less effort (and significantly less osmosis) than pyperl.
