We've done that by using py2exe to build the executable program, then
take the output from that process and give it to an installer in the
conventional Windows way. Works nicely, no external dependencies at all
(it's all self-contained). You can even avoid the installer at a small
cost in runtime startup time.
If you do that with multiple apps you get multiples copies of the
dependencies (everything is self-contained). I expect that can be
avoided but I haven't looked to see how.
paul
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Arve Knudsen
> Sent: Friday, January 25, 2008 4:01 AM
> To: python-win32@python.org
> Subject: [python-win32] Embedding/bundling Python, best practices?
>
>
> Hello,
>
> We're planning to embed Python in our application, which mainly runs
> on Windows. To avoid dependencies, we want to bundle Python. Do any of
> you know of any resources on the Web describing best practices for
> bundling Python with an application, particularly on Windows? I have
> googled a bit, but most advice I found was to extend Python instead of
> embedding it, which wasn't very helpful :)
>
> Thanks,
> Arve Knudsen
> _______________________________________________
> python-win32 mailing list
> python-win32@python.org
> http://mail.python.org/mailman/listinfo/python-win32
>
_______________________________________________
python-win32 mailing list
python-win32@python.org
http://mail.python.org/mailman/listinfo/python-win32
