From: Michael F. <mi...@pc...> - 2004-12-23 22:40:43
|
I'm writing an application that builds a script and then runs py2exe. (windows xp, Python 2.4 by the way). I call py2exe with the following code : if len(sys.argv) == 1: sys.argv.append("py2exe") # setup can be executed without command line... setup( console=[{ 'script': 'movpy.py', 'icon_resources': [(1, 'py.ico')], # anyone do an icon ? }], version= '0.4.1', description= 'Builds the standalone Python distributions.', name= 'Movable Python', author= 'Michael Foord and Bruno Thoorens', author_email= 'fuz...@vo...', url= 'http://sourceforge.net/projects/movpy', data_files= [('', ['test/test.py', 'test/dummylibrary.py'])], zipfile= 'lib\library.zip', options={ 'py2exe':{ 'dist_dir': 'movpy', # 'excludes': [], # 'packages': [], # 'compressed': '1', # 'optimize': '2', } }, ) See the four commented out lines in the options dictionary ? If I uncomment back in*any* of these, then the program crashes with a ' Memory referenced could not be read' error and dies *completely*. As it stands it builds fine. Regards, Fuzzy http://www.voidspace.org.uk/python/index.shtml -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.289 / Virus Database: 265.6.4 - Release Date: 22/12/04 |
From: Michael F. <mi...@pc...> - 2004-12-29 14:49:32
|
I recently had a problem with trying to add an options dictionary to my py2exe setup from Python 2.4. (See previous message). I've now tried the same code on my work computer with Python 2.3.3 and py2exe 0.5.4 (windows XP). If I have anything beyond the 'dist_dir' in the options directory, py2exe crashes - not a python exception, a proper crash. I've included the full function that is getting called, below. Uncommenting out any of the 'excludes', 'optimize' or 'compressed' options causes a crash. Most annoying. Is it my fault or a problem with py2exe ? def dobuild(): from distutils.core import setup import py2exe import shutil if len(sys.argv) == 1: sys.argv.append("py2exe") # setup can be executed without command line... setup( console=[{ 'script': outfile, 'icon_resources': [(1, 'files/py.ico')], # anyone do an icon ? }], windows = [{ 'script': outfile_win, 'icon_resources': [(1, 'files/py.ico')], # anyone do an icon ? }], version= '0.4.1', description= 'The standalone, portable Python distribution.', name= 'Movable Python', author= 'Michael Foord and Bruno Thoorens', author_email= 'fuz...@vo...', url= 'http://sourceforge.net/projects/movpy', data_files= [('', filelist), ('lib', ['files/customize.py', 'files/syspaths.pth'])], zipfile= 'lib/library.zip', options={ 'py2exe':{ 'dist_dir': 'movpy', # 'excludes': exclude_modules, # 'packages': [], # 'compressed': '1', # 'optimize': '2', } }, ) Regards, Fuzzy http://www.voidspace.org.uk/python/index.shtml |
From: Michael F. <Michael.Foord@NorthamptonJesusCentre.org.uk> - 2005-01-04 11:50:43
|
See my previous email about options causing py2exe to bomb out. =20 The crash occurs *before* the message about 'searching for required modules' is printed. In fact before anything is printed to screen. When run from the command line my script (a glorified setup.py) just exits. When run from IDLE the following message is printed in red (i.e. to sys.stderr) =20 WARNING: Stream <cin> looks suspicious: it lacks a 'fileno' attribute WARNING: Stream <cin> looks suspicious: it lacks a 'mode' attribute WARNING: Stream <cout> looks suspicious: it lacks a 'fileno' attribute WARNING: Stream <cout> looks suspicious: it lacks a 'mode' attribute WARNING: Stream <cerr> looks suspicious: it lacks a 'fileno' attribute WARNING: Stream <cerr> looks suspicious: it lacks a 'mode' attribute =20 As I said, this is for a script that does 3-400 imports - so something may be getting overloaded. (same error (<cout> and <cerr> anyway) when attempting to enter interactive console mode with a program built as a windows program) =20 I get the same error for Python 2.4 and Python 2.3, py2exe 0.5.4. =20 Regards, =20 Fuzzy http://www.voidspace.org.uk/python/index.shtml |
From: Thomas H. <th...@py...> - 2005-01-06 21:00:14
|
"Michael Foord" <Michael.Foord@NorthamptonJesusCentre.org.uk> writes: > See my previous email about options causing py2exe to bomb out. > > > > The crash occurs *before* the message about 'searching for required > modules' is printed. In fact before anything is printed to screen. When > run from the command line my script (a glorified setup.py) just exits. Are you sure that you are not simply importing a module which does a sys.exit() somewhere= > When run from IDLE the following message is printed in red (i.e. to > sys.stderr) > > > > WARNING: Stream <cin> looks suspicious: it lacks a 'fileno' attribute > > WARNING: Stream <cin> looks suspicious: it lacks a 'mode' attribute > > WARNING: Stream <cout> looks suspicious: it lacks a 'fileno' attribute > > WARNING: Stream <cout> looks suspicious: it lacks a 'mode' attribute > > WARNING: Stream <cerr> looks suspicious: it lacks a 'fileno' attribute > > WARNING: Stream <cerr> looks suspicious: it lacks a 'mode' attribute Where are these messages coming from? > As I said, this is for a script that does 3-400 imports - so something > may be getting overloaded. > > (same error (<cout> and <cerr> anyway) when attempting to enter > interactive console mode with a program built as a windows program) |
From: Michael F. <mi...@pc...> - 2005-01-06 23:24:14
|
Thomas Heller wrote: >"Michael Foord" <Michael.Foord@NorthamptonJesusCentre.org.uk> writes: > > > >>See my previous email about options causing py2exe to bomb out. >> >> >> >>The crash occurs *before* the message about 'searching for required >>modules' is printed. In fact before anything is printed to screen. When >>run from the command line my script (a glorified setup.py) just exits. >> >> > >Are you sure that you are not simply importing a module which does a >sys.exit() somewhere= > > > No - it *crashes* with a 'memory cannot be read error'. *Not* a python traceback. It happens after 'running py2exe' is printed but before 'searching for the required modules' is printed. I've been trying to track down where in distutils it happens. I got into the 'Distribution' class before I discovered 'DISTUTILS_DEBUG' and then the whole thing came crashing down !! >>When run from IDLE the following message is printed in red (i.e. to >>sys.stderr) >> >> >> >>WARNING: Stream <cin> looks suspicious: it lacks a 'fileno' attribute >> >>WARNING: Stream <cin> looks suspicious: it lacks a 'mode' attribute >> >>WARNING: Stream <cout> looks suspicious: it lacks a 'fileno' attribute >> >>WARNING: Stream <cout> looks suspicious: it lacks a 'mode' attribute >> >>WARNING: Stream <cerr> looks suspicious: it lacks a 'fileno' attribute >> >>WARNING: Stream <cerr> looks suspicious: it lacks a 'mode' attribute >> >> > >Where are these messages coming from? > > > These messages are printed to sys.stderr. I'm not sure *where* they're coming from. I'll dig deeper into distutils and report the exact point at which it crashes - this may give more clues. Regards, Fuzzy http://www.voidspace.org.uk/python/index.shtml >>As I said, this is for a script that does 3-400 imports - so something >>may be getting overloaded. >> >>(same error (<cout> and <cerr> anyway) when attempting to enter >>interactive console mode with a program built as a windows program) >> >> > > > >------------------------------------------------------- >The SF.Net email is sponsored by: Beat the post-holiday blues >Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. >It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt >_______________________________________________ >Py2exe-users mailing list >Py2...@li... >https://lists.sourceforge.net/lists/listinfo/py2exe-users > > > > > > -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.6.9 - Release Date: 06/01/05 |
From: <sjm...@le...> - 2005-01-07 01:29:51
|
On 6 Jan 2005 at 23:25, Michael Foord wrote: > > > Thomas Heller wrote: > > >"Michael Foord" <Michael.Foord@NorthamptonJesusCentre.org.uk> writes: > > > >>When run from IDLE the following message is printed in red (i.e. to > >>sys.stderr) > >> > >> > >> > >>WARNING: Stream <cin> looks suspicious: it lacks a 'fileno' > >>attribute > >> > >>WARNING: Stream <cin> looks suspicious: it lacks a 'mode' attribute > >> > >>WARNING: Stream <cout> looks suspicious: it lacks a 'fileno' > >>attribute > >> > >>WARNING: Stream <cout> looks suspicious: it lacks a 'mode' attribute > >> > >>WARNING: Stream <cerr> looks suspicious: it lacks a 'fileno' > >>attribute > >> > >>WARNING: Stream <cerr> looks suspicious: it lacks a 'mode' attribute > >> > >> > > > >Where are these messages coming from? > > > > > > > > These messages are printed to sys.stderr. I'm not sure *where* they're > coming from. IPython, in module genutils.py And the red colour is (of course(?)) from the readline gadget. HTH, John |
From: Thomas H. <th...@py...> - 2004-12-30 18:50:51
|
Michael Foord <mi...@pc...> writes: > I'm writing an application that builds a script and then runs > py2exe. (windows xp, Python 2.4 by the way). > > I call py2exe with the following code : [a fairly usual setup script] > See the four commented out lines in the options dictionary ? If I > uncomment back in*any* of these, then the program crashes with a ' > Memory referenced could not be read' error and dies *completely*. As > it stands it builds fine. Needless to say, it works for me, with some dummy modules, and some icon. Where does the crash occur - any more information? Thomas |
From: Michael F. <mi...@pc...> - 2004-12-30 22:54:34
|
Hello Thomas, Thanks for your reply. I'm getting the same behaviour for Python 2.3 *and* Python 2.4 (two different machines, both with windows XP). This leads me to suspect it is a genuine issue and not a peculiarity of my setup. I need to run it again and report to you the exact point at which it crashes - but I'm pretty sure it's when it switches to 'py2exe is searching for modules' (or whatever ?). One thing that is odd about this script is that it has a *minimum* of about 300 import statements in it. Is it possible this causes the problem ? If you can be bothered you can download the script (460k because it includes the microsoft VC 7 dlls) and just run 'PyDistFreeze.py'. This will confirm whether you can duplicate the problem. The url is : http://www.voidspace.org.uk/cgi-bin/voidspace/downman.py?file=testenv.zip (I think - if not http://www.voidspace.org.uk/atlantibots/pythonutils.html#testenv ) It isn't quite the latest version - but it's not bad. I quite understand if you don't have time for this anyway and will report back with the exact point the crash occurs. Regards, Fuzzy http://www.voidspace.org.uk/python/index.shtml Thomas Heller wrote: >Michael Foord <mi...@pc...> writes: > > > >>I'm writing an application that builds a script and then runs >>py2exe. (windows xp, Python 2.4 by the way). >> >>I call py2exe with the following code : >> >> >[a fairly usual setup script] > > > >>See the four commented out lines in the options dictionary ? If I >>uncomment back in*any* of these, then the program crashes with a ' >>Memory referenced could not be read' error and dies *completely*. As >>it stands it builds fine. >> >> > >Needless to say, it works for me, with some dummy modules, and some >icon. Where does the crash occur - any more information? > >Thomas > > > > > > > -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.298 / Virus Database: 265.6.7 - Release Date: 30/12/04 |