enchant and OS-X
Christopher Barker
The pyenchant package now provides an installer for a self-contained
packge on OS-X, which is very nice, as it was kind of a pain to install
before. This should also make it easier to bundle into a stand-alone
bundle of Peppy (using py2app). It might be nice to do that some day. I
tried once, and got tangled up in the dynamic importing of plugins.
Let me know if you want to give it a shot again.
I run it from SVN source, but it's be nice to have a stand-alone
executable I could point folks to.
-Chris
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Rob McMullen
<Chris....@noaa.gov> wrote:
> The pyenchant package now provides an installer for a self-contained packge
> on OS-X, which is very nice, as it was kind of a pain to install before.
Thanks for the heads-up about that.
> I run it from SVN source, but it's be nice to have a stand-alone executable
> I could point folks to.
I'd love your help to get this working. I never could get the dynamic
loading of plugins to work on win32/py2exe either so in the end I had
to generate a python file that force-imports all the plugins. I'd bet
something like that will work on py2app, but my osx-fu is quite
limited.
For win32, I have a fragile process (that is run mostly on my linux
box) involving a Makefile, bash scripts, python scripts, git (for the
version number), sphinx (for documentation; including latex and a huge
set of dependencies there in order to generate the manual in PDF) that
eventually culminate in a call to py2exe and the NSIS installer to
create a standalone installer.
See ticket: http://trac.flipturn.org/ticket/868
I just checked in a bit of the fragile chain that creates the python
file that imports all the plugins rather than deal with them
dynamically. That might help. The command 'bash build-archives.sh'
is the main driver for building py2exe, which calls 'make dist' and
then ssh-es to my virtualbox XP to complete the py2exe process. 'make
dist' will break for you immediately because you probably don't use
the git-svn bridge to generate peppy/_peppy_version.py. If you do:
mkdir .git
touch .git/index
and use the attached file for peppy/_peppy_version.py, it might git as
far as sphinx for the documentation. Comment out that dependency in
the makefile and it might get to the make-py2exe-plugin-list.py which
is probably the key.
In the meantime, if you get anywhere, let me know. I've just moved
into my new house so I'll have to find out which box contains the ol'
Mac and dust it off.
Rob
Christopher Barker
> On Mon, Nov 1, 2010 at 4:17 PM, Christopher Barker
>> I run it from SVN source, but it's be nice to have a stand-alone executable
>> I could point folks to.
>
> I'd love your help to get this working. I never could get the dynamic
> loading of plugins to work on win32/py2exe either so in the end I had
> to generate a python file that force-imports all the plugins. I'd bet
> something like that will work on py2app, but my osx-fu is quite
> limited.
yup -- should be similar.
> For win32, I have a fragile process (that is run mostly on my linux
> box) involving a Makefile, bash scripts, python scripts, git (for the
> version number), sphinx (for documentation; including latex and a huge
> set of dependencies there in order to generate the manual in PDF) that
> eventually culminate in a call to py2exe and the NSIS installer to
> create a standalone installer.
ah -- memory coming out of the fog -- yes I did poke into that, and it
got ugly, so I quit. Maybe it's a bit cleaner now? My advise to write as
much as possible of the process in Python -- a bit easier to keep cross
platform, and not depend on other tools. But OS-X has the unix stuff, so
I'll give it a try at some point.
> In the meantime, if you get anywhere, let me know.
will do.