Finally, we want to upgrade from Zope 2.1.6 to 2.3.2 (Python 2.1). We now experience what many have recognized already: ZClasses are a bit volatile wrt. Zope upgrades I created a distribution under 2.1.6 and unpacked it in the new Zope 2.3 CVS (taken shortly before the 2.4 development hit the CVS). After a restart, I see the following message in the Zope log file:
------ 2001-06-14T05:46:02 ERROR(200) ZODB Couldn't load state for '\x00\x00\x00\x00\x0 0\x00f\xc2' Traceback (innermost last): File /home/dieter/tmp/ZopeCVS/lib/python/ZODB/Connection.py, line 533, in sets tate ImportError: No module named *EDd7FLD+AY2OWsUAz/H7bw==
------ 2001-06-14T05:46:14 INFO(0) Zope A broken ZClass dependency was found in the glo bal class registry. This is probably due to a product being uninstalled. The reg istry has successfully been rebuilt.
The imported ZClass is there, but when I try to view the "Basic" tab or try to do anything with a corresponding Z Instance, I get a "TypeError" exception: "String or Unicode string expected, None found". I have analysed this problem: During commit, a "DispatcherClass_ZPropertySheetsClass" instance should be pickled ("DispatcherClass" is my ZClass). This fails, because the class' "__module__" is "None". Two questions: 1. what is this strange module, that could not be loaded? In fact, I would be very astonished, if it could. 2. what should "DispatcherClass_ZPropertySheetsClass.__module__" be. Dieter