Just ported a webapp from TurboGears to Django and studying the procedure for obtaining a proper server running (i.e. not
runserver). Attempted going the suggested Apache + mod_wsgi route the Django paperwork discuss, but for whatever reason the thread stalls by helping cover their no error message or anything the moment you attempt to
import CoreData any place in a module that Apache is loading.
Particularly, the point where it stalls out is incorporated in the
CoreData/__init__.py file here:
__bundle__ = _objc.initFrameworkWrapper("CoreData", frameworkIdentifier="com.apple.CoreData", frameworkPath=_objc.pathForFramework( "/System/Library/Frameworks/CoreData.framework"), globals=globals())
Unsure what it's about CoreData which makes this fail, since
import Foundation works fine (i.e. it does not appear to become that the PyObjC stuff is damaged under Apache, just CoreData).
I am kinda considering going the lighttpd route now rather, but when anybody could reveal steps to make the mod_wsgi way work that might be good, when i would rather stick as near to the recommended easiest deployment method as you possibly can.
Thanks ahead of time for just about any experience.
Also: I am on OSX 10.6.4 with whatever latest version of PyObjC &lifier Apache includes that, as well as the latest mod_wsgi I snapped up in the Google Code website.
Try forcing WSGI application to operate in primary interpreter. Seems like PyObjC isn't implemented properly in order to be utilized in sub interpreters. See: