On Fri, Aug 31, 2001 at 02:15:12PM -0700, Ken Simpson wrote:
> Jeff Youel posted some interesting questions in his recent Ethernet MAC
> address script (the first publicly announced script to use PyInline! --
> see it at http://www.jeffyouel.com), which I have paraphrased in this
> email. Perhaps other PyInliners out there could help me find answers to
> Jeff's questions.
Thanks Ken. I updated it with your suggestions for exceptions and returning
a PyObject. The latest is at http://www.jeffyouel.com/weblog/mac.py.
...snip...
> 3. How can I ship my inline Python script along with its compiled
> binary extensions?
>
> Currently, the only way to ship the binary part of your inline script is
> to first run the script on your system to generate and compile any inlined
> C source code and then ship the _PyInline_abc34234... directory along with
> your script.
>
> I am currently discussing this problem with Brian Ingerson (of Inline for
> Perl fame) and hope to have a better solution soon. Probably the new
> solution will involve configuration files...
>
I was thinking about deploying scripts with inlined code on a Windows
box (without a compiler). This would be very handy but not a rush for me.
> 4. How do I keep from collecting dozens of _PyInline_* directories while
> I'm developing?
>
> Currently, "rm -r _PyInline*" is the most effective strategy to reduce
> clutter. In future, PyInline will provide a configuration file inside a
> much better-named directory (perhaps _PyInline_MyModuleName) which
> contains the MD5 checksum of all inlined sources so that PyInline knows
> when to do a rebuild.
Yeah, figured that. It's really just a minor issue.
// Jeff
|
