> Nope. I don't have the PostgreSQL package installed (copying the DLLs was > intended to avoid that), and the goal is to run this compiled executable > on a system that doesn't have Python or pgsql installed. So having an > executable with an outside dependency of the entire database installation > just wouldn't be acceptable for the customer.
I just checked once more *without* any reference to PostgreSQL or Python in the PATH and found that's not even necessary. Py2exe has already copied all necessary DLLs (primarily _pg.pyd and libpq.dll) into the distribution directory, automatically. Pretty cool I think. > I did come up with a method that worked. Basically, I bundle the entire > c:\Python25 and some registry entries (to point to the bundled Python) > into a InnoSetup program. Hm maybe it's a Python 2.5 issue? I tested with Python 2.4 only, so far. -- Chris _______________________________________________ PyGreSQL mailing list [email protected] http://mailman.vex.net/mailman/listinfo/pygresql
