Fabio Tranchitella wrote:
Hello,
I just committed the removal of the dependency from zope.filerepresentation
to zope.container, breaking the dependency cycle.
A belated yay! Thanks!
Regards,
Martijn
___
Zope-Dev maillist - Zope-Dev@zope.org
On Jul 7, 2009, at 5:15 PM, Fabio Tranchitella wrote:
Hello,
I would like to break the dep cycle between zope.container and
zope.filerepresentation. I already prepared the two patches
(attached to
this e-mail), but I'm not confident enough with the zope3 repository
to
check in them
Hello,
* 2009-07-08 12:51, Jim Fulton wrote:
I find it a bit hard to believe that there are no clients of these
interfaces, but, if that's the case, I suggest deprecating
zope.filerepresentation and zope.container.directory. In that case, I'd
just remove the dependency in zope.container on
On Jul 8, 2009, at 8:21 AM, Fabio Tranchitella wrote:
Hello,
* 2009-07-08 12:51, Jim Fulton wrote:
I find it a bit hard to believe that there are no clients of these
interfaces, but, if that's the case, I suggest deprecating
zope.filerepresentation and zope.container.directory. In that
Hello,
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
Hello,
I would like to break the dep cycle between zope.container and
zope.filerepresentation. I already prepared the two patches (attached to
this e-mail), but I'm not confident enough with the zope3 repository to
check in them without asking for comments.
Is this the right way to break the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fabio Tranchitella wrote:
Hello,
I would like to break the dep cycle between zope.container and
zope.filerepresentation. I already prepared the two patches (attached to
this e-mail), but I'm not confident enough with the zope3 repository to
