X-Received: by 10.50.142.71 with SMTP id ru7mr647391igb.11.1450313132300; Wed, 16 Dec 2015 16:45:32 -0800 (PST) X-Received: by 10.50.115.41 with SMTP id jl9mr20173igb.10.1450313132286; Wed, 16 Dec 2015 16:45:32 -0800 (PST) Path: csiph.com!au2pb.net!feeder.erje.net!2.us.feeder.erje.net!news.glorb.com!mv3no17174292igc.0!news-out.google.com!f6ni25078igq.0!nntp.google.com!mv3no17174288igc.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.python Date: Wed, 16 Dec 2015 16:45:31 -0800 (PST) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=23.30.65.94; posting-account=h3aEwQoAAACiuqX-oR3gvCVFm8lLHoWj NNTP-Posting-Host: 23.30.65.94 References: User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: How does one distribute Tkinter or Qt GUI apps Developed in Python From: Rick Johnson Injection-Date: Thu, 17 Dec 2015 00:45:32 +0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Xref: csiph.com comp.lang.python:100545 On Wednesday, December 16, 2015 at 6:03:55 PM UTC-6, Bruce Whealton wrote: > Surely, one is going to want to create GUI apps for users > that are not Python Developers. I would not think to ask > someone to install Python on their system and make sure it > is added to the path. Maybe it is not so hard for the non- > technical, average users. >=20 > I would want to package in some way so that when launched, > it installs whatever is needed on the end user's computer. > How is this done? Are there common practices for this? Your assumptions are correct! In fact, in a language that was "supposedly" = designed to be an "applications language" (eat your heart out D'Aprano!!!),= one would think that distributing apps would not only be obvious, but also= intuitive! ALAS, THE CRUEL REALITIES OF INTERPRETED LANGUAGES SLAPS YOU IN THE PASTEY= WHITE FACE!=20 Unlike a true "applications language", like say, um, *JAVA*, one cannot sim= ply compile an executable and distribute it in a teeny tiny binary form, no= , with Python, the end user must either (1) have Python on his machine alre= ady, (2) download Python, or (3) you must package a Python interpreter alon= g with your script (and dependencies) -- which will end up being a very lar= ge file just to run (what is in most cases) a very small script.=20 BOO-HISS! But the good news is that, Python ships on many machines already. But of co= urse, you're seeking more consistency in your distribution QA than the "wil= d guess" and the fickle nature of "lady luck".=20 Many 3rd party libraries exist to solve your distribution issue. Google pro= bably knows about all (or at least most) of them.