Best way of extending Python com or lnk or dll?

[Darrell]

Unless you're wrapping existing code, do new work in Python first.
Then if you really, really must, and have no other choice.
Take a look at a 'C' extension.
Often it's not worth the head ach to code it in 'C'.

Someone won't like this, but I'd avoid COM.
Unless you share your components with VB developers or the like.
For reuse in a Python environment .py files are great.

Several times now I've converted 'C' and Java apps to Python.
Once you get rid of the visual noise those languages come with.
A simplified solution may fall out.

Oh, don't I whish C++ required you use this->xyz
--Darrell


"Owen F. Ransen" <ransen_spam_me_not at nemo.it> wrote in message
news:3ae64b92.1979659 at news.newsguy.com...
> I'd like to extend Python and I'm not yet sure if it would
> be best to use COM (of which I know next to nothing) or
> a different method.
>
> I'd like to extend it for both Mac and Windows and it would
> probably be best to use methods as similar as is possible
> for these two environments, though it may not be easy....
>
> Is there an equivalent to Com on the Mac which works,
> would work, with Windows?
>
> I *think*, from reading the docs, is that the easiest way for
> me to add my own functions to Python on both the Mac and
> Windows is for me to statically link the new functions into
> the Python source.
>
> Any ideas/comments?
>
> --
> Owen F. Ransen
> http://www.ransen.com/
> Home of Gliftic & Repligator Image Generators