Shane Hathaway wrote:
> Martijn Faassen wrote:
>> So, the only dependency cycles left in are these:
>> <--> <-->
> I fixed those tonight.  On the trunk, there are no longer any 
> dependencies between,, and 
>, except testing dependencies.

Cool! Thanks very much!

> Here is a summary of what I did:
[snip summary]
> - I used zope.deferred to deprecate things I moved from 
>,, and  Are there 
> any objections to using zope.deferred in those packages?

No objection, but what's the reason to use zope.deferred instead of 
straight imports or zope.deprecation? To break the dependencies?

> In all, I changed 6 packages.  Should I release them now, or should I 
> look for other dependencies we might clean up at the same time?  

I'm +1 on releasing now. (and thanks for making them feature releases) 
Getting these things out there gives everybody who plays with this nicer 
dependency graphs and this tends to help improvement.



Zope-Dev maillist  -
**  No cross posts or HTML encoding!  **
(Related lists - )

Reply via email to