PyPi package: 4.11 test release

[Matt Wilkie]

Hi Folks,

I've just uploaded Leo-4.11-devel-build-5769 to the Python Package Index:
https://pypi.python.org/pypi/leo

(todo: fix the readme, which is for 4.10, the 4.11 version remains to be written)

It can be downloaded from there and installed manually or, better yet, installed with `pip install leo`.

Pre-requisites are:

1. Python
2. PyQt
3. Distribute / Setuptools

Improvements over previous pypi package:

 - Sports Leo splash screen while installing on Windows

 - Installs "leo" and "leoc" wrappers to PYTHONHOME\Scripts, so as long as this directory is in PATH you don't need to create your own launcher (this is the part that requires Distribute. I'm working an way to include this automatically, http://stackoverflow.com/questions/16702658). It is common for this to be set.

- all the other changes in trunk over the last couple of weeks (http://bazaar.launchpad.net/~leo-editor-team/leo-editor/trunk3/changes)

cheers,

-matt

[Edward K. Ream]

On Wed, May 22, 2013 at 6:36 PM, Matt Wilkie <map...@gmail.com> wrote:

Hi Folks,

I've just uploaded Leo-4.11-devel-build-5769 to the Python Package Index:
https://pypi.python.org/pypi/leo

Interesting.  This looks like a completely different installer than the NSIS installer.  How did you create the installer?

Edward

[Matt Wilkie]

> Interesting.  This looks like a completely different installer than the NSIS installer.  How did you create the installer?

Specifically: `python setup.py bdist_wininst {options}`

More generally and usefully, using Distutils and Distribute: http://pythonhosted.org/distribute/. Someone else before me did the hard work of constructing setup.py, Ville according to bzr annotate. I've just fleshed it out a little.

There is a hook to run a postinstall script to create shortcuts and so on, which I haven't tried to figure out yet. Given how much it's taken to understand where we're at now I'm not sure I want to either! :)

I didn't set out to create an installer. My goal on starting was to make something that could be automatically downloaded and installed with the pip package manager. That an .exe (and/or .msi) installer could be created in the same process was a happy accident.

-matt

[Edward K. Ream]

On Thu, May 23, 2013 at 3:30 PM, Matt Wilkie <map...@gmail.com> wrote:

> Interesting.  This looks like a completely different installer than the NSIS installer.  How did you create the installer?

Specifically: `python setup.py bdist_wininst {options}`

I just took a look at setup.py.  It's remarkably simple.

Executing the .exe file installs Leo for a particular Python version.  This includes compiling all the .py files to object files, which is useful.  In contrast, the NSIS installer doesn't compile the .py files, which means the first time the user starts Leo there is a substantial delay.  The user might well be wondering what is happening.

So it looks there has been parallel progress.  I would prefer to use distutils to create the .exe installer.

There is a hook to run a postinstall script to create shortcuts and so on, which I haven't tried to figure out yet. Given how much it's taken to understand where we're at now I'm not sure I want to either! :)

I like the work you have done so far, but I think it's essential that whatever installer we use will create shortcuts and file associations.

Edward

[Edward K. Ream]

On Fri, May 24, 2013 at 4:29 PM, Edward K. Ream <edre...@gmail.com> wrote:

 

I just took a look at setup.py.  It's remarkably simple.

Happily, it appears that executing the .exe installer does *not* copy setup.py anywhere where it would be confusing to the user, so that's another plus.

EKR

[Matt Wilkie]

> Happily, it appears that executing the .exe installer does *not* copy
> setup.py anywhere where it would be confusing to the user, so that's another
> plus.

lp:~maphew/leo-editor/pypi-packaging

This branch has an incomplete adaptation of moving setup.py and
related "use only on a new computer" files into a common folder. If it
can be made to work completely then all users not just .exe installers
will have a cleaner root.

-matt