1

Here's the problem. I have mynamespace.mypackage that has as a dependency mynamespace.mydependencypackage, that is a local utility. It's registered using component registry.

In config.py from mynamespace.mypackage, I have 

DEPENDENCIES = ['mynamespace.mydependencypackage']

And in my mynamespace.mypackage's setuphandlers.py this dependency is installed if not already installed.

Problem is: if I reinstall mynamespace.mypackage through ZMI, everything seems to perfectly install (since no errors are shown) but I keep getting a ComponentLookupError when using methods in mynamespace.mypackage that gets the utility:

Module zope.component._api, line 207, in getUtility
ComponentLookupError: (<InterfaceClass MY_UTILITY_INTERFACE, '')

I can 'fix' this problem, by reinstalling the mynamespace.mydependencypackage in my setuphandlers.py or through the ZMI as well when reinstalling mynamespace.mypackage, but this doesn't seem the best solution for me.

What am I missing about Generic Setup here? I didn't make this utility persist any value on ZODB whatsoever. I can just forget about all these problems and create a BrowserView with utilities methods, but I want to understand first why am I having these problems.

EDIT: Now, I have a bigger problem. The TypeError: ('object.__new__(MyClass) is not safe, use Persistence.Persistent.__new__()', <function _reconstructor at 0xb7783e9c>, (<class 'mynamespace.mydependencypackage.package.MyClass'>, <type 'object'>, None)) is being shown. Full traceback:

Traceback (innermost last):
  Module ZPublisher.Publish, line 110, in publish
  Module ZPublisher.BaseRequest, line 429, in traverse
  Module ZPublisher.BeforeTraverse, line 99, in __call__
  Module Products.CMFCore.PortalObject, line 94, in __before_publishing_traverse__
  Module zope.event, line 23, in notify
  Module zope.component.event, line 26, in dispatch
  Module zope.component._api, line 130, in subscribers
  Module zope.component.registry, line 290, in subscribers
  Module zope.interface.adapter, line 535, in subscribers
  Module zope.component.event, line 33, in objectEventNotify
  Module zope.component._api, line 130, in subscribers
  Module zope.component.registry, line 290, in subscribers
  Module zope.interface.adapter, line 535, in subscribers
  Module zope.app.component.site, line 375, in threadSiteSubscriber
  Module zope.app.component.hooks, line 61, in setSite
  Module Products.CMFCore.PortalObject, line 75, in getSiteManager
  Module ZODB.Connection, line 761, in setstate
  Module ZODB.Connection, line 819, in _setstate
  Module ZODB.serialize, line 604, in setGhostState
  Module ZODB.serialize, line 597, in getState
  Module copy_reg, line 48, in _reconstructor
TypeError: ('object.__new__(MyClass) is not safe, use Persistence.Persistent.__new__()', <function _reconstructor at 0xb7783e9c>, (<class 'mynamespace.mydependencypackage.package.MyClass'>, <type 'object'>, None))
Somebody still uses you MS-DOS
  • 13,029
  • 20
  • 64
  • 103

1 Answers1

5

It sounds like you have custom Python code in your setuphandlers.py file to install the dependency. Is there a reason you don't note the dependency in the metadata.xml file? Or can you show us that code?

When activating an add-on in Plone, it does a before/after comparison of various entities to support deactivation. Among these are local persistent utilities, as defined by the componentregistry.xml file. Note: anything defined in GenericSetup xml files results in persistent changes - if you want non-persistent utilities, use ZCML files to register them.

So when you have custom code to add a local utility in your setuphandlers.py code, Plone thinks this utility belongs to your main add-on. If you reinstall that add-on the utility gets removed alongside anything else and then everything is installed again.

I'm guessing your "is it already installed" check fails after the reinstall and the utility isn't added again.

You can avoid all of this, by simple giving both the dependency and main add-on their own GenericSetup profiles and than noting a dependency in the main's metadata.xml, like:

<?xml version="1.0"?>
<metadata>
  <version>1</version>
  <dependencies>
    <dependency>profile-my.dependency:default</dependency>
  </dependencies>
</metadata>

Once you do that the dependencies profile will be activated independently and Plone keeps track of it on its own. If you then decide to reinstall the main add-on, the dependency won't be touched at all and remains intact.

  • Thanks for the answer. I've updated my question with another error. I'm going to try the dependency file on metadata. – Somebody still uses you MS-DOS Aug 01 '11 at 15:31
  • The persistent error sounds like you are using componentregistry.xml file but use a class that doesn't inherit from persistent.Persistent. Either use persistent utilities via componentregistry.xml and add the proper base class, or use global utilities via ZCML files and don't have the persistent base class. –  Aug 01 '11 at 15:33
  • So, is it safe to use `class MyClass(Persistence.Persistent)` in my utility? How do I fix the error that is already being shown? I can't even delete the Plone Site. – Somebody still uses you MS-DOS Aug 01 '11 at 18:47
  • The installDependencies code is here: http://stackoverflow.com/questions/6684166/quickinstaller-installproduct-installs-stuff-that-doesnt-even-exist-how-do-i I have read about the dependency tag in metadata.xml. We were using the config.py approach because it worked for plone 3 and plone 2 legacy we have, but if the metadata.xml works, I'm going to stick with it. – Somebody still uses you MS-DOS Aug 01 '11 at 21:01
  • Hum, another problem arose: if I uninstall `mynamespace.mypackage`, the utility declared as a dependency gets uninstalled! Why? :/ I have other products that use this utility as a dependency, so it can't be uninstalled... How do I avoid uninstallation of this utility when uninstalling the product that declared the utility as a dependency? – Somebody still uses you MS-DOS Sep 19 '11 at 19:07
  • If you want custom uninstall behavior, you need to create an Extensions/Install.py in your package and provide an uninstall method. Doing so will prevent any of the standard uninstall logic to be skipped. –  Sep 26 '11 at 11:09