-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Christian Theune wrote: > On Wed, 2009-03-11 at 17:27 +0100, Martijn Faassen wrote: >> Hi there, >> >> Stephan Richter wrote: >> [snip] >>>> In my opinion going for an extra here just to avoid this is speculating >>>> a bit too much right now. Do we really have users that want to use >>>> zope.password and really don't want zope.component and zope.schema? If >>>> so, we'll hear from them when they speak up and *then* declare an extra >>>> or take some other action. >>> +1. I want more of our decisions to go into this direction. It is a sign >>> that >>> we turn the # of packages knob as well. >> I agree with you in the case against extras. >> >> It appears though that Dan has a concrete use case for using >> zope.password in a Pylons app where he isn't interested in >> zope.component, so I'm +1 on the extra in this case. We'll see whether >> this leads to difficulties. Luckily the zope.component and zope.schema >> libraries are typically around anyway so it doesn't make reasoning about >> the graph that much harder. > > I remember that at the sprint we used to identify packages which are > "always good". E.g. zope.interface is a declared no-brainer to add to > your dependencies. The other two that keep popping up that we *might* > wanna white-list are zope.schema and zope.component.
That woould imply the transitive closure of their dependencies, which would be: - - zope.event - - zope.i18nmessageid - - zope.interface - - zope.component - - zope.schema We would need to finish trimming off the zope.component extras, first. Once done, those pacakges are all essentially "libraries," and could be managed as a "chunk." > In addition this would need documentation as well. Fleshing out the in-package narrative docs for those packages (or perhaps for the set?) would be pretty valuable, too. Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tsea...@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 iD8DBQFJwNge+gerLs4ltQ4RAtV8AKC0+44VxwGBq4n65uwM+ry4xRQfsQCfbQTQ klc7Xe1goO+nSPfaAflpl48= =2+XJ -----END PGP SIGNATURE----- _______________________________________________ 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 )