I just committed the removal of the dependency from zope.filerepresentation
to zope.container, breaking the dependency cycle.

* 2009-07-08 15:13, Jim Fulton wrote:
> Sure, but if they want to *use* zope.container.directory, they have to
> separately import zope.filerepresentation.interfaces, in which case
> they're already depending on it, and a dependency in zope.container,
> even in an extra, is superfluous.

It seems the only user of zope.container.directory is zope.app.dav, but for
this reason I'm not going to touch zope.container at all.

All in all, remove the circular dependency was my original goal. :)


Fabio Tranchitella                         http://www.kobold.it
Free Software Developer and Consultant     http://www.tranchitella.it
1024D/7F961564, fpr 5465 6E69 E559 6466 BF3D 9F01 2BF8 EE2B 7F96 1564
Zope-Dev maillist  -  Zope-Dev@zope.org
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope )

Reply via email to