In <[EMAIL PROTECTED]>, [EMAIL PROTECTED] typed:
> > The downside is that you wind up with one copy of Python installed for
> > every script. If you've only got one script, this is ok. If you've got
> > more than one, you probably want to consider another approach.
> It will be the same, using several scripts, too.
>
> I have tried, I can do the following variant:
> - place all the python scripts into the script dir
> - create .exe files for the scripts
> - create an archive file containing python
>
> In this case, you will have only one python packaged , but several small
> scrits converted to .exe.
Unless you're doing something strange, the process of creating the
.exe files will put the python dll and copies of all the library files
into the .exe. Are you doing something to prevent that? And if so -
I'd be interested in knowing what.
> A few converted scritps look like this:
> PYTHON23 DLL 979 005 05.02.08 16.23 python23.dll
> W9XPOPEN EXE 16 384 05.02.08 16.24 w9xpopen.exe
> LIBRARY ZIP 311 060 05.10.12 19.30 library.zip
> LYX2LYX EXE 40 960 05.10.12 19.30 lyx2lyx.exe
> GENERA~1 EXE 28 672 05.10.12 19.30 general_command_wrapper.exe
> PIC2AS~1 EXE 28 672 05.10.12 19.30 pic2ascii.exe
>
> So, they can use the same interpreter.
This amounts to simply bundling the Python interpreter with LyX. I
think that's a great option - in fact, I think someone should bundle
up a complete system, with all the dependencies included - but I'm
pretty sure that shouldn't be the only binary offering available.
<mike
--
Mike Meyer <[EMAIL PROTECTED]> http://www.mired.org/consulting.html
Independent Network/Unix/Perforce consultant, email for more information.
