On Mar 31, 4:53 pm, Amit Gupta <[EMAIL PROTECTED]> wrote: > On Mar 31, 1:52 pm, Mike Driscoll <[EMAIL PROTECTED]> wrote: > > > > > What about creating a setup.py and using the distutils command to > > build rpms or tarballs? > > >http://docs.python.org/dist/built-dist.html > > > Mike > > My quick look: The link you sent is under the header "Distributing > Python Modules". In my case, I have set of python-files that > altogether is part of one product-functionality. I would like to > package it and have it run standalone, even if the user does not have > python installed.
Good point. I guess I missed the "one product-functionality" requirement in your original post. Sorry for the noise! > > Ok, I guess build-dist can possibly achieve the same purpose (without > reading through the link you sent). So my question would be: why is > there pyinstaller, if this does the job. Is build-dist more low-level > and thus is over-kill for the kind of application I am looking for?: > > Thanks PyInstaller is for converting something you've written in Python into a binary for various OS's. When I read through the thread though, I thought your requirements might include distributing the modules as source too. If you want to produce a binary for Macs, I've heard that py2app does the job: http://pypi.python.org/pypi/py2app/ There's also cx_freeze, which is different than freeze.py: http://www.cxtools.net/default.aspx?nav=cxfrlb The last one is probably the best new advice I have to offer. Mike -- http://mail.python.org/mailman/listinfo/python-list
