Hello, I'm wondering if it would be possible to drop the dependency between zope.location and zope.copy. It makes sense to me because zope.location depends on zope.copy only because it registers a LocationCopyHook, not because it is really using anything from that package. Attached to this message you can find my (proposed) patch to remove the dependency making the adapter registration optional, and informing the developer that zope.copy is needed is he is importing directly the zope.location.pickling module. Comments? Thanks, Fabio
2009/12/22 Fabio Tranchitella <kobold@kobold.it>:
I'm wondering if it would be possible to drop the dependency between zope.location and zope.copy. It makes sense to me because zope.location depends on zope.copy only because it registers a LocationCopyHook, not because it is really using anything from that package.
Attached to this message you can find my (proposed) patch to remove the dependency making the adapter registration optional, and informing the developer that zope.copy is needed is he is importing directly the zope.location.pickling module.
Comments?
Looks okay :) -- WBR, Dan Korostelev
Fabio Tranchitella wrote:
Comments?
+1 from me. Often instead of optional dependencies we'd move the registration to the other package, but that's not possible here as zope.copy doesn't depend on zope.location. Regards, Martijn
participants (3)
-
Dan Korostelev -
Fabio Tranchitella -
Martijn Faassen