Hi Jorma,
Jorma Paavola wrote:
...
1) Ansi build
I´ll try that next ==> this means, that I have to uninstall Unicode-versions from W2k and install Ansi-version instead(because I have only one w2k-machine available!)
I´ll let you know the results
You don't have to un-install Unicode.
Check this page:
http://wiki.wxpython.org/index.cgi/MultiVersionInstalls
Werner
Werner F. Bruhin kirjoitti:
Hi Jorma,
Jorma Paavola wrote:
...
1) Ansi build
I´ll try that next ==> this means, that I have to uninstall Unicode-versions from W2k and install Ansi-version instead(because I have only one w2k-machine available!)
I´ll let you know the resultsYou don't have to un-install Unicode.
Check this page:
http://wiki.wxpython.org/index.cgi/MultiVersionInstallsWerner
Hi Werner,
Thanks again - I noted a possibility to have both Ansi/Unicode installed !
==> Ansi and Unicode gave same Error !
Based on my earlier experience with resource problems with other programs on Win98 - and especially after checking the size of memoryallocation of my TestGUI(exe)abt. 24 MB on running!! (Exe- Filesize is abt. 5 MB !)I am now quite convinced of that.
I have one question about your "gc.function-code":
- what/how is the meaning/use of last row: x = gc.collect() ?
Thanks and regards,
Jorma
Hi Jorma,
Werner F. Bruhin kirjoitti:
> Hi Jorma,
>
> Jorma Paavola wrote:
>> ...
>>
>> 1) Ansi build
>> I´ll try that next ==> this means, that I have to uninstall
>> Unicode-versions from W2k and install Ansi-version instead(because I
>> have only one w2k-machine available!)
>> I´ll let you know the results
> You don't have to un-install Unicode.
>
> Check this page:
> http://wiki.wxpython.org/index.cgi/MultiVersionInstalls
>
> Werner
Hi Werner,Thanks again - I noted a possibility to have both Ansi/Unicode installed !
==> Ansi and Unicode gave same Error !
Based on my earlier experience with resource problems with other
programs on Win98 - and especially after checking the size of
memoryallocation of my TestGUI(exe)abt. 24 MB on running!! (Exe-
Filesize is abt. 5 MB !)I am now quite convinced of that.I have one question about your "gc.function-code":
- what/how is the meaning/use of last row: x = gc.collect() ?
What Werner did was to force Python to garbage-collect all Python
objects that do not have any reference anymore (i.e., they are useless
and can be safely destroyed/removed to increase the resource
availability).
Quoting Fredrik Lundh very useful help pages:
"""
Python uses reference counting to keep track of when to get rid of
objects; as soon as the last reference to an object goes away, the
object is destroyed.
Starting with version 2.0, Python also provides a cyclic garbage
collector, which runs at regular intervals. This collector looks for
data structures that point to themselves, and does what it can to
break the cycles.
You can use the gc.collect function to force full collection. This
function returns the number of objects destroyed by the collector.
"""
Andrea.
"Imagination Is The Only Weapon In The War Against Reality."
http://xoomer.virgilio.it/infinity77/
On 5/3/07, Jorma Paavola wrote:
Werner F. Bruhin kirjoitti:
Hi Jorma,
Jorma Paavola wrote:
Werner F. Bruhin kirjoitti:
...
if __name__ == "__main__":
app = wx.PySimpleApp()
MyGcCollect('','Test',1,1)
frame = Frame(None)
frame.Show()
app.MainLoop()gives now error message:
Traceback (most recent call last):
File "C:\Documents and Settings\Administrator\My Documents\Omat softat\Morod.py", line 38, in <module>
MyGcCollect('','Test',1,1)
File "C:\Documents and Settings\Administrator\My Documents\Omat softat\Morod.py", line 26, in MyGcCollect
wx.PD_AUTO_HIDE | wx.PD_APP_MODAL)
AttributeError: 'str' object has no attribute 'dlgPro'=========================================================================
and opens ProgressDialog-window in "Tilt-state" !
Obviously my functioncall-parameters are invalid ? - but how ?
You are calling MyGcCollect with a string ('') as the first parameter.
Try the enclosed sample, just change this line:
if runningPlatform[0] == 6:according to your test platform.
Werner
------------------------------------------------------------------------
#Boa:Frame:Frame1
import wx
import gc
import sysrunningPlatform = sys.getwindowsversion()
def create(parent):
return Frame1(parent)[wxID_FRAME1] = [wx.NewId() for _init_ctrls in range(1)]
class Frame1(wx.Frame):
def _init_ctrls(self, prnt):
wx.Frame.__init__(self, style=wx.DEFAULT_FRAME_STYLE, name='', parent=prnt, title='Frame1', pos=wx.Point(-1, -1), id=wxID_FRAME1, size=wx.Size(-1, -1))def __init__(self, parent):
self._init_ctrls(parent)
self.MyGcCollect('Test',3,1)
wx.Sleep(2)
wx.YieldIfNeeded()
self.MyGcCollect('Test',3,2)
wx.Sleep(2)
wx.YieldIfNeeded()
self.MyGcCollect('Test',3,3)
def MyGcCollect(self, message='', max=0, done=0):
if runningPlatform[0] == 6: # Testaa onko Windows 9x
if done == 1:
self.dlgPro = wx.ProgressDialog('Windows 9x - forcing release of resources',
message,
max,
None,
wx.PD_AUTO_HIDE | wx.PD_APP_MODAL)
self.dlgPro.Update(done, message)
if done == max:
self.dlgPro.Destroy()
x = gc.collect()if __name__ == '__main__':
app = wx.PySimpleApp()
frame = create(None)
frame.Show()app.MainLoop()
------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-users-help@lists.wxwidgets.org
Hi Werner,
I 'compiled'this sw into .exe-file with Py2exe and ran it by "double-clicking":
1) in Win2k - PC (python sw´s installed)==> Running OK, when started by double-click(as before) !
2) in 'clean' Win 98 - PC (no python sw´s installed) ==> Unfortunately generates Traceback:
Traceback (most recent call last):
File "Morow.py", line 49, in <module>
File "Morow.py", line 15, in create
File "Morow.py", line 25, in __init__
File "Morow.py", line 41, in MyGcCollect
File "wx\_windows.pyo", line 2928, in __init__
wx._core.PyAssertionError: C++ assertion "wxAssertFailure" failed at ..\..\src\msw\control.cpp(159) in wxControl::MSWCreateControl(): CreateWindowEx("msctls_progress32", flags=52000000, ex=00000200) failed
NOTE: Original TestSW (without GcCollect) could not create any wxWindowClassNR !
3) Original TestSW (without GcCollect) generates Tracebacks:
on 'clean' WinMe PC:
Traceback (most recent call last):
File "Moro.py", line 1, in <module>
File "zipextimporter.pyo", line 82, in load_module
File "wx\__init__.pyo", line 45, in <module>
File "zipextimporter.pyo", line 82, in load_module
File "wx\_core.pyo", line 4, in <module>
File "zipextimporter.pyo", line 98, in load_module
ImportError: MemoryLoadLibrary failed loading wx\_core_.pyd
and on 'clean' WinXp PC:
Traceback (most recent call last):
File "Moro.py", line 1, in <module>
File "zipextimporter.pyo", line 82, in load_module
File "wx\__init__.pyo", line 45, in <module>
File "zipextimporter.pyo", line 82, in load_module
File "wx\_core.pyo", line 14244, in <module>
File "zipextimporter.pyo", line 82, in load_module
File "wx\_gdi.pyo", line 2972, in <module>
File "wx\_gdi.pyo", line 2781, in AddCatalogLookupPathPrefix
UnicodeDecodeError: 'ascii' codec can't decode byte 0xf6 in position 33: ordinal not in range(128)
Should we consider these annoying results stating, that (Py2exe)-'compiled' .exe-files cannot run in any other PC´s if Python-Sw´s are not pre-installed ?? (ie. platform/OS/version - conflict)
or
Are there still error somewhere ?
Regards,
Jorma
Werner F. Bruhin kirjoitti:
Hi Jorma,
Jorma Paavola wrote:
Hi Werner !
I assume you changed this:
if runningPlatform[0] == 6: # Testaa onko Windows 9x
to something like this:
if runningPlatform[0] < 4: # Testaa onko Windows 9xYou are right:
- with Win98 I changed runningPlatform[0] == 4:,
which according to my knowledge: major == 4 and minor == 10; and therefore should be OK ! (Ansi-version used !)I am not sure what the version number for WinMe and/or 9x, but I think if you use " <4" you should catch anything before Win NT.
3) Original TestSW (without GcCollect) generates Tracebacks:
on 'clean' WinMe PC:Traceback (most recent call last):
ImportError: MemoryLoadLibrary failed loading wx\_core_.pydSee above, make sure that you use a version which includes ME, so gc.collect is run.
Pls. Note: For testing Me I used my "original" TestSw (without GcCollect & platformtest) Unicode-version
I think 98 and ME (this one is probably even worse) have the same kind of problems, so you should use the version with gc.collect.
For testing 98 I used the version with gc.collect Ansi-version with runningPlatform(test) == 4 as already described above <=> in despite of that I got "Traceback":'
in 'clean' Win 98 - PC (no python sw´s installed) ==> Unfortunately generates Traceback:
Traceback (most recent call last):
File "Morow.py", line 49, in <module>
File "Morow.py", line 15, in create
File "Morow.py", line 25, in __init__
File "Morow.py", line 41, in MyGcCollect
File "wx\_windows.pyo", line 2928, in __init__
wx._core.PyAssertionError: C++ assertion "wxAssertFailure" failed at ..\..\src\msw\control.cpp(159) in wxControl::MSWCreateControl(): CreateWindowEx("msctls_progress32", flags=52000000, ex=00000200) failed
which I cannot understand - I see only two possibilities for that:
- Py2exe don´t create a common, complete Win-based 'compilation' on Win2k and/or my used setup.py is not complete enough ??
and on 'clean' WinXp PC:
UnicodeDecodeError: 'ascii' codec can't decode byte 0xf6 in position 33: ordinal not in range(128)
This is a totally different problem. I think this could be fixed by changing your default encoding to something other then ascii.
Pls. Note: For testing Xp I used my "original" TestSw (without GcCollect & platformtest) Unicode-version
If you used the Unicode version for this one, then I don't understand that you get a decode error. I didn't think it would use ascii as the default, but I can't remember.
This is really strange - even more strange when I tell, that when I ran it on Xp with Me- or 98 Emulation Mode my "original" Testsw worked perfectly again !?
- I got Traceback on Xp only when running on normal mode and Win2k emulation mode !!?
I do this in my wx.App module:
if hasattr(sys, "frozen"): #Py2Exe does not run Site.py
sys.setdefaultencoding('iso-8859-1')
del sys.setdefaultencoding- I'll try that as well - should I test first this working (on win2k)-ANSI version (with GcCollect) on WinMe and WinXp, or do you think, that Unicode/Ansi has no influence to the problem ?
Should we consider these annoying results stating, that (Py2exe)-'compiled' .exe-files cannot run in any other PC´s if Python-Sw´s are not pre-installed ?? (ie. platform/OS/version - conflict)
I don't think this is the case. Otherwise why even bother having py2exe - BTW, which version of py2exe are you using?
Py2exe 0.6.6
or
Are there still error somewhere ?
Yeap, this is more like it:)
If you still have problems I suggest that you create a small sample application which shows the problem and post it here together with your setup.py.
I´ll do so after seen your answer first
Werner
Thanks & regards,
Jorma
Werner
I´ll send my Test.py and my setup.py to morrow to you.
Jorma
Big Pipe Dream: Any change wxPython will ever be able to run inside a browser? (or all browsers?)
- Ken Seehart
There used to be a plugin for mozilla based browsers that allowed Python
to run. You may try looking around for it.
- Josiah
Ken Seehart <ken@seehart.com> wrote:
Big Pipe Dream: Any change wxPython will ever be able to run inside a
browser? (or all browsers?)
Hi Werner !
I found out, that Boa 0.4.4 from Sourceforge wount work and I replaced it by 0.5.2 version from CVS.
It works fine - thanks a lot !
I listed 3 questions on my right previous Email - waiting for your comments/reply...
Jorma
Werner F. Bruhin kirjoitti:
Hi Jorma,
Jorma Paavola wrote:
Hi Werner,
Hereby I submit my used GUItest.py and setup.py , which don´t 'compile' on Win2k (ANSI) the proper .exe-file to run in Win98 environement(generates Traceback as sent before).
Could you see any essential reason in my setup.py used or something else ... ??
Your p2e_test.py by standard should be called setup.py (nice things happen then in e.g. Boa, I can just use File/Setup py2exe to run it from within the IDE).
What is the "ansi": 1 for? Isn't this maybe the cause of your problem for the encoding?
BTW, I can run py2exe on it and it runs both on my Vista and my Win2K machine (which has no development tools at all as it is my test machine.
Werner
Hi Jorma,
Jorma Paavola wrote:
Hi Werner !
I found out, that Boa 0.4.4 from Sourceforge wount work and I replaced it by 0.5.2 version from CVS.
Yes, wxPython 2.7.x and 2.8.x need the CVS version of Boa.
Werner
It works fine - thanks a lot !
I listed 3 questions on my right previous Email - waiting for your comments/reply...
Jorma
Werner F. Bruhin kirjoitti:
Hi Jorma,
Jorma Paavola wrote:
Hi Werner,
Hereby I submit my used GUItest.py and setup.py , which don´t 'compile' on Win2k (ANSI) the proper .exe-file to run in Win98 environement(generates Traceback as sent before).
Could you see any essential reason in my setup.py used or something else ... ??
Your p2e_test.py by standard should be called setup.py (nice things happen then in e.g. Boa, I can just use File/Setup py2exe to run it from within the IDE).
What is the "ansi": 1 for? Isn't this maybe the cause of your problem for the encoding?
BTW, I can run py2exe on it and it runs both on my Vista and my Win2K machine (which has no development tools at all as it is my test machine.
Werner
---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwidgets.org
For additional commands, e-mail: wxPython-users-help@lists.wxwidgets.org
Hi Jorma,
Jorma Paavola wrote:
Werner F. Bruhin kirjoitti:
Hi Jorma,
Jorma Paavola wrote:
Hi Werner,
Hereby I submit my used GUItest.py and setup.py , which don´t 'compile' on Win2k (ANSI) the proper .exe-file to run in Win98 environement(generates Traceback as sent before).
Could you see any essential reason in my setup.py used or something else ... ??
Your p2e_test.py by standard should be called setup.py (nice things happen then in e.g. Boa, I can just use File/Setup py2exe to run it from within the IDE).
What is the "ansi": 1 for? Isn't this maybe the cause of your problem for the encoding?
BTW, I can run py2exe on it and it runs both on my Vista and my Win2K machine (which has no development tools at all as it is my test machine.
Werner
Hi Werner,
Thanks for good advice for Boa, which looks nice and useful !
(My simple code-samples are made just by IDLE !)I used python "ansi"-version in this case - I have also Unicode-version installed - do you mean that I should try on it as well ?
I don't know what this ansi switch/parameter does, and won't have time to look it up for the moment (as 2.8.4 just got released I am trying to put final touches/tests for my software which will keep me busy for a few days.
I ran my'setup' just from python command prompt(DOS) by (python p2e_test.py) - is that not OK ?
Shouldn't be a problem, I just never use it as I just always work within Boa.
Did you use "ansi"- or "unicode"-version on Vista and Win2k?
I just run your pe2_test.py (after having renamed it to setup.py) from within Boa which on my development machine (Vista) uses the wxPython ansi version. Then I executed the generated .exe file on the Vista machine and did not see any problems, then I copied the GUITest.exe, MSVCR71.dll and w9xpopen.exe to the Win2K machine and executed the .exe and again all worked without problems.
Werner
Hi Wener,
Werner F. Bruhin kirjoitti:
Hi Jorma,
Jorma Paavola wrote:
Werner F. Bruhin kirjoitti:
Hi Jorma,
Jorma Paavola wrote:
Hi Werner,
Hereby I submit my used GUItest.py and setup.py , which don´t 'compile' on Win2k (ANSI) the proper .exe-file to run in Win98 environement(generates Traceback as sent before).
Could you see any essential reason in my setup.py used or something else ... ??
Your p2e_test.py by standard should be called setup.py (nice things happen then in e.g. Boa, I can just use File/Setup py2exe to run it from within the IDE).
What is the "ansi": 1 for? Isn't this maybe the cause of your problem for the encoding?
BTW, I can run py2exe on it and it runs both on my Vista and my Win2K machine (which has no development tools at all as it is my test machine.
Werner
Hi Werner,
Thanks for good advice for Boa, which looks nice and useful !
(My simple code-samples are made just by IDLE !)I used python "ansi"-version in this case - I have also Unicode-version installed - do you mean that I should try on it as well ?
I don't know what this ansi switch/parameter does, and won't have time to look it up for the moment (as 2.8.4 just got released I am trying to put final touches/tests for my software which will keep me busy for a few days.
I ran my'setup' just from python command prompt(DOS) by (python p2e_test.py) - is that not OK ?
Shouldn't be a problem, I just never use it as I just always work within Boa.
Did you use "ansi"- or "unicode"-version on Vista and Win2k?
I just run your pe2_test.py (after having renamed it to setup.py) from within Boa which on my development machine (Vista) uses the wxPython ansi version. Then I executed the generated .exe file on the Vista machine and did not see any problems, then I copied the GUITest.exe, MSVCR71.dll and w9xpopen.exe to the Win2K machine and executed the .exe and again all worked without problems.
Werner
I had today some more time to study the problematics on Win98 using Boa on Win2k by generating various TestGUI´s(.exe-file) with py2exe :
The plain facts on win98 are:
- python ansi/unicode version has nothing to do with the problematics !
- lack of resources has nothing to do with the problematics !
- so GcCollect has neither no influence !
BUT I have found from win98-environment one depending factor: "bundle_files" option used in setup (in win2k) !
If "bundle_files" <= 2 in setup, py2exe generates 3-4 files on dist-folder. When try´ing to run generated .exe-file from dist-folder on win98 problems are coming ...
If "bundle_files" > 2 or don´t exist, py2exe generates more than 10 files on dist-folder. Generated .exe-file runs from dist-folder on win98 fully perfectly ! (even without GcCollect !!)
My intension is to "pack" everything necessary on one single executive whenever possible without using extra wrapping-sw´s !
Therefore I now suspect, that "packing" of files with py2exe
obviously don´t fit for use on Win98 !!? - So Summa Summarum: There is possible a version conflict between py2xe and win98 !??
What is your opinion ?
Do you see, that "bundle_files"-argument should be avoided and just wrap the files together to allow them to run on all Win´s ?
Regards,
Jorma Paavola
Hello,
Jorma Paavola said the following on 17.05.2007 17:34:
My intension is to "pack" everything necessary on one single executive whenever possible without using extra wrapping-sw´s !
You could try something like this:
http://www.py2exe.org/index.cgi/SingleFileExecutable
Therefore I now suspect, that "packing" of files with py2exe
obviously don´t fit for use on Win98 !!? - So Summa Summarum: There is possible a version conflict between py2xe and win98 !??
Yes, I can confirm this.
--
Oleg
Hi Jorma,
Jorma Paavola wrote:
...
I had today some more time to study the problematics on Win98 using Boa on Win2k by generating various TestGUI´s(.exe-file) with py2exe :The plain facts on win98 are:
- python ansi/unicode version has nothing to do with the problematics !
- lack of resources has nothing to do with the problematics !
- so GcCollect has neither no influence !
The resource problem you will only run in on an application which uses many more widgets.
BUT I have found from win98-environment one depending factor: "bundle_files" option used in setup (in win2k) !
If "bundle_files" <= 2 in setup, py2exe generates 3-4 files on dist-folder. When try´ing to run generated .exe-file from dist-folder on win98 problems are coming ...
If "bundle_files" > 2 or don´t exist, py2exe generates more than 10 files on dist-folder. Generated .exe-file runs from dist-folder on win98 fully perfectly ! (even without GcCollect !!)
My intension is to "pack" everything necessary on one single executive whenever possible without using extra wrapping-sw´s !
Therefore I now suspect, that "packing" of files with py2exe
obviously don´t fit for use on Win98 !!? - So Summa Summarum: There is possible a version conflict between py2xe and win98 !??What is your opinion ?
Do you see, that "bundle_files"-argument should be avoided and just wrap the files together to allow them to run on all Win´s ?
I never used the bundle options nor did I try to create the single file option Oleg is mentioning. My app includes a database and some other files which can't be bundled. I distribute it with InnoSetup, which works fine for me.
As Oleg confirmed there is some issue with py2exe bundle option when running on win98. So, maybe try out the link he mentioned and in worst case you can always use something like InnoSetup to deliver a single .exe installer which then puts all the different files needed for your application in the appropriate folders.
Werner
Werner F. Bruhin kirjoitti:
Hi Jorma,
Jorma Paavola wrote:
...
I had today some more time to study the problematics on Win98 using Boa on Win2k by generating various TestGUI´s(.exe-file) with py2exe :The plain facts on win98 are:
- python ansi/unicode version has nothing to do with the problematics !
- lack of resources has nothing to do with the problematics !
- so GcCollect has neither no influence !The resource problem you will only run in on an application which uses many more widgets.
BUT I have found from win98-environment one depending factor: "bundle_files" option used in setup (in win2k) !
If "bundle_files" <= 2 in setup, py2exe generates 3-4 files on dist-folder. When try´ing to run generated .exe-file from dist-folder on win98 problems are coming ...
If "bundle_files" > 2 or don´t exist, py2exe generates more than 10 files on dist-folder. Generated .exe-file runs from dist-folder on win98 fully perfectly ! (even without GcCollect !!)
My intension is to "pack" everything necessary on one single executive whenever possible without using extra wrapping-sw´s !
Therefore I now suspect, that "packing" of files with py2exe
obviously don´t fit for use on Win98 !!? - So Summa Summarum: There is possible a version conflict between py2xe and win98 !??What is your opinion ?
Do you see, that "bundle_files"-argument should be avoided and just wrap the files together to allow them to run on all Win´s ?
I never used the bundle options nor did I try to create the single file option Oleg is mentioning. My app includes a database and some other files which can't be bundled. I distribute it with InnoSetup, which works fine for me.
As Oleg confirmed there is some issue with py2exe bundle option when running on win98. So, maybe try out the link he mentioned and in worst case you can always use something like InnoSetup to deliver a single .exe installer which then puts all the different files needed for your application in the appropriate folders.
Werner
Hi Werner,
Good news:
- I am pleased to confirm, that my original TestGui(.exe)(even without GcCollect)generated on Win2k(without bundle-option) worked today exellent on Me and Vista as well , propably also on Xp !! (without any tracebacks as earlier on all Win´s!)
- so all this mess means, that there must be A GENERAL BUG in "bundle_files"-option of py2exe!!! - not only on win98 ! (Should somebody contact developers concerning issue... ?)
I have used InnoSetup earlier, which normally works fine - NSIS mentioned by Oleg looks interesting due Temp-file-philosophy - I´ll certainly try it.
Thanks a lot for your practical advices, which strenthened my trust on continue my sw-dev on Python.
Best regards,
Jorma
Oleg Deribas kirjoitti:
Hello,
Jorma Paavola said the following on 17.05.2007 17:34:
My intension is to "pack" everything necessary on one single executive whenever possible without using extra wrapping-sw´s !
You could try something like this:
SingleFileExecutable - py2exe.orgTherefore I now suspect, that "packing" of files with py2exe
obviously don´t fit for use on Win98 !!? - So Summa Summarum: There is possible a version conflict between py2xe and win98 !??Yes, I can confirm this.
Hi Oleg,
Thanks a lot of your wrote, which gave me more trust to test my TestGUI(.exe)(generated now without "bundle"-option) on other 'clean' OS´s - it ran today perfectly on all of them !!
Earlier I could run it on my development PC (Win2k) only without problems!
Unfortunately I used "bundle"-option from very beginning with my TestGUI and luckily you were the first one, who confirmed my suspection of possible version/platform conflict - thanks a lot !
I´ll test NSIS, which could fit better to my purposes as InnoSetup more used.
regards,
Jorma
"DON´T USE BUNDLE-OPTION" ... "DON´T USE ..." ......
Hi Jorma,
Jorma Paavola wrote:
...
Hi Werner,Good news:
- I am pleased to confirm, that my original TestGui(.exe)(even without GcCollect)generated on Win2k(without bundle-option) worked today exellent on Me and Vista as well , propably also on Xp !! (without any tracebacks as earlier on all Win´s!)
- so all this mess means, that there must be A GENERAL BUG in "bundle_files"-option of py2exe!!! - not only on win98 ! (Should somebody contact developers concerning issue... ?)
Yes, I would check the py2exe list if it is not already reported and if not then report it with as much detail as possible.
Werner
Werner F. Bruhin kirjoitti:
Hi Jorma,
Jorma Paavola wrote:
...
Hi Werner,Good news:
- I am pleased to confirm, that my original TestGui(.exe)(even without GcCollect)generated on Win2k(without bundle-option) worked today exellent on Me and Vista as well , propably also on Xp !! (without any tracebacks as earlier on all Win´s!)
- so all this mess means, that there must be A GENERAL BUG in "bundle_files"-option of py2exe!!! - not only on win98 ! (Should somebody contact developers concerning issue... ?)Yes, I would check the py2exe list if it is not already reported and if not then report it with as much detail as possible.
Werner
Hi Werner,
I also checked my Runtime-environment on my development PC (Win2k) by running my TestGUI(.exe)with "Dependency Walker" and got the following dynamic module warnings:
GetProcAddress(0x7C570000 [KERNEL32.DLL], "FlsAlloc") called from "MSVCR71.DLL" at address 0x7C341950 and returned NULL. Error: The specified procedure could not be found (127).
GetProcAddress(0x7C570000 [KERNEL32.DLL], "FlsGetValue") called from "MSVCR71.DLL" at address 0x7C34195D and returned NULL. Error: The specified procedure could not be found (127).
GetProcAddress(0x7C570000 [KERNEL32.DLL], "FlsSetValue") called from "MSVCR71.DLL" at address 0x7C34196A and returned NULL. Error: The specified procedure could not be found (127).
GetProcAddress(0x7C570000 [KERNEL32.DLL], "FlsFree") called from "MSVCR71.DLL" at address 0x7C341977 and returned NULL. Error: The specified procedure could not be found (127)
GetProcAddress(0x7C570000 [KERNEL32.DLL], "IsTNT") called from "OLEAUT32.DLL" at address 0x77A23F12 and returned NULL. Error: The specified procedure could not be found (127).
My philosophy is sustain automatically "up/dawnwards"-compatibility of sw´s on all Win´s whenever possible and therefore I selected "a middle class" PC as development-platform.
There is of course a risk, that a part of (Python)-modules used are made on higher level of Win´s/Motherboard/Processor, which don´t fully fit with my "middle class"-environment.
According to the documentation founded the listed warnings are possible not very critical and just may relate to version/processor-incompabilities.
What is your opinion ?
I also found one surprising fact, that quite many modules loaded generated by python are without a proper checksum ??!
Is that typical with python ?
regards,
Jorma
Werner F. Bruhin kirjoitti:
Hi Jorma,
Jorma Paavola wrote:
...
Hi Werner,Good news:
- I am pleased to confirm, that my original TestGui(.exe)(even without GcCollect)generated on Win2k(without bundle-option) worked today exellent on Me and Vista as well , propably also on Xp !! (without any tracebacks as earlier on all Win´s!)
- so all this mess means, that there must be A GENERAL BUG in "bundle_files"-option of py2exe!!! - not only on win98 ! (Should somebody contact developers concerning issue... ?)Yes, I would check the py2exe list if it is not already reported and if not then report it with as much detail as possible.
Werner
Hi Werner,
I ran my TestGUI also on win98-environment with "Dependency Walker" and got similar warnings:
GetProcAddress(0x7C570000 [KERNEL32.DLL], "FlsAlloc") called from "MSVCR71.DLL" at address 0x7C341950 and returned NULL. Error: The specified procedure could not be found (127).
GetProcAddress(0x7C570000 [KERNEL32.DLL], "FlsGetValue") called from "MSVCR71.DLL" at address 0x7C34195D and returned NULL. Error: The specified procedure could not be found (127).
GetProcAddress(0x7C570000 [KERNEL32.DLL], "FlsSetValue") called from "MSVCR71.DLL" at address 0x7C34196A and returned NULL. Error: The specified procedure could not be found (127).
GetProcAddress(0x7C570000 [KERNEL32.DLL], "FlsFree") called from "MSVCR71.DLL" at address 0x7C341977 and returned NULL. Error: The specified procedure could not be found (127)
GetProcAddress(0x7C570000 [KERNEL32.DLL], "IsTNT") called from "OLEAUT32.DLL" at address 0x77A23F12 and returned NULL. Error: The specified procedure could not be found (127).
Also one missing file was claimed (as on Win2k): "APPHELP.DLL" (TestGui ran OK in despite of that!)
According to my knowledge this file dependency is a bug generated on Win2k related to Python-sw's constructor, because that file belongs to XP-environment only and causes error when added to Win2k, 98 or 95 !!
On Win2k, 98 and 95 the correct , related file is called "SHLWAPI.DLL" !
The "Procedure"-errors above are appearing just at the beginning after first USERcall and make me even more suspious, that they are possible related to bugs in some Python-modules due their obvious origin on Xp-environment !
(I don't know, wich module:Python 2.5, wxPython 2.8.3.0 or py2exe 0.6.6 ?)
Your comments were appreciated !
Best regards,
Jorma
Jorma Paavola wrote:
Werner F. Bruhin kirjoitti:
Hi Jorma,
Jorma Paavola wrote:
...
Hi Werner,Good news:
- I am pleased to confirm, that my original TestGui(.exe)(even without GcCollect)generated on Win2k(without bundle-option) worked today exellent on Me and Vista as well , propably also on Xp !! (without any tracebacks as earlier on all Win´s!)
- so all this mess means, that there must be A GENERAL BUG in "bundle_files"-option of py2exe!!! - not only on win98 ! (Should somebody contact developers concerning issue... ?)Yes, I would check the py2exe list if it is not already reported and if not then report it with as much detail as possible.
Werner
Hi Werner,
I ran my TestGUI also on win98-environment with "Dependency Walker" and got similar warnings:
GetProcAddress(0x7C570000 [KERNEL32.DLL], "FlsAlloc") called from "MSVCR71.DLL" at address 0x7C341950 and returned NULL. Error: The specified procedure could not be found (127).
GetProcAddress(0x7C570000 [KERNEL32.DLL], "FlsGetValue") called from "MSVCR71.DLL" at address 0x7C34195D and returned NULL. Error: The specified procedure could not be found (127).
GetProcAddress(0x7C570000 [KERNEL32.DLL], "FlsSetValue") called from "MSVCR71.DLL" at address 0x7C34196A and returned NULL. Error: The specified procedure could not be found (127).
GetProcAddress(0x7C570000 [KERNEL32.DLL], "FlsFree") called from "MSVCR71.DLL" at address 0x7C341977 and returned NULL. Error: The specified procedure could not be found (127)
GetProcAddress(0x7C570000 [KERNEL32.DLL], "IsTNT") called from "OLEAUT32.DLL" at address 0x77A23F12 and returned NULL. Error: The specified procedure could not be found (127).Also one missing file was claimed (as on Win2k): "APPHELP.DLL" (TestGui ran OK in despite of that!)
These are harmless. The GetProcAddress is how the MS DLL is dynamically testing at runtime if certain functionality is available on the system in other DLLs so it can work around it being missing if needed. Same thing with the missing DLL, they are loaded dynamically on demand at runtime, but if they are never needed (because the functions using them are never called) then they are never loaded and so there is no problem. All of this happens inside the MS DLLs and is completely hidden from us at the Python level.
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!
Hi Jorma,
Jorma Paavola wrote:
...
I ran my TestGUI also on win98-environment with "Dependency Walker" and got similar warnings:GetProcAddress(0x7C570000 [KERNEL32.DLL], "FlsAlloc") called from "MSVCR71.DLL" at address 0x7C341950 and returned NULL. Error: The specified procedure could not be found (127).
GetProcAddress(0x7C570000 [KERNEL32.DLL], "FlsGetValue") called from "MSVCR71.DLL" at address 0x7C34195D and returned NULL. Error: The specified procedure could not be found (127).
GetProcAddress(0x7C570000 [KERNEL32.DLL], "FlsSetValue") called from "MSVCR71.DLL" at address 0x7C34196A and returned NULL. Error: The specified procedure could not be found (127).
GetProcAddress(0x7C570000 [KERNEL32.DLL], "FlsFree") called from "MSVCR71.DLL" at address 0x7C341977 and returned NULL. Error: The specified procedure could not be found (127)
GetProcAddress(0x7C570000 [KERNEL32.DLL], "IsTNT") called from "OLEAUT32.DLL" at address 0x77A23F12 and returned NULL. Error: The specified procedure could not be found (127).
Can't help on this, this is too technical for me.
Also one missing file was claimed (as on Win2k): "APPHELP.DLL" (TestGui ran OK in despite of that!)
According to my knowledge this file dependency is a bug generated on Win2k related to Python-sw's constructor, because that file belongs to XP-environment only and causes error when added to Win2k, 98 or 95 !!
On Win2k, 98 and 95 the correct , related file is called "SHLWAPI.DLL" !
The "Procedure"-errors above are appearing just at the beginning after first USERcall and make me even more suspious, that they are possible related to bugs in some Python-modules due their obvious origin on Xp-environment !
(I don't know, wich module:Python 2.5, wxPython 2.8.3.0 or py2exe 0.6.6 ?)Your comments were appreciated !
Hopefully someone else can you help with this.
Werner