On Tue, 11 Dec 2007, Reid Ellis wrote:

Has anyone else had any problem running a debug Chandler under Leopard? From a clean checkout and "make DEBUG=1 install" I keep getting a traceback:

Traceback (most recent call last):
File "Chandler.py", line 21, in <module>
  from application import Globals, Utility
File "/Users/rae/work/osaf/chandler/chandler/application/Globals.py", line 24, in <module>
  from application.Utility import initDefaults
File "/Users/rae/work/osaf/chandler/chandler/application/Utility.py", line 20, in <module>
  import i18n, schema, itertools
File "/Users/rae/work/osaf/chandler/chandler/i18n/__init__.py", line 16, in <module>
  from i18nmanager import I18nManager, I18nException
File "/Users/rae/work/osaf/chandler/chandler/i18n/i18nmanager.py", line 17, in <module> from egg_translations import EggTranslations, hasCountryCode, stripCountryCode
ImportError: No module named egg_translations

When running on Leopard (or any other OS where we do only partial builds because we use the system's python) you need to be sure that there is only one site-packages directory in your release tree and that it is the correct one.

For Leopard (and any other partial build OS such as Feisty and Gutsy), site-packages is expected to be under $CHANDLERBIN/release|debug.

The way RunPython detects whether you're running a full build or not is by finding a local build of Python. On Mac, this is determined by finding $CHANDLERBIN/release|debug/Library/Frameworks/Python.framework. If a local build of Python is found, that is what is run. If, that possibly unexpected, local build of Python is incomplete, that is, missing stuff in its site-packages, you get that kind of error.

In other words, on a partial build OS such as Leopard, Feisty or Gutsy, always make sure you don't have a stray installation of a local python build in the way that may be left over from an older build (pre-partial) or some other source code tree sharing mechanism.

Andi..
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev

Reply via email to