Hi Matt, if you don't have any C extensions to deal with and can assume Python is already present on the destination system, then a zipfile with a __main__.py file may also be a suitable solution (see PEP 441 for more info about that feature - it's been supported since 2.6, the PEP just proposes some better tools in the standard library for creating them)
Cheers, Nick. On Sat, May 25, 2013 at 5:46 PM, Matt Wilkie <map...@gmail.com> wrote: > Thanks PJ. > > I haven't used py2exe as I don't want to redistribute python also, > just our program. I'll dig into your other suggestions and see where I > end up. > > -matt > > > On Wed, May 22, 2013 at 10:22 PM, PJ Eby <p...@telecommunity.com> wrote: >> >> On Wed, May 22, 2013 at 8:12 PM, Matt Wilkie <map...@gmail.com> wrote: >> > How do I get my installer to include Distribute so I don't have to tell our >> > users "before you install our program you have to go install this other >> > program"? >> >> Setuptools (which Distribute is based on) is designed for shipping >> libraries, not applications; it's developer installer, not primarily >> an end-user installer for applications. So you probably should be >> using py2exe instead. >> >> Alternatively, you can bundle a copy of pkg_resources.py, or use a >> script that doesn't depend on entry points, or copy your script to >> "foo-script.py" alongside the .exe launcher, and manually include >> those two files as scripts (not using entry points) in your setup() >> definition. >> >> Any of these approaches will solve the problem; it's mostly a matter >> of your preferences or other requirements. > _______________________________________________ > Distutils-SIG maillist - Distutils-SIG@python.org > http://mail.python.org/mailman/listinfo/distutils-sig -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org http://mail.python.org/mailman/listinfo/distutils-sig