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 zope.filerepresentation. > If an application is going to use zope.container.directory, it will need > to import zope.filerepresentation.interfaces itself, and it will have the > zope.filerepresentation dependency itself. I'd add deprecation warning > in zope.container.directory. I wouldn't add these interfaces to > zope.container.interfaces.
What about adding zope.filerepresentation as an extras_require "directory"? If somebody is using zope.container.directory, it is possible to depend on zope.container [directory]. Best regards. -- 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 http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )