[Zope-dev] Breaking the dep cycle between zope.{container, filerepresentation}

[Tres Seaver]

-----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
> check in them without asking for comments.
> 
> Is this the right way to break the dependency? I think nobody really uses
> zope.filerepresentation, so transforming it into a dummy package which just
> imports things from zope.container.interface is ok.

I think I would break the cycle by moving the IReadDirectory,
IWriteDirectory, and IDirectoryFactory interfaces to zope.container:
those three interfaces are used directly in zope.container, and they are
"about" containers.  I would leave the other two (IReadFile, IWriteFile)
declared in zope.filerepresentation.

We can then leave behind BBB imports in zope.filerepresentation, which
will depend on zope.container for them;  zope.container will no longer
depend on zope.filerepresentation.


Tres.
- --
===================================================================
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFKVAJE+gerLs4ltQ4RAp7yAKCcWI+rG2oNGVrWXWiBSXnNKb36cgCgizIV
EdYKLqfwcU0kU99x2HeHmmA=
=t8KD
-----END PGP SIGNATURE-----