Re: Python Webstart ?

From: Fredrik Lundh (fredrik_at_pythonware.com)
Date: 09/19/04


To: python-list@python.org
Date: Sun, 19 Sep 2004 11:00:07 +0200


"huy" <nytimes@swiftdsl.com.au> wrote:

> Well not really. I don't mind doing one installation of a (Python/Java) webstart. However, it's
> the automatic update of the actual application software which I find most useful.

As long as you don't insist on upgrading Python itself all the time, that's
pretty easy. Here's how I usually do it:

1) Wrap the Python parts of your application in one or more ZIP archives.

2) Add a thin wrapper that can check for new versions of the ZIP archives
(and optionally install them) before starting the rest of the application:

    if check_for_updates():
        install_updates()
    fix_path()
    import my_application

3) Create a "platform" release that contains a python build, the extensions
you need, and a "baseline" version of your application. Use your favourite
tool for this purpose (eg. py2exe).

4) Let your users install the platform release.

5) When you prepare new versions, build new ZIP import packages
and put them where the wrapper can find them.

The wrapper can also install new versions of required extensions, offer
access to earlier versions of the application, etc.

I use a variation of this technique for the effbot.exe platform:

    http://effbot.org/zone/effnews-exe.htm

Here, the core installer simply installs Python (2.1, in this case) plus some
extensions, and a default application. Updates and additional applications
are shipped as "effbot" files, which are basically zipped-up PYC archives.
Works like a charm.

</F>



Relevant Pages

  • Re: Whats so funny? WAS Re: rotor replacement
    ... That I have to download and perhaps install them to use ... > * I have to download and build the MySQLdb package to talk to MySQL ... > servers from Python code ... I can write something using a core module instead of an external ...
    (comp.lang.python)
  • RE: Python 2.4 killing commercial Windows Python development ?
    ... > install fully useable Python on their Windows machines. ... > Quicksomething for Windows, or RealPlayer, ... The Windows application that I develop and distribute relies on Python ...
    (comp.lang.python)
  • Re: bytecode non-backcompatibility
    ... Unstable bytecodes makes updating to a newer version of Python very ... >>>tedious and risk breaking old scripts, ... > setup.py install" to install the library into site-package. ... each port has a list of all the other ports it depends ...
    (comp.lang.python)
  • HOWTO: Python 2.3 on Fedora Core 1 Linux
    ... About the 'new' Python ... Appendix A: Python Installation with Tkinter - edit: Modules/Setup.dist ... Be aware that it is always risky to install new software; ... # uncomment and/or edit those parts as indicated. ...
    (comp.lang.python)
  • Re: Python 2.4 killing commercial Windows Python development ?
    ... install fully useable Python on their Windows machines. ... different to me than having to install Shockwave, ... Quicksomething for Windows, or RealPlayer, ... The Windows application that I develop and distribute relies on Python ...
    (comp.lang.python)