On Thu, 21 Sep 2006 17:39:10 +1000, Mark Hammond
<mhammond@[...].au>  wrote:
> > py2exe works perfectly for python 2.4.  I just don't
> > understand what changed...
> 
> Me either, but sadly I haven't had a chance to try 2.5 with py2exe.  I
> assume you are working with the 209.1 build for 2.5 - earlier builds will
> fail to work (but will fail the same way regardless of py2exe)

	Yeah, I'm using 209.1 for 2.5 and version 208 for python 2.4

> Note 'import pythoncom' just imports a .py file, which itself attempts to
> load a DLL.  Does pythoncom.pyo appear in your library?

	Interesting note here...NEITHER 2.4 nor 2.5 has a
pythoncom.pyo file in the build\bdist.win32\winexe\collect-2.x
directory.  Yet it most definitely imports correctly in 2.4.

	This is such a bizarro circumstance that I'm lead to wonder if
there is some horrible bug creeping about in the new
"absolute/relative" import mechanism for 2.5.  I would have no clue
how to go about confirming that, though.

	In this email I have included a simple program to demonstrate
the problem and the compile script I used to compile it.  Note that
the simple program is literally:

import pythoncom
print "hello world"

	In my tests, this bombs rather spectacularly.  (Please don't
run the compile script as it appears here.  I have customized it to my
development system.  It's similar enough to the single-exe compile
script example I got from the py2exe distribution...)

	Any help would be appreciated.  I'd love to move to Python2.5,
but my deployables REQUIRE a single-exe distribution.

> Mark

PS: Running my software from source works fine, so I know it's not my
code causing problems.  It's a fundamental problem in the interaction
between py2exe 0.6.5 and python 2.5

Christoper L. Spencer
CTO ROXX, LLC
4515 Leslie Ave.
Cincinnati, OH
45242
TEL: 513-545-7057
EMAIL: chris@roxx.biz