Publish as EXE - Introduction

[TrashcanPatrol]

Hmm it works when I try to run just the script posted here... just not when I try to put it into my own script

[moooh]

I'm just going to slide into this conversation and add my problem with publishing instead of making a new topic.

I'm using the module xml.dom.minidom but when I publish an exe and try to run it on an other computer, the exe is unable to find this module. The publish as exe wizard found a dependancy for minicompat.pyc but having it included does not change anything.

I noticed that the minidom.py didn't have it's own .pyc file so I tried manually compiling one and included in the list of dependencies. This didn't change anything either.

Being fairly new to Python I'm not entirely sure how the structuring works for the .pyc-files.
The minidom is importing other modules from the xml.dom namespace, do I need to create .pyc files for all of those as well? Or are they recursively bundled toghether inside the minidom.pyc?

[farshizzo]

Using the xml.dom.minidom module in a published exe works fine for me. Can you publish the following script to an exe?

import viz
viz.go()

import xml.dom.minidom

[moooh]

No that one fails as well.

Traceback (most recent call last):
  File "<string>", line 11, in ?
  File "testfile.py", line 4, in ?
      import xml.dom.minidom
ImportError: No module named xml.dom.minidom

Note that this is on a computer which do not have neither Python nor Vizard installed. If I publish the same exe and run it from my own system which has Vizard, the exe finds the module. Presumably it also fails to find it in the exe in that case, but has the option of looking up and finding it elsewhere.

[moooh]

Found out anything regarding this?
The dependencies I get when publishing the 3 line script is the following:

viz_python.dll
python24.dll
osgDB.dll
MSVCP71.dll
osg.dll
osgText.dll
osgParticle.dll
MSVCR71.dll
vizcore.dll
Producer.dll
OpenThreadsWin32.dll
transform.dll
osgUtil.dll
codecs.pyc
minidom.pyc
sre_parse.pyc
HTMLDOMImplementation.pyc
traceback.pyc
domreg.pyc
MessageSource.pyc
__init__.pyc
Range.pyc
viz.pyc
dis.pyc
UserDict.pyc
sre_constants.pyc
token.pyc
__init__.pyc
re.pyc
types.pyc
sre_compile.pyc
linecache.pyc
testfile.py
random.pyc
cp1252.pyc
tokenize.pyc
xmlbuilder.pyc
gettext.pyc
stat.pyc
sre.pyc
locale.pyc
vizmat.pyc
inspect.pyc
site.pyc
FtCore.pyc
__init__.pyc
__init__.pyc
DOMImplementation.pyc
aliases.pyc
NodeFilter.pyc
ntpath.pyc
opcode.pyc
minicompat.pyc
os.pyc
copy_reg.pyc
string.pyc
warnings.pyc
copy.pyc
vizact.pyc

Is this the same list that you get for your exe that is working?

[farshizzo]

You probably have another Python installation on your computer that is interfering with the Vizard installation. Run the following script and post the output. If the output contains any directories that are outside the Vizard directory, then that is most likely the problem.

import sys
for p in sys.path:
	print p

[moooh]

Here's what I get. Seems to be the expected normal result, everything is under Vizard.

C:\Program Files\WorldViz\Vizard30\python
C:\Program Files\WorldViz\Vizard30\bin\python24.zip
C:\Program Files\WorldViz\Vizard30\bin\lib
C:\Program Files\WorldViz\Vizard30\bin\DLLs
C:\Program Files\WorldViz\Vizard30\bin\lib\plat-win
C:\Program Files\WorldViz\Vizard30\bin\lib\lib-tk
C:\Program Files\WorldViz\Vizard30\bin
C:\Program Files\WorldViz\Vizard30\bin\lib\site-packages
C:\Program Files\WorldViz\Vizard30\bin\lib\win32

For some reason I seem to have failed to mention that I'm running Vizard under Windows Vista. That may or may not have anything to do with this problem.