A weird error when i use ppackage to make (wow) packages for my p3d app.
my .pdef …
from pandac.PandaModules import Filename
packager.setHost("http://localhost/bb/")
class bbGMaker (package):
module('babilonia.guimaker.*')
The error message tells…
:Packager: Reading bbGMaker.pdef
couldn't import babilonia.guimaker
couldn't import babilonia
Traceback (most recent call last):
File "C:\panda3d-1.7.0\built_cmu\direct\showbase\Messenger.py", line 352, in __taskChainDispatch
File "C:\panda3d-1.7.0\built_cmu\direct\showbase\Messenger.py", line 410, in __dispatch
File "C:\panda3d-1.7.0\built_cmu\direct\p3d\AppRunner.py", line 493, in __startIfReady
File "VFSImporter", line 153, in load_module
File "/root/pandaworker/panda3d-1.7.0/built_cmu/direct/p3d/ppackage.py", line 200, in <module>
File "/root/pandaworker/panda3d-1.7.0/built_cmu/direct/p3d/Packager.py", line 2245, in readPackageDef
File "/root/pandaworker/panda3d-1.7.0/built_cmu/direct/p3d/Packager.py", line 2270, in __evalFunc
File "/root/pandaworker/panda3d-1.7.0/built_cmu/direct/p3d/Packager.py", line 2703, in do_module
File "/root/pandaworker/panda3d-1.7.0/built_cmu/direct/p3d/Packager.py", line 2713, in addModule
File "C:\panda3d-1.7.0\built_cmu\direct\showutil\FreezeTool.py", line 770, in addModule
File "C:\panda3d-1.7.0\built_cmu\direct\showutil\FreezeTool.py", line 701, in getModuleStar
File "C:\panda3d-1.7.0\built_cmu\direct\showutil\FreezeTool.py", line 671, in getModulePath
ImportError: No module named babilonia
no module named babilonia! but babilonia is in the pythonpath, in sys.path and i can access it in every python code i got
Whatta Hell ?
What is babilonia, specifically? Is it a directory containing an init.py file, is it a babilonia.py file, or is it a babilonia.pyd file, or is it something else altogether?
For testing purposes i copy babilonia to same folder where pdefs files in. ppackage runs smooth, my packages are imported fine, everybody is in peace in Camelot and in p3dapp. But weird still in the air…
Of course someone cant see somebody in the paths … but i have no idea…
Remember that ppackage runs its own version of Python, and it may not read your PYTHONPATH variable. What do you see if you print sys.path within your pdef file?