AW: AW: Why do we restrict our egg testing?
"Roger Ineichen" <[email protected]> Thu, 27 Sep 2007 15:54:29 +0200
| Newsgroups | gmane.comp.web.zope.zope3 |
|---|---|
| Message-ID | <006301c8010d$f0fcef90$5800000a@mobile04> |
> Betreff: Re: AW: [Zope3-dev] Why do we restrict our egg testing? > > On 9/27/07, Benji York <[email protected]> wrote: > > Second, why would you include all of the zope.* eggs if that > > particular package doesn't depend on them? > > I suspect there are hidden differences in expectations here. ;-) > > Roger, when you assemble an application, are you expecting to > find all of zope.* in the result? No I excpect some of them, but others excpect others. So I'm pretty shure if we count all different setup then we can excpect all packages in the summary. > We're not expecting that in the projects I'm involved in. In > fact, I'd be pretty upset to find a lot of that stuff in > there, and would like to see less of it than I do. That's the problem you only solve your problems with this pattern. but the zope namspace suggest participation. And you can't ensure quality wiht this point of view. > Zope 3 is not an application, and I consider that a good thing. I agree, Zope 3 is not a application, but packages in this namespace can break things outside of your context. That doesn't matter if this are packages in a 3rd party namespace, but this should not happen in the zope namespace. > -Fred > > -- > Fred L. Drake, Jr. <fdrake at gmail.com> > "Chaos is the score upon which reality is written." --Henry Miller >