[python-win32] Re: Problems with py2exe and COM

[Giles A. Radford]

On Mon, Dec 29, 2003 at 10:30:19PM +0100, Thomas Heller wrote:
> Are you using py2exe 0.4.x? If so, you should switch to the (soon to be
> officially released) version 0.5.  Prereleases are in the Sourceforge
> project page, in the downloads section.  Note that these currently
> require win NT, 2k, or XP, and Python 2.3, and, for COM, win32all 163.

It works a dream, apart form the fact that you can't seem to use python
2.3 to be a client for a python 2.3 server inside a DLL. But I read
somewhere that's a known problem. Any idea if it's solvable at all?

The configuration file was a bit abstruse to understand, but I managed
to get the gist fo it in the end. In the advanced sample, you may, for
clarity, want to make the com_server line point to the interp object you
set up earlier

> There's no documentation so far ;-)

This seems to be a weakness of PythonCOM generally. If you give me a
heads up and are willign to answer questions, I'm quite happy to at
least start documenting py2exe for you...

> --debug build debug versions of the executables, normally you don't want
> to do this, also you need debug versions of Python, py2exe, win32all,
> and whatever you use.

aah, right. I thoguht it would just register the COM server for
debugging.

OK: next question- Do I really need everythin in "build", or can I just
send webupdater.dll and the library.zip file over? How exactly does this
work? If so, what's the best place for this stuff to be installed on a
standard windows installation? I have a bunch of dlls, including
python23.dll, a bunch of .pyds and a library.zip file

Incidentally, My co-programmer is getting rather annoyed that the python
objects I've created aren't showing up under VB at all. He's tryign to
get things like autocompletion of method names going. Any idea how I
could get that going? Or at least get the application showing up on his
list of things to include?

Moof