You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(7) |
Jun
(31) |
Jul
(50) |
Aug
(79) |
Sep
(45) |
Oct
(41) |
Nov
(56) |
Dec
(103) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2005 |
Jan
(75) |
Feb
(37) |
Mar
(40) |
Apr
(41) |
May
(91) |
Jun
(41) |
Jul
(38) |
Aug
(48) |
Sep
(146) |
Oct
(98) |
Nov
(65) |
Dec
(64) |
2006 |
Jan
(40) |
Feb
(123) |
Mar
(57) |
Apr
(69) |
May
(49) |
Jun
(51) |
Jul
(50) |
Aug
(103) |
Sep
(89) |
Oct
(23) |
Nov
(73) |
Dec
(63) |
2007 |
Jan
(74) |
Feb
(76) |
Mar
(40) |
Apr
(46) |
May
(97) |
Jun
(45) |
Jul
(57) |
Aug
(74) |
Sep
(42) |
Oct
(15) |
Nov
(63) |
Dec
(10) |
2008 |
Jan
(40) |
Feb
(40) |
Mar
(25) |
Apr
(51) |
May
(34) |
Jun
(70) |
Jul
(52) |
Aug
(55) |
Sep
(44) |
Oct
(66) |
Nov
(44) |
Dec
(42) |
2009 |
Jan
(26) |
Feb
(32) |
Mar
(40) |
Apr
(81) |
May
(44) |
Jun
(49) |
Jul
(45) |
Aug
(58) |
Sep
(23) |
Oct
(62) |
Nov
(40) |
Dec
(48) |
2010 |
Jan
(24) |
Feb
(74) |
Mar
(62) |
Apr
(31) |
May
(42) |
Jun
(24) |
Jul
(39) |
Aug
(61) |
Sep
(21) |
Oct
(24) |
Nov
(26) |
Dec
(41) |
2011 |
Jan
(27) |
Feb
(27) |
Mar
(45) |
Apr
(15) |
May
(13) |
Jun
(26) |
Jul
(20) |
Aug
(52) |
Sep
(11) |
Oct
(32) |
Nov
(5) |
Dec
(5) |
2012 |
Jan
(7) |
Feb
(21) |
Mar
(2) |
Apr
(5) |
May
(9) |
Jun
|
Jul
(14) |
Aug
(20) |
Sep
(5) |
Oct
(8) |
Nov
(11) |
Dec
(4) |
2013 |
Jan
(7) |
Feb
(9) |
Mar
(8) |
Apr
(7) |
May
(22) |
Jun
(7) |
Jul
(4) |
Aug
(10) |
Sep
(7) |
Oct
(1) |
Nov
(17) |
Dec
(2) |
2014 |
Jan
(4) |
Feb
(2) |
Mar
(6) |
Apr
(6) |
May
(15) |
Jun
|
Jul
(9) |
Aug
(7) |
Sep
(21) |
Oct
(13) |
Nov
|
Dec
(2) |
2015 |
Jan
(5) |
Feb
|
Mar
(11) |
Apr
(3) |
May
(9) |
Jun
(5) |
Jul
(2) |
Aug
(2) |
Sep
(8) |
Oct
(9) |
Nov
(6) |
Dec
(1) |
2016 |
Jan
|
Feb
(5) |
Mar
(32) |
Apr
|
May
|
Jun
(10) |
Jul
(2) |
Aug
|
Sep
(5) |
Oct
(7) |
Nov
(3) |
Dec
|
2017 |
Jan
(5) |
Feb
|
Mar
(1) |
Apr
(1) |
May
(5) |
Jun
(1) |
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
(1) |
2018 |
Jan
|
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2019 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2020 |
Jan
(2) |
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
2021 |
Jan
|
Feb
(5) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
From: Jeremy K. <jer...@gm...> - 2016-03-09 04:38:44
|
Ok. Here is a little script to see what imports are required for a given module: # -- begin -- import sys initial = set(sys.modules) # change this import as needed for testing import numpy.core.multiarray # determine which modules have been added by the import statement loaded = set(sys.modules) - initial # remove "placeholder" modules loaded -= set(name for name in loaded if sys.modules[name] is None) # remove built-in modules loaded -= set(name for name in loaded if not hasattr(sys.modules[name], '__file__')) # finally, find the extension modules for name in loaded: fn = sys.modules[name].__file__ if fn.lower().endswith('.pyd'): print(fn) # -- end -- Copy/Paste the above into a new .py file and run it with python: python somefile.py The output will be the names of extension modules which are needed by the given import. A quick test locally produces: C:\Python27\lib\site-packages\numpy\random\mtrand.pyd C:\Python27\lib\site-packages\numpy\core\umath.pyd C:\Python27\lib\site-packages\numpy\fft\fftpack_lite.pyd C:\Python27\lib\site-packages\numpy\core\multiarray.pyd C:\Python27\lib\site-packages\numpy\linalg\_umath_linalg.pyd C:\Python27\lib\site-packages\numpy\linalg\lapack_lite.pyd The listed files should exist in the DIST directory of py2exe executable. -- Jeremy Kloth |
From: Sharma, G. <gir...@wu...> - 2016-03-09 04:05:12
|
Sorry Kloth, I used datetime only. While writing to you, I made a mistake. The order in my mainscript is: from Tkinter import * import numpy.core.multiarray import math as ma # maths operations import matplotlib.pyplot as plt # plotting import numpy as np # for arrays from scipy.integrate import ode # for integration if 0: import datetime ________________________________________ From: Jeremy Kloth <jer...@gm...> Sent: Tuesday, March 8, 2016 10:01 PM To: Sharma, Girish Cc: py2...@li... Subject: Re: [Py2exe-users] .exe file working on my computer but not other computers On Tue, Mar 8, 2016 at 8:50 PM, Sharma, Girish <gir...@wu...> wrote: > Hi Kloth, > > The same error persists even after adding 'import time'. The import needed is 'datetime'. -- Jeremy Kloth |
From: Jeremy K. <jer...@gm...> - 2016-03-09 04:01:18
|
On Tue, Mar 8, 2016 at 8:50 PM, Sharma, Girish <gir...@wu...> wrote: > Hi Kloth, > > The same error persists even after adding 'import time'. The import needed is 'datetime'. -- Jeremy Kloth |
From: Sharma, G. <gir...@wu...> - 2016-03-09 03:51:04
|
Hi Kloth, The same error persists even after adding 'import time'. I was just wondering about the Error File "numpy\core\multiarray.pyc", line 10, in __load I do not have the .py file in my system. I just have the multiarray.pyc file which I cannot read. So, do you what exactly is written in line 10, which it is unable to load? Please suggest something. I have spent enormous amount of time in trying to solve this problem. Is it even solvable? What am I missing? - Girish Sharma |
From: Jeremy K. <jer...@gm...> - 2016-03-09 02:47:34
|
On Tue, Mar 8, 2016 at 6:34 PM, Sharma, Girish <gir...@wu...> wrote: > Hi Kloth, > > I think I understand what you mean. Could you please specify where should I add > >>if 0: >> import datetime > > There are three options: > 1. setup.py file > 2. mainscript.py file (I have just one file) > 3. somewhere else (in some .py file in library) In the mainscript.py file usually as it is not needed for the library to operate normally. > Also, where exactly in the file. In the beginning of the imports or somewhere else? Its location is not really that important. But, to keep related things together, I would place it after the other imports in the file. -- Jeremy Kloth |
From: Sharma, G. <gir...@wu...> - 2016-03-09 01:34:31
|
Hi Kloth, I think I understand what you mean. Could you please specify where should I add >if 0: > import datetime There are three options: 1. setup.py file 2. mainscript.py file (I have just one file) 3. somewhere else (in some .py file in library) Also, where exactly in the file. In the beginning of the imports or somewhere else? ________________________________________ From: Jeremy Kloth <jer...@gm...> Sent: Tuesday, March 8, 2016 6:37 PM To: Sharma, Girish Cc: py2...@li... Subject: Re: [Py2exe-users] .exe file working on my computer but not other computers On Tue, Mar 8, 2016 at 11:22 AM, Sharma, Girish <gir...@wu...> wrote: > Dear Massa, > > I understood what you are saying. Thank you for explaining it more clearly > to a newbie. > > To analyse the problem: > - read the file numpy\core\multiarray.py > - check which file is imported in line 10 > > But, > I could not find numpy\core\multiarray.py file in > C:\Anaconda2\Lib\site-packages\numpy\core. Though I found multiarray.pyd > file which I cannot open and see. multiarray.py is a stub file generated by py2exe for loading multiarray.pyd. It will not be found in the normal Python module locations. > which makes your error message rather suspicious. Anyway, multiarray.pyd is > probably the binary file that is missing. Actually, in this case it is a module that is imported *by* multiarray that is missing. > Have you checked if it is copied into the build directory? > > > Build directory has numpy\core\multiarray.pyc file. > Dist directory has numpy\core\multiarray.pyd file. > > import sys > import numpy.core > import numpy.core.mutliarray > As I alluded to above, the multiarray module does imports in C which py2exe cannot discover. The missing import is 'datetime' from the Python standard library. The "trick" used for adding missing modules to py2exe-generated executables is to add an: if 0: import missing_module_1 import missing_module_2 to the main executable that is scanned by the py2exe setup.py. For you, it should be sufficient to add "import datetime" to the forced import block: if 0: import datetime and regenerate the executable. -- Jeremy Kloth |
From: Jeremy K. <jer...@gm...> - 2016-03-09 00:37:08
|
On Tue, Mar 8, 2016 at 11:22 AM, Sharma, Girish <gir...@wu...> wrote: > Dear Massa, > > I understood what you are saying. Thank you for explaining it more clearly > to a newbie. > > To analyse the problem: > - read the file numpy\core\multiarray.py > - check which file is imported in line 10 > > But, > I could not find numpy\core\multiarray.py file in > C:\Anaconda2\Lib\site-packages\numpy\core. Though I found multiarray.pyd > file which I cannot open and see. multiarray.py is a stub file generated by py2exe for loading multiarray.pyd. It will not be found in the normal Python module locations. > which makes your error message rather suspicious. Anyway, multiarray.pyd is > probably the binary file that is missing. Actually, in this case it is a module that is imported *by* multiarray that is missing. > Have you checked if it is copied into the build directory? > > > Build directory has numpy\core\multiarray.pyc file. > Dist directory has numpy\core\multiarray.pyd file. > > import sys > import numpy.core > import numpy.core.mutliarray > As I alluded to above, the multiarray module does imports in C which py2exe cannot discover. The missing import is 'datetime' from the Python standard library. The "trick" used for adding missing modules to py2exe-generated executables is to add an: if 0: import missing_module_1 import missing_module_2 to the main executable that is scanned by the py2exe setup.py. For you, it should be sufficient to add "import datetime" to the forced import block: if 0: import datetime and regenerate the executable. -- Jeremy Kloth |
From: Sharma, G. <gir...@wu...> - 2016-03-08 18:22:58
|
Dear Massa, I understood what you are saying. Thank you for explaining it more clearly to a newbie. To analyse the problem: - read the file numpy\core\multiarray.py - check which file is imported in line 10 But, I could not find numpy\core\multiarray.py file in C:\Anaconda2\Lib\site-packages\numpy\core. Though I found multiarray.pyd file which I cannot open and see. which makes your error message rather suspicious. Anyway, multiarray.pyd is probably the binary file that is missing. Have you checked if it is copied into the build directory? Build directory has numpy\core\multiarray.pyc file. Dist directory has numpy\core\multiarray.pyd file. import sys import numpy.core import numpy.core.mutliarray Anyways, I imported them in my mainscript.py. The exe ran on my computer as usual. But on a different computer, it showed me a bit different error. Traceback (most recent call last): File "Moment_Final.py", line 4, in <module> File "numpy\__init__.pyc", line 180, in <module> File "numpy\add_newdocs.pyc", line 13, in <module> File "numpy\lib\__init__.pyc", line 8, in <module> File "numpy\lib\type_check.pyc", line 11, in <module> File "numpy\core\__init__.pyc", line 14, in <module> File "numpy\core\multiarray.pyc", line 12, in <module> File "numpy\core\multiarray.pyc", line 10, in __load ImportError: DLL load failed: The specified module could not be found. I am really not sure, what exactly am I missing. line 4 of the Moment_Final.py (which is my mainscript.py) is: import numpy.core Please help. |
From: Massa, H. A. <ch...@gh...> - 2016-03-08 18:11:02
|
Jamal, 2016-03-08 18:07 GMT+01:00 Jamal Mazrui <Jam...@fc...>: > Using py2exe configuration options, if an executable is built to be, as > much as possible, a single .exe file, does it create needed components on > disk as temporary files when initially loading? Based on the documentation > of alternatives to py2exe, cx_Freeze and PyInstaller, they create such > temporary files. I am unclear from the documentation of py2exe whether it > does so as well. > py2exe loads the files directly from the single file (or the additional zip-file, when not opting for the single file version). That includes binary files (.pyd, .dll) There is some "load dll from memory code" included with py2exe. No temporary files are spilled to disk. I am distributing these kind of single-file-applications to customers since ~14 years. It is not really single file, as some Micosoft C Runtime files need to be distributed additionally. HOWEVER: when you use Python modules that dynamically create files to import, that may spill stuff out to disk - dynamically created bindings for com-Modules may be that way. Additionally, that "grab all necessary dlls and bundle them in an .exe" can be troublesome, as sometimes to many .dlls are identified as necessary. That takes a quite some research each time Microsoft decides to put out different dependencies in some system areas; and then new lines in the exclude-directive. I felt that pain with every major windows update. Harald -- GHUM GmbH Harald Armin Massa Spielberger Straße 49 70435 Stuttgart 0173/9409607 Amtsgericht Stuttgart, HRB 734971 |
From: Jamal M. <Jam...@fc...> - 2016-03-08 17:41:38
|
Using py2exe configuration options, if an executable is built to be, as much as possible, a single .exe file, does it create needed components on disk as temporary files when initially loading? Based on the documentation of alternatives to py2exe, cx_Freeze and PyInstaller, they create such temporary files. I am unclear from the documentation of py2exe whether it does so as well. I was hoping that components bundled into a py2exe executable are accessed in memory at runtime rather than saved to disk as temporary files, thereby acting more like an executable compiled with other programming languages, even though being considerably larger in size. If that is not the case, however, I wish to be informed accurately. Can anyone shed light on this? Jamal |
From: Massa, H. A. <ch...@gh...> - 2016-03-08 17:07:25
|
Hi Sharma, > Update: > My exe is running on computers which have Anaconda 2.7 64-bit version > installed on their computers. > > yes, because they have multiarray.pyd on their computer. You said: > To analyse the problem: > - read the file numpy\core\multiarray.py > - check which file is imported in line 10 > > But, > I could not find numpy\core\multiarray.py file > in C:\Anaconda2\Lib\site-packages\numpy\core. Though I found multiarray.pyd > file which I cannot open and see. > which makes your error message rather suspicious. Anyway, multiarray.pyd is probably the binary file that is missing. Have you checked if it is copied into the build directory? pyexe builds an exe and a zip; or, if run in the single file mode, just an .exe. That .exe can be "unzipped" by using 7zip. That allows you to check: has multiarray.pyd be included? > > Also, could you please specify that how do I solve the problem using > solution b) by using my_toplevel_file_with_py2exepatches.py: and import > statements. > > IF the check (looking into build directory / checking what is zipped into your .exe / .zip by py2exe) confirms, that mutliarray.pyd is NOT packaged, we have to find a way to get in bundled. The tools used by py2exe aim to find all needed library feels by simulating the imports. As Python is more dynamic than anybody imagines; that may fail. A trick that often works is: explicitly import the file so, in your main script file, add the lines import numpy.core import numpy.core.mutliarray and after doing the setup.py build step, check if mutliarray.pyd is included in the build directory / the zipped up .exe file. best wishes Harald > Traceback (most recent call last): >> File "Moment_Final.py", line 5, in <module> >> File "matplotlib\__init__.pyc", line 122, in <module> >> File "matplotlib\cbook.pyc", line 33, in <module> >> File "numpy\__init__.pyc", line 180, in <module> >> File "numpy\add_newdocs.pyc", line 13, in <module> >> File "numpy\lib\__init__.pyc", line 8, in <module> >> File "numpy\lib\type_check.pyc", line 11, in <module> >> File "numpy\core\__init__.pyc", line 14, in <module> >> File "numpy\core\multiarray.pyc", line 12, in <module> >> File "numpy\core\multiarray.pyc", line 10, in __loadImportError: DLL load failed: The specified module could not be found. >> >> multiarray.py tries to import a file in line 10, most likely a .pyd > That .pyd is for some reasons not included in your distributed exe-file. > > To analyse the problem: > - read the file numpy\core\multiarray.py > - check which file is imported in line 10 > > After finding the name of the file, check your dist-directory if that .pyd > is really missing. > > If that .pyd is missing, you have 2 options: > > a) there is an include-directive in py2exe options; you can try to > explicitly name the .pyd to be included > b) I had good results by explicitly importing files which import .pyd on a > top level, that is > > my_toplevel_file_with_py2exepatches.py: > > import sys > import numpy.core > import numpy.core.multiarray > > More of these tricks you can find on http://py2exe.org/ > <http://py2exe.org/> > FrontPage - py2exe.org <http://py2exe.org/> > py2exe.org > py2exe. py2exe is a Python Distutils extension which converts Python > scripts into executable Windows programs, able to run without requiring a > Python installation. > > > Best wishes > > Harald > > > > > >> >> >> ------------------------------------------------------------------------------ >> Transform Data into Opportunity. >> Accelerate data analysis in your applications with >> Intel Data Analytics Acceleration Library. >> Click to learn more. >> http://makebettercode.com/inteldaal-eval >> _______________________________________________ >> Py2exe-users mailing list >> Py2...@li... >> https://lists.sourceforge.net/lists/listinfo/py2exe-users >> >> > > > -- > > GHUM GmbH > Harald Armin Massa > Spielberger Straße 49 > 70435 Stuttgart > 0173/9409607 > > Amtsgericht Stuttgart, HRB 734971 > > -- GHUM GmbH Harald Armin Massa Spielberger Straße 49 70435 Stuttgart 0173/9409607 Amtsgericht Stuttgart, HRB 734971 |
From: Sharma, G. <gir...@wu...> - 2016-03-08 07:15:55
|
Hi Massa, Thank you for your quick response. I am a newbie to py2exe and a chemical Engineer by profession with little knowledge of computer science. So, please spare me if I do not understand some basics. Update: My exe is running on computers which have Anaconda 2.7 64-bit version installed on their computers. You said: To analyse the problem: - read the file numpy\core\multiarray.py - check which file is imported in line 10 But, I could not find numpy\core\multiarray.py file in C:\Anaconda2\Lib\site-packages\numpy\core. Though I found multiarray.pyd file which I cannot open and see. Also, could you please specify that how do I solve the problem using solution b) by using my_toplevel_file_with_py2exepatches.py: and import statements. ________________________________ From: Massa, Harald Armin <ch...@gh...> Sent: Monday, March 7, 2016 7:19 AM To: Sharma, Girish Cc: py2...@li... Subject: Re: [Py2exe-users] .exe file working on my computer but not other computers Hello Girish, Traceback (most recent call last): File "Moment_Final.py", line 5, in <module> File "matplotlib\__init__.pyc", line 122, in <module> File "matplotlib\cbook.pyc", line 33, in <module> File "numpy\__init__.pyc", line 180, in <module> File "numpy\add_newdocs.pyc", line 13, in <module> File "numpy\lib\__init__.pyc", line 8, in <module> File "numpy\lib\type_check.pyc", line 11, in <module> File "numpy\core\__init__.pyc", line 14, in <module> File "numpy\core\multiarray.pyc", line 12, in <module> File "numpy\core\multiarray.pyc", line 10, in __load ImportError: DLL load failed: The specified module could not be found. multiarray.py tries to import a file in line 10, most likely a .pyd That .pyd is for some reasons not included in your distributed exe-file. To analyse the problem: - read the file numpy\core\multiarray.py - check which file is imported in line 10 After finding the name of the file, check your dist-directory if that .pyd is really missing. If that .pyd is missing, you have 2 options: a) there is an include-directive in py2exe options; you can try to explicitly name the .pyd to be included b) I had good results by explicitly importing files which import .pyd on a top level, that is my_toplevel_file_with_py2exepatches.py: import sys import numpy.core import numpy.core.multiarray More of these tricks you can find on http://py2exe.org/ [http://py2exe.org/pythonlogo.png]<http://py2exe.org/> FrontPage - py2exe.org<http://py2exe.org/> py2exe.org py2exe. py2exe is a Python Distutils extension which converts Python scripts into executable Windows programs, able to run without requiring a Python installation. Best wishes Harald ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval _______________________________________________ Py2exe-users mailing list Py2...@li...<mailto:Py2...@li...> https://lists.sourceforge.net/lists/listinfo/py2exe-users -- GHUM GmbH Harald Armin Massa Spielberger Straße 49 70435 Stuttgart 0173/9409607 Amtsgericht Stuttgart, HRB 734971 |
From: Massa, H. A. <ch...@gh...> - 2016-03-07 13:41:26
|
Hello Girish, Traceback (most recent call last): > File "Moment_Final.py", line 5, in <module> > File "matplotlib\__init__.pyc", line 122, in <module> > File "matplotlib\cbook.pyc", line 33, in <module> > File "numpy\__init__.pyc", line 180, in <module> > File "numpy\add_newdocs.pyc", line 13, in <module> > File "numpy\lib\__init__.pyc", line 8, in <module> > File "numpy\lib\type_check.pyc", line 11, in <module> > File "numpy\core\__init__.pyc", line 14, in <module> > File "numpy\core\multiarray.pyc", line 12, in <module> > File "numpy\core\multiarray.pyc", line 10, in __loadImportError: DLL load failed: The specified module could not be found. > > multiarray.py tries to import a file in line 10, most likely a .pyd That .pyd is for some reasons not included in your distributed exe-file. To analyse the problem: - read the file numpy\core\multiarray.py - check which file is imported in line 10 After finding the name of the file, check your dist-directory if that .pyd is really missing. If that .pyd is missing, you have 2 options: a) there is an include-directive in py2exe options; you can try to explicitly name the .pyd to be included b) I had good results by explicitly importing files which import .pyd on a top level, that is my_toplevel_file_with_py2exepatches.py: import sys import numpy.core import numpy.core.multiarray More of these tricks you can find on http://py2exe.org/ Best wishes Harald > > > ------------------------------------------------------------------------------ > Transform Data into Opportunity. > Accelerate data analysis in your applications with > Intel Data Analytics Acceleration Library. > Click to learn more. > http://makebettercode.com/inteldaal-eval > _______________________________________________ > Py2exe-users mailing list > Py2...@li... > https://lists.sourceforge.net/lists/listinfo/py2exe-users > > -- GHUM GmbH Harald Armin Massa Spielberger Straße 49 70435 Stuttgart 0173/9409607 Amtsgericht Stuttgart, HRB 734971 |
From: Sharma, G. <gir...@wu...> - 2016-03-07 03:27:49
|
Hi all, System: Windows 7 64-bit Anaconda 2.7 64-bit py2exe 64-bit Background: I converted my python code to .exe using py2exe and setup.py file shown below: from distutils.core import setup import py2exe from distutils.filelist import findall import matplotlib opts = {"py2exe": { "packages" : ['matplotlib'], "includes": ['scipy', 'scipy.integrate', 'scipy.special.*','scipy.linalg.*'], 'dll_excludes': ['libgdk-win32-2.0-0.dll', 'libgobject-2.0-0.dll', 'libgdk_pixbuf-2.0-0.dll'] } } setup( windows = [{'script': "with_GUI.py"}], zipfile = None, options= opts, data_files = matplotlib.get_py2exe_datafiles() ) But this gave me some error saying that there was version conflict with two files. So I changed the two files viz. dist/tcl/tcl8.5/init.tcl (in line 19) and dist/tcl/tk8.5/tk.tcl (in line 18). In my case I changed the version from 8.5.15 to 8.5.18. I found the location of the two files by looking at the path specified by the error in error log. Then the .exe worked just fine. Problem: I zipped the dist folder which contains .exe file. Then, I unzipped it on another computer but it is not working there. Following is the error it shows: Traceback (most recent call last): File "Moment_Final.py", line 5, in <module> File "matplotlib\__init__.pyc", line 122, in <module> File "matplotlib\cbook.pyc", line 33, in <module> File "numpy\__init__.pyc", line 180, in <module> File "numpy\add_newdocs.pyc", line 13, in <module> File "numpy\lib\__init__.pyc", line 8, in <module> File "numpy\lib\type_check.pyc", line 11, in <module> File "numpy\core\__init__.pyc", line 14, in <module> File "numpy\core\multiarray.pyc", line 12, in <module> File "numpy\core\multiarray.pyc", line 10, in __load ImportError: DLL load failed: The specified module could not be found. Please guide me what am I missing. |
From: John D. <moo...@gm...> - 2016-03-05 09:33:19
|
You'll have to modify the C code the binary runs on. Most of that should take place in /source/start.c You can look at my fork for a working example. Once you are done with your changes you'll have to build the package from source, then install it. https://github.com/goatpig/py2exe On 3/5/2016 10:26 AM, Gianluca Cantoro wrote: > Hi, > thanks for your suggestion. > How would I have to proceed in order to build with Wide characters? > Thanks > > >> This has to do with the inner workings of the prebuilt binary. It's >> built around A (for ANSI) calls and you need replace them with W (for >> wide char) calls. >>> On 3/3/2016 10:19 AM, Gianluca Cantoro wrote: >>> Dear all, >>> I'm having some troubles with some specific characters in the >>> installation folder. >>> If I convert my script and run it from a simple named folder, say >>> c:\myprogram\myscript.exe, everything works fine. >>> If I put the same script in a folder with other characters, say >>> c:\myprogram\???\myscript.exe, I get the error that the program cannot >>> load python27.dll... and I can assure you that the dll is in that >>> folder. >>> >>> I assume the issue has to do with the "?" symbol in the path but I >>> don't know how to solve it and which file to modify. Perhaps the >>> setup.py file? or should I put something in my scripts' headers? >>> >>> Any help is welcome. >>> Thanks, >>> Gianluca |
From: Gianluca C. <gia...@gm...> - 2016-03-05 09:26:19
|
Hi, thanks for your suggestion. How would I have to proceed in order to build with Wide characters? Thanks > This has to do with the inner workings of the prebuilt binary. It's > built around A (for ANSI) calls and you need replace them with W (for > wide char) calls. >> On 3/3/2016 10:19 AM, Gianluca Cantoro wrote: >> Dear all, >> I'm having some troubles with some specific characters in the >> installation folder. >> If I convert my script and run it from a simple named folder, say >> c:\myprogram\myscript.exe, everything works fine. >> If I put the same script in a folder with other characters, say >> c:\myprogram\???\myscript.exe, I get the error that the program cannot >> load python27.dll... and I can assure you that the dll is in that >> folder. >> >> I assume the issue has to do with the "?" symbol in the path but I >> don't know how to solve it and which file to modify. Perhaps the >> setup.py file? or should I put something in my scripts' headers? >> >> Any help is welcome. >> Thanks, >> Gianluca |
From: LEON H. <le...@bt...> - 2016-03-04 21:28:53
|
Whenever I try to download PY2EXE from Sourceforge I get about 500 kb, and then nothing! I'm using Win 7 x64. Any ideas as to why would be appreciated. Leon Heller G1HSM |
From: Martin L. <lap...@gm...> - 2016-03-04 20:16:26
|
''' Created on Mar 3, 2011 @author: daniel ''' import win32serviceutil import win32event import sys class Launcher(win32serviceutil.ServiceFramework): _svc_name_ = "<insert service name>" _svc_display_name_ = "<insert display name>" def __init__(self, args): win32serviceutil.ServiceFramework.__init__(self, args) self.hWaitStop = win32event.CreateEvent(None, 0, 0, None) def SvcStop(self): sys.stopservice = True def SvcDoRun(self): # Call a Main() like function here, ideally something that will # know to close when the `sys` module gains a 'stopservice' attribute. pass |
From: John D. <moo...@gm...> - 2016-03-03 10:20:41
|
This has to do with the inner workings of the prebuilt binary. It's built around A (for ANSI) calls and you need replace them with W (for wide char) calls. On 3/3/2016 10:19 AM, Gianluca Cantoro wrote: > Dear all, > I'm having some troubles with some specific characters in the > installation folder. > If I convert my script and run it from a simple named folder, say > c:\myprogram\myscript.exe, everything works fine. > If I put the same script in a folder with other characters, say > c:\myprogram\ááá\myscript.exe, I get the error that the program cannot > load python27.dll... and I can assure you that the dll is in that > folder. > > I assume the issue has to do with the "á" symbol in the path but I > don't know how to solve it and which file to modify. Perhaps the > setup.py file? or should I put something in my scripts' headers? > > Any help is welcome. > Thanks, > Gianluca > > ------------------------------------------------------------------------------ > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 > _______________________________________________ > Py2exe-users mailing list > Py2...@li... > https://lists.sourceforge.net/lists/listinfo/py2exe-users |
From: Gianluca C. <gia...@gm...> - 2016-03-03 09:19:46
|
Dear all, I'm having some troubles with some specific characters in the installation folder. If I convert my script and run it from a simple named folder, say c:\myprogram\myscript.exe, everything works fine. If I put the same script in a folder with other characters, say c:\myprogram\ááá\myscript.exe, I get the error that the program cannot load python27.dll... and I can assure you that the dll is in that folder. I assume the issue has to do with the "á" symbol in the path but I don't know how to solve it and which file to modify. Perhaps the setup.py file? or should I put something in my scripts' headers? Any help is welcome. Thanks, Gianluca |
From: Jimmy R. <ji...@re...> - 2016-02-12 09:46:38
|
On Thu, Feb 11, 2016 at 2:38 PM, Gufflet Yves <yve...@or...> wrote: > Mark, did you answer on the basis of the forum link I sent, or do you > know the heart of py2exe ? > I would trust what Mark says about this. He is one of the foremost authorities on Python as it relates to Windows in general, and py2exe in particular. And that's been the case for many years. Only Thomas Heller has contributed more code to py2exe than Mark. His answer also matches my vague memory of things from when I was more deeply familiar with py2exe's inner workings. Jimmy |
From: Mark H. <ski...@gm...> - 2016-02-11 22:54:06
|
On 12/02/2016 9:38 AM, Gufflet Yves wrote: > Thanks Dan and Mark for your answers. > It appears you do not tell the same thing. > Mark, did you answer on the basis of the forum link I sent, or do you > know the heart of py2exe ? It's been quite a few years, but last I recall, py2exe makes no attempt to update the checksum after modifying the executable. A quick google tells me I said the same thing 6 years ago too :) https://sourceforge.net/p/py2exe/mailman/message/24637537/ HTH, Mark > Dan did you check the checksum with depends.exe or did you assume you > had no problem with checksum ? > > Could you check for your executables what it indicates with depends.exe ? > > http://www.dependencywalker.com/ > > Effectively, I am deploying without python installed and I had a lot of > problem to incorporate with a manifest the versions 9.0.21022.8 of > msvcr90.dll (and co). And I thought it was the problem. I used by error > 32 bits version and then 64 bits version. Still do not work and then I > saw it was conflicting with AV. I cannot assume that the person do not > use AV or that an antivirus will not block because of an invalid link > checksum. > > Have you got any idea of a minimal configuration for the build that do > not generate this link checksum ? > > Do you think it is because the dll used at compilation or at runtime are > not the same and that I am still having problem with dll hell or winsws > hell ? > > Any suggestions ? > > Le 11/02/2016 22:08, Mark Hammond a écrit : >> This is due to how py2exe works - it uses a pre-built stub and appends >> data to it without attempting to change any checksums. There's not >> much you can do about that (and probably no value in avast flagging it >> as a problem either - AV software seems to be in a race to the bottom) >> >> Mark >> >> On 12/02/2016 4:31 AM, Gufflet Yves wrote: >>> Hi, >>> >>> I generated an executable with py2exe but it fails to run on my machine >>> when avast is running. >>> I discovered with Dependency Walker that the "link checksum" for the exe >>> is in red and differs from the "real checksum" >>> I am not sure about the origin of the problem (virus or py2exe way of >>> doing things) neither how to fix it (I cannot guaranty that the final >>> user will have avast or not) >>> Any idea ? >>> >>> Thanks in advance, >>> >>> Yves >>> >>> --- >>> L'absence de virus dans ce courrier électronique a été vérifiée par >>> le logiciel antivirus Avast. >>> https://www.avast.com/antivirus >>> >>> >>> ------------------------------------------------------------------------------ >>> >>> Site24x7 APM Insight: Get Deep Visibility into Application Performance >>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >>> Monitor end-to-end web transactions and take corrective actions now >>> Troubleshoot faster and improve end-user experience. Signup Now! >>> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 >>> _______________________________________________ >>> Py2exe-users mailing list >>> Py2...@li... >>> https://lists.sourceforge.net/lists/listinfo/py2exe-users >>> >> >> > > > --- > L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. > https://www.avast.com/antivirus > > > ------------------------------------------------------------------------------ > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 > _______________________________________________ > Py2exe-users mailing list > Py2...@li... > https://lists.sourceforge.net/lists/listinfo/py2exe-users > |
From: Gufflet Y. <yve...@or...> - 2016-02-11 22:39:03
|
Thanks Dan and Mark for your answers. It appears you do not tell the same thing. Mark, did you answer on the basis of the forum link I sent, or do you know the heart of py2exe ? Dan did you check the checksum with depends.exe or did you assume you had no problem with checksum ? Could you check for your executables what it indicates with depends.exe ? http://www.dependencywalker.com/ Effectively, I am deploying without python installed and I had a lot of problem to incorporate with a manifest the versions 9.0.21022.8 of msvcr90.dll (and co). And I thought it was the problem. I used by error 32 bits version and then 64 bits version. Still do not work and then I saw it was conflicting with AV. I cannot assume that the person do not use AV or that an antivirus will not block because of an invalid link checksum. Have you got any idea of a minimal configuration for the build that do not generate this link checksum ? Do you think it is because the dll used at compilation or at runtime are not the same and that I am still having problem with dll hell or winsws hell ? Any suggestions ? Le 11/02/2016 22:08, Mark Hammond a écrit : > This is due to how py2exe works - it uses a pre-built stub and appends > data to it without attempting to change any checksums. There's not > much you can do about that (and probably no value in avast flagging it > as a problem either - AV software seems to be in a race to the bottom) > > Mark > > On 12/02/2016 4:31 AM, Gufflet Yves wrote: >> Hi, >> >> I generated an executable with py2exe but it fails to run on my machine >> when avast is running. >> I discovered with Dependency Walker that the "link checksum" for the exe >> is in red and differs from the "real checksum" >> I am not sure about the origin of the problem (virus or py2exe way of >> doing things) neither how to fix it (I cannot guaranty that the final >> user will have avast or not) >> Any idea ? >> >> Thanks in advance, >> >> Yves >> >> --- >> L'absence de virus dans ce courrier électronique a été vérifiée par >> le logiciel antivirus Avast. >> https://www.avast.com/antivirus >> >> >> ------------------------------------------------------------------------------ >> >> Site24x7 APM Insight: Get Deep Visibility into Application Performance >> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >> Monitor end-to-end web transactions and take corrective actions now >> Troubleshoot faster and improve end-user experience. Signup Now! >> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 >> _______________________________________________ >> Py2exe-users mailing list >> Py2...@li... >> https://lists.sourceforge.net/lists/listinfo/py2exe-users >> > > --- L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. https://www.avast.com/antivirus |
From: Mark H. <ski...@gm...> - 2016-02-11 21:09:16
|
This is due to how py2exe works - it uses a pre-built stub and appends data to it without attempting to change any checksums. There's not much you can do about that (and probably no value in avast flagging it as a problem either - AV software seems to be in a race to the bottom) Mark On 12/02/2016 4:31 AM, Gufflet Yves wrote: > Hi, > > I generated an executable with py2exe but it fails to run on my machine > when avast is running. > I discovered with Dependency Walker that the "link checksum" for the exe > is in red and differs from the "real checksum" > I am not sure about the origin of the problem (virus or py2exe way of > doing things) neither how to fix it (I cannot guaranty that the final > user will have avast or not) > Any idea ? > > Thanks in advance, > > Yves > > --- > L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. > https://www.avast.com/antivirus > > > ------------------------------------------------------------------------------ > Site24x7 APM Insight: Get Deep Visibility into Application Performance > APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month > Monitor end-to-end web transactions and take corrective actions now > Troubleshoot faster and improve end-user experience. Signup Now! > http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 > _______________________________________________ > Py2exe-users mailing list > Py2...@li... > https://lists.sourceforge.net/lists/listinfo/py2exe-users > |
From: Gufflet Y. <yve...@or...> - 2016-02-11 17:31:30
|
Hi, I generated an executable with py2exe but it fails to run on my machine when avast is running. I discovered with Dependency Walker that the "link checksum" for the exe is in red and differs from the "real checksum" I am not sure about the origin of the problem (virus or py2exe way of doing things) neither how to fix it (I cannot guaranty that the final user will have avast or not) Any idea ? Thanks in advance, Yves --- L'absence de virus dans ce courrier électronique a été vérifiée par le logiciel antivirus Avast. https://www.avast.com/antivirus |