An update. I ended up not using py2exe or setuptools at all.
I wrote a script that copied python.exe, PythonService.exe, necessary libraries and my Python files with their dependencies into distribution directory. This directory is then packaged by InstallShield into Setup.exe. During installation, everything is dropped into user's target directory, so that his C:\Program Files\My Program looks a lot like my C:\Python24. Installer then registers PythonService.exe, puts python DLLs into %systemroot%, registers my python-based services, and everything just works. I do not have to worry about py2exe and eggs anymore, or about JSON engine not working because something is treated differently when it runs from a zip file. Turns out, life is simpler than I thought :) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears -~----------~----~----~----~------~----~------~--~---
