Wolf Logan wrote:
ok. i patched ExternalMethod sufficiently to see the error message, and i was able to track the problem. it's another name collision.
Cool.
the mxDateTime package uses a module named DateTime. so does ZOPE. when my code tries to unpickle the mxDateTime objects, it tries to use the definitions in the ZOPE DateTime module, and fails.
i know this was a problem with PIL as well. was there ever an "official" workaround?
I don't know how official it is, bt you could create an mxDateTime package (as in Python package) and put it's DateTime module in their. Then, the mxDateTime DateTime class will get pickled as "mxDateTime.DateTime.DateTime", rather than as "DateTime.DateTime". This might require some tweeks to the mxDateTime registration code. In the long-run, I intend to move all of the Zope packages into a single Zope package, so there aill be only one name, "Zope" added to the path. This will be some time off though. Jim -- Jim Fulton mailto:jim@digicool.com Python Powered! Technical Director (888) 344-4332 http://www.python.org Digital Creations http://www.digicool.com http://www.zope.org Under US Code Title 47, Sec.227(b)(1)(C), Sec.227(a)(2)(B) This email address may not be added to any commercial mail list with out my permission. Violation of my privacy with advertising or SPAM will result in a suit for a MINIMUM of $500 damages/incident, $1500 for repeats.