Py2exe migration issue

Hi Sullivan (?)

me: win98, Py233, wxPy2515

Q: win platform?

I also have some concern about py2exe. May I humbly suggest you download
my application and report some feedback?
The goal is not to make some advertisement, I really just want to know if it
works. Thanks.
psi exe has been packed with py2exe 0.5.0. The installation has been created
with Inno Setup 4.1.5. It works ok on my win98 platform.

Thread:
http://lists.wxwidgets.org/cgi-bin/ezmlm-cgi?11:mss:27380:200404:jelhdncbgfblphcfbili

psi home page
http://www.chez.com/spinecho/pypsi/pagpypsi.htm

Jean-Michel Fauth, Switzerland

"Jean-Michel Fauth" <jmfauth@bluewin.ch> writes:

me: win98, Py233, wxPy2515

Q: win platform?

I also have some concern about py2exe. May I humbly suggest you download
my application and report some feedback?
The goal is not to make some advertisement, I really just want to know if it
works. Thanks.
psi exe has been packed with py2exe 0.5.0. The installation has been created
with Inno Setup 4.1.5. It works ok on my win98 platform.

What do you mean by 'concern'? Do you doubt that it works?
I downloaded psi-58-py233.exe, and it seems to work fine.
Win XP Pro, SP 1.

Thomas

Hi,

I want to make a correction: py2exe works for my app with
wxPython 2515, Python 233 on Win98, but cx_freeze
reports some missing DLLs when I run the .exe.

I am looking forward to the release of a new version of py2exe
that fixes the Win98 set .exe icon problem.

I wonder if it is possible for the app to load the embedded icon
from the .exe instead of an .ico file. This is to set the app's small
and big icons on wx.frame init.

Regards,
Steven.

Thomas Heller wrote:

···

"Jean-Michel Fauth" <jmfauth@bluewin.ch> writes:

me: win98, Py233, wxPy2515

Q: win platform?

I also have some concern about py2exe. May I humbly suggest you download
my application and report some feedback?
The goal is not to make some advertisement, I really just want to know if it
works. Thanks.
psi exe has been packed with py2exe 0.5.0. The installation has been created
with Inno Setup 4.1.5. It works ok on my win98 platform.
   
What do you mean by 'concern'? Do you doubt that it works?
I downloaded psi-58-py233.exe, and it seems to work fine.
Win XP Pro, SP 1.

Thomas

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

Steven Pang wrote:

Hi,

I want to make a correction: py2exe works for my app with
wxPython 2515, Python 233 on Win98, but cx_freeze
reports some missing DLLs when I run the .exe.

Which ones? Did you copy all the DLLs and .pyd's installed with wxPython to the target machine?

I wonder if it is possible for the app to load the embedded icon
from the .exe instead of an .ico file. This is to set the app's small
and big icons on wx.frame init.

I havn't tried it yet, but wxIconLocation is supposed to be able to pull icons from a .exe file. You give it the pathname and the index of the icon to pull out.

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

Hi,

I want to make a correction: py2exe works for my app with
wxPython 2515, Python 233 on Win98, but cx_freeze
reports some missing DLLs when I run the .exe.

I just discovered why: the builds for wxPython 2.5.1.5 are considerably
different than the ones for wxPython 2.4.2.4. I have made a change to
cx_Freeze to handle these differences and I can provide you a patch if
desired. Otherwise, I intend to make a new release with this change in
it in a few weeks.

···

On Wed, 2004-04-07 at 09:17, Steven Pang wrote:

Regards,
Steven.

Thomas Heller wrote:

>"Jean-Michel Fauth" <jmfauth@bluewin.ch> writes:
>
>
>
>>me: win98, Py233, wxPy2515
>>
>>Q: win platform?
>>
>>I also have some concern about py2exe. May I humbly suggest you download
>>my application and report some feedback?
>>The goal is not to make some advertisement, I really just want to know if it
>>works. Thanks.
>>psi exe has been packed with py2exe 0.5.0. The installation has been created
>>with Inno Setup 4.1.5. It works ok on my win98 platform.
>>
>>
>
>What do you mean by 'concern'? Do you doubt that it works?
>I downloaded psi-58-py233.exe, and it seems to work fine.
>Win XP Pro, SP 1.
>
>Thomas
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwidgets.org
>For additional commands, e-mail: wxPython-users-help@lists.wxwidgets.org
>
>
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-users-help@lists.wxwidgets.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

Anthony Tuininga wrote:

···

On Wed, 2004-04-07 at 09:17, Steven Pang wrote:

Hi,

I want to make a correction: py2exe works for my app with
wxPython 2515, Python 233 on Win98, but cx_freeze
reports some missing DLLs when I run the .exe.

I just discovered why: the builds for wxPython 2.5.1.5 are considerably
different than the ones for wxPython 2.4.2.4. I have made a change to
cx_Freeze to handle these differences

Which of the differences are tripping you up? The multiple wxGTK libs? The different wxPython extension module names? Just curious.

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

The different module names are not a problem. It is the list of
independent shared libraries that causes the grief. The issue, of
course, is what files need to be copied to create a standalone package.
py2exe follows the binary dependency chain and strips off those dlls
that it "knows" are part of the system itself. cx_Freeze does not do
this since I am not (as yet) convinced that the py2exe solution to the
problem is the ideal one. wxPython is the only package (that I am aware
of) that makes use of shared libraries that are not a part of the
modules themselves but exist as standalone libraries. In 2.4 there was
only one of them but in 2.5 there are several and the names don't match
the 2.4 names -- thus the problem. Does that satisfy your curiosity??
:slight_smile:

···

On Mon, 2004-04-12 at 17:32, Robin Dunn wrote:

Anthony Tuininga wrote:
> On Wed, 2004-04-07 at 09:17, Steven Pang wrote:
>
>>Hi,
>>
>>I want to make a correction: py2exe works for my app with
>>wxPython 2515, Python 233 on Win98, but cx_freeze
>>reports some missing DLLs when I run the .exe.
>
>
> I just discovered why: the builds for wxPython 2.5.1.5 are considerably
> different than the ones for wxPython 2.4.2.4. I have made a change to
> cx_Freeze to handle these differences

Which of the differences are tripping you up? The multiple wxGTK libs?
  The different wxPython extension module names? Just curious.

--
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

Anthony Tuininga wrote:

Anthony Tuininga wrote:

I just discovered why: the builds for wxPython 2.5.1.5 are considerably
different than the ones for wxPython 2.4.2.4. I have made a change to
cx_Freeze to handle these differences

Which of the differences are tripping you up? The multiple wxGTK libs? The different wxPython extension module names? Just curious.

The different module names are not a problem. It is the list of
independent shared libraries that causes the grief. The issue, of
course, is what files need to be copied to create a standalone package.
py2exe follows the binary dependency chain and strips off those dlls
that it "knows" are part of the system itself. cx_Freeze does not do
this since I am not (as yet) convinced that the py2exe solution to the
problem is the ideal one. wxPython is the only package (that I am aware
of) that makes use of shared libraries that are not a part of the
modules themselves but exist as standalone libraries. In 2.4 there was
only one of them but in 2.5 there are several and the names don't match
the 2.4 names -- thus the problem.

And the list of libs can change over time, or from different build options, etc. Perhaps just doing a wildcard match (libwx*) would do the trick for you?

Does that satisfy your curiosity??

Yep.

···

On Mon, 2004-04-12 at 17:32, Robin Dunn wrote:

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

It does, in fact. Thanks.

···

On Wed, 2004-04-14 at 14:24, Robin Dunn wrote:

Anthony Tuininga wrote:
> On Mon, 2004-04-12 at 17:32, Robin Dunn wrote:
>
>>Anthony Tuininga wrote:
>>>
>>>I just discovered why: the builds for wxPython 2.5.1.5 are considerably
>>>different than the ones for wxPython 2.4.2.4. I have made a change to
>>>cx_Freeze to handle these differences
>>
>>Which of the differences are tripping you up? The multiple wxGTK libs?
>> The different wxPython extension module names? Just curious.
>
>
> The different module names are not a problem. It is the list of
> independent shared libraries that causes the grief. The issue, of
> course, is what files need to be copied to create a standalone package.
> py2exe follows the binary dependency chain and strips off those dlls
> that it "knows" are part of the system itself. cx_Freeze does not do
> this since I am not (as yet) convinced that the py2exe solution to the
> problem is the ideal one. wxPython is the only package (that I am aware
> of) that makes use of shared libraries that are not a part of the
> modules themselves but exist as standalone libraries. In 2.4 there was
> only one of them but in 2.5 there are several and the names don't match
> the 2.4 names -- thus the problem.

And the list of libs can change over time, or from different build
options, etc. Perhaps just doing a wildcard match (libwx*) would do the
trick for you?

--
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