Create executable for wxPython script

Yes, I too started with py2exe but later switched to Installer because
of some problems with win32 libraries.

A few more postings - and we can launch a Holy War ;).

2 Anthony Tuininga: Anthony, have you have your scripts available
somewhere in the net? It would be interesting to look at them.

Victor.

···

----
Sincerely Yours, Victor V. Kryukov, UFG
phone: +7501 967 3727, ext. 4387
email: vkryukov@ufg.com

-----Original Message-----
From: Kevin Ollivier [mailto:kevino@tulane.edu]
Sent: Tuesday, November 12, 2002 7:26 PM
To: wxPython-users@lists.wxwindows.org
Subject: Re: [wxPython-users] Create executable for wxPython script

Hi all,

I want to second this recommendation - I use it for my program and it
works like a charm. I tried py2exe first, but it seemed to
have trouble
including all of my program libraries, so I switched to
Installer and it
worked without problems. (I think it was the win32 libraries
that py2exe
was having trouble with, but it was a while back.) Apparently
with some
tweaks you can now run it on Mac OS X as well. =)

Kevin

On Tuesday, November 12, 2002, at 07:12 AM, Krjukov Victor wrote:

> Hi!
>
> I personally would suggest McMillian's installer
> http://www.mcmillan-inc.com/install1.html
> which looks a little bit more usefriendly for me, and also
exists for
> both Windows and Linux platforms.
>
> ----
> Sincerely Yours, Victor V. Kryukov, UFG
> phone: +7501 967 3727, ext. 4387
> email: vkryukov@ufg.com
>
>> -----Original Message-----
>> From: Bjorn Platzen [mailto:bplatzen@sosnetz.de]
>> Sent: Tuesday, November 12, 2002 3:01 PM
>> To: wxPython-users@lists.wxwindows.org
>> Subject: Re: [wxPython-users] Create executable for wxPython script
>>
>>
>> Hi!
>>
>>> Is there a way I can package up a set of wxPython and
>> Python scripts to
>>> create an executable, so that neither Python nor wxPython
need to be
>>> installed on the machine the scripts will be run on?
>>
>> Do you want to create executables for Win, Lin or Mac?
>>
>> For win there exist a distutil named py2exe[1]. This worked
>> good for me ...
>>
>> At the bottom of the py2exe-Homepage you will find some more
>> links to related
>> work that should work on Lin as well.
>>
>> hth,
>>
>> Bjoern
>>
>> [1] http://starship.python.net/crew/theller/py2exe/
>>
>> --
>> small office solutions
>> info@sosnetz.de - http://www.sosnetz.de
>>
>>
---------------------------------------------------------------------
>> To unsubscribe, e-mail:
wxPython-users-unsubscribe@lists.wxwindows.org
>> For additional commands, e-mail:
>> wxPython-users-help@lists.wxwindows.org
>>
>>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
wxPython-users-unsubscribe@lists.wxwindows.org
> For additional commands, e-mail:
wxPython-users-help@lists.wxwindows.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwindows.org
For additional commands, e-mail:
wxPython-users-help@lists.wxwindows.org

My freeze scripts are not currently available on the net. I have sent
them to a few people, received feedback and used them internally in our
company for several months and have been quite satisfied with them.

I am intending to put them up on our site to join cx_Oracle which is
already there. That may take a few days, however, so if you want to see
them sooner, let me know and I'll send you a copy in advance.

···

On Tue, 2002-11-12 at 09:33, Krjukov Victor wrote:

Yes, I too started with py2exe but later switched to Installer because
of some problems with win32 libraries.

A few more postings - and we can launch a Holy War ;).

2 Anthony Tuininga: Anthony, have you have your scripts available
somewhere in the net? It would be interesting to look at them.

Victor.

----
Sincerely Yours, Victor V. Kryukov, UFG
phone: +7501 967 3727, ext. 4387
email: vkryukov@ufg.com

> -----Original Message-----
> From: Kevin Ollivier [mailto:kevino@tulane.edu]
> Sent: Tuesday, November 12, 2002 7:26 PM
> To: wxPython-users@lists.wxwindows.org
> Subject: Re: [wxPython-users] Create executable for wxPython script
>
>
> Hi all,
>
> I want to second this recommendation - I use it for my program and it
> works like a charm. I tried py2exe first, but it seemed to
> have trouble
> including all of my program libraries, so I switched to
> Installer and it
> worked without problems. (I think it was the win32 libraries
> that py2exe
> was having trouble with, but it was a while back.) Apparently
> with some
> tweaks you can now run it on Mac OS X as well. =)
>
> Kevin
>
> On Tuesday, November 12, 2002, at 07:12 AM, Krjukov Victor wrote:
>
> > Hi!
> >
> > I personally would suggest McMillian's installer
> > http://www.mcmillan-inc.com/install1.html
> > which looks a little bit more usefriendly for me, and also
> exists for
> > both Windows and Linux platforms.
> >
> > ----
> > Sincerely Yours, Victor V. Kryukov, UFG
> > phone: +7501 967 3727, ext. 4387
> > email: vkryukov@ufg.com
> >
> >> -----Original Message-----
> >> From: Bjorn Platzen [mailto:bplatzen@sosnetz.de]
> >> Sent: Tuesday, November 12, 2002 3:01 PM
> >> To: wxPython-users@lists.wxwindows.org
> >> Subject: Re: [wxPython-users] Create executable for wxPython script
> >>
> >>
> >> Hi!
> >>
> >>> Is there a way I can package up a set of wxPython and
> >> Python scripts to
> >>> create an executable, so that neither Python nor wxPython
> need to be
> >>> installed on the machine the scripts will be run on?
> >>
> >> Do you want to create executables for Win, Lin or Mac?
> >>
> >> For win there exist a distutil named py2exe[1]. This worked
> >> good for me ...
> >>
> >> At the bottom of the py2exe-Homepage you will find some more
> >> links to related
> >> work that should work on Lin as well.
> >>
> >> hth,
> >>
> >> Bjoern
> >>
> >> [1] http://starship.python.net/crew/theller/py2exe/
> >>
> >> --
> >> small office solutions
> >> info@sosnetz.de - http://www.sosnetz.de
> >>
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail:
> wxPython-users-unsubscribe@lists.wxwindows.org
> >> For additional commands, e-mail:
> >> wxPython-users-help@lists.wxwindows.org
> >>
> >>
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> wxPython-users-unsubscribe@lists.wxwindows.org
> > For additional commands, e-mail:
> wxPython-users-help@lists.wxwindows.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwindows.org
> For additional commands, e-mail:
> wxPython-users-help@lists.wxwindows.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwindows.org
For additional commands, e-mail: wxPython-users-help@lists.wxwindows.org

--
Anthony Tuininga
anthony@computronix.com

Computronix
Distinctive Software. Real People.
Suite 200, 10216 - 124 Street NW
Edmonton, AB, Canada T5N 4A3
Phone: (780) 454-3700
Fax: (780) 454-3838
http://www.computronix.com

Anthony Tuininga wrote:

My freeze scripts are not currently available on the net. I have sent
them to a few people, received feedback and used them internally in our
company for several months and have been quite satisfied with them.

Can you give a quick description of what advantages your scripts might
have over Installer? It sounds like they are attempting to solve the
same problem.

One quick question about either your aproach or Installer: Does it
handle "reload" ? Py2exe does not, and that has been an annoyance in the
past.

-Chris

···

--
Christopher Barker, Ph.D.
Oceanographer
                                        
NOAA/OR&R/HAZMAT (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception

Chris.Barker@noaa.gov

Apologies in advance as this is slightly offtopic.... :slight_smile:

Yes, they are attempting to solve the same problem. I have used
Installer in the past but ran into a few issues, specifically that
Installer is very invasive and requires the use of an import hook to
work properly. My approach was to avoid the use of an import hook
entirely and use the "frozen" support that is already built in to
Python. Thus, I have created a few "base" executables for the different
platforms that I support and a "FreezePython" utility is run which finds
all of the modules required and adds them to the end of the executable
(this part is the same or similar to Py2exe and Installer). At runtime,
the modules are read and Python is told about the list of frozen modules
and then Python takes over -- the minimum amount of code is executed to
avoid issues with the "source" version and the "frozen" version working
differently (and I had those with Installer and py2exe).

The "base" executables that I know currently work are:

Console (Linux, Win32, Solaris, Tru64 Unix)
Win32 GUI (Windows insists on a different format for these)
Win32 Service
DLL (generic means of embedding Python in a DLL)

If you have any other questions, feel free to contact me.

···

On Tue, 2002-11-12 at 11:34, Chris Barker wrote:

Anthony Tuininga wrote:
>
> My freeze scripts are not currently available on the net. I have sent
> them to a few people, received feedback and used them internally in our
> company for several months and have been quite satisfied with them.

Can you give a quick description of what advantages your scripts might
have over Installer? It sounds like they are attempting to solve the
same problem.

One quick question about either your aproach or Installer: Does it
handle "reload" ? Py2exe does not, and that has been an annoyance in the
past.

-Chris

--
Christopher Barker, Ph.D.
Oceanographer
                                        
NOAA/OR&R/HAZMAT (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception

Chris.Barker@noaa.gov

---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwindows.org
For additional commands, e-mail: wxPython-users-help@lists.wxwindows.org

--
Anthony Tuininga
anthony@computronix.com

Computronix
Distinctive Software. Real People.
Suite 200, 10216 - 124 Street NW
Edmonton, AB, Canada T5N 4A3
Phone: (780) 454-3700
Fax: (780) 454-3838
http://www.computronix.com

Anthony Tuininga <anthony@computronix.com> writes:

Apologies in advance as this is slightly offtopic.... :slight_smile:

Yes, they are attempting to solve the same problem. I have used
Installer in the past but ran into a few issues, specifically that
Installer is very invasive and requires the use of an import hook to
work properly. My approach was to avoid the use of an import hook
entirely and use the "frozen" support that is already built in to
Python. Thus, I have created a few "base" executables for the different
platforms that I support and a "FreezePython" utility is run which finds
all of the modules required and adds them to the end of the executable
(this part is the same or similar to Py2exe and Installer). At runtime,
the modules are read and Python is told about the list of frozen modules
and then Python takes over -- the minimum amount of code is executed to
avoid issues with the "source" version and the "frozen" version working
differently (and I had those with Installer and py2exe).

The "base" executables that I know currently work are:

Console (Linux, Win32, Solaris, Tru64 Unix)
Win32 GUI (Windows insists on a different format for these)
Win32 Service
DLL (generic means of embedding Python in a DLL)

(Even more off-topic :wink:

Based on the ideas from Anthony, but without looking at his code, I am
currently changing py2exe to do it a similar way. Anthony is right:
We don't need no stinkin import hook :-), it works *much* better this
way.

With an additional change to freeze's ModuleFinder I am even able
to convert some PyXML test-scripts into executables.

The exe-files are much larger this way (similar to what you can expect
from freeze), although the frozen module table can also be compressed
by zlib or something comparable.

An additional advantage is that the py2exe'd script can no longer be
unpacked into the .pyc files by winzip - which annoyed a lot of users.

Thomas

by the way,
is there a way to suppress the black windows that appears when you run a
wxpython script ?
especially, i would like to suppress this windows even after py2exe !!

thanks

Manu

Dr E B Bettler <bettler@cmbi.kun.nl> writes:

by the way,
is there a way to suppress the black windows that appears when you run a
wxpython script ?
especially, i would like to suppress this windows even after py2exe !!

Rename the python script from something.py into something.pyw.

This should even do the trick for py2exe. Otherwise, if you don't want
to do this, there's the --windows or -w command line flag.

Thomas

When you compile it do this:

  setup py2exe -w

-w is for window

Or do this for more info:

  setup py2exe --help

Matthew Sherborne

···

----- Original Message -----
From: "Dr E B Bettler" <bettler@cmbi.kun.nl>
To: <wxPython-users@lists.wxwindows.org>
Sent: Wednesday, November 13, 2002 10:10 PM
Subject: [wxPython-users] Create executable for wxPython script

by the way,
is there a way to suppress the black windows that appears when you run a
wxpython script ?
especially, i would like to suppress this windows even after py2exe !!

thanks

Manu

---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwindows.org
For additional commands, e-mail: wxPython-users-help@lists.wxwindows.org