Chris McDonough wrote:
On 5/14/09 11:05 PM, Chris McDonough wrote:
- It depends on zope.filerepresentation but depends only on its interfaces
IReadDirectory, IWriteDirectory, and IDirectoryFactory.
(zope.filerepresentation has 32 transitive dependencies).
I found out that
Hey,
Chris McDonough wrote:
zope.container (32 transitive dependencies) has some possibly low-hanging
dependency tease-apart fruit. Does anyone have any ideas about to sort out
the
below, particularly with externalizing the mentioned interface dependencies?
- It depends on
Hey,
Chris McDonough wrote:
On 5/14/09 11:05 PM, Chris McDonough wrote:
zope.container (32 transitive dependencies) has some possibly low-hanging
dependency tease-apart fruit. Does anyone have any ideas about to sort out
the
below, particularly with externalizing the mentioned interface
On Friday 15 May 2009, Martijn Faassen wrote:
It's tempting to start pushing more interfaces (and exceptions) down
into zope.browser to break dependencies further. It does run the risk of
turning zope.browser into a bit of a mash though. Perhaps that's worth
it. Opinions, anyone?
zope.browser
Stephan Richter wrote:
On Friday 15 May 2009, Martijn Faassen wrote:
It's tempting to start pushing more interfaces (and exceptions) down
into zope.browser to break dependencies further. It does run the risk of
turning zope.browser into a bit of a mash though. Perhaps that's worth
it.
Previously Martijn Faassen wrote:
If we wanted to make zope.container agnostic about traversal and the
publisher, we'd need to move this code somewhere else. I cannot think of
an existing package for this (anyone?). Lacking that, I'd suggest a new
package, zope.containertraversing or
On 5/14/09 11:05 PM, Chris McDonough wrote:
zope.container (32 transitive dependencies) has some possibly low-hanging
dependency tease-apart fruit. Does anyone have any ideas about to sort out
the
below, particularly with externalizing the mentioned interface dependencies?
- It depends on
