RetroSearch Browse

Mon Jan 12 18:48:59 CET 2015 · https://mail.python.org/pipermail/python-dev/2015-January/137731.html

On Mon, 12 Jan 2015 17:26:43 +0000, Steve Dower <Steve.Dower at microsoft.com> wrote:
> David Anthoff wrote:
> > Yes, those are good examples. Right now doing this in the way these guys do is
> > too much work for our small project... Anything that makes this easier would be
> > appreciated.
> 
> I don't see how. All they've done is literally copy a Python
> installation into their install directory. Yes, they have their own
> launcher executables (py2exe generated, it looks like) and have
> precompiled the standard library and put it in a ZIP file, but you
> don't even need to go that far. Without knowing anything about your
> project I can't give specific suggestions, but simply dropping a
> Python installation in is not that difficult (and until the issues
> that Nick referred to are fixed, will have the same problems as
> TortoiseHg presumably has).

That's what py2exe *does*.  It does all the python-integration and
launcher-building work for you.  I use it for a small project myself
(proprietary), which I build an installer for using Inno Setup.  Works
very well, supports python3.

--David

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2015-January/137731.html below:

[Python-Dev] New Windows installer for Python 3.5