[Zope3-dev] Re: [Zope3-checkins] SVN: Zope3/trunk/ Add DEPENDENCIES.cfg for zope.testbrowser and tell zpkgtools where to find them.

[Fred Drake]

On 11/4/05, Stephan Richter <srichter at cosmos.phy.tufts.edu> wrote:
> > Also, if we do move them back into testbrowser, we're going to have
> > to send another patch to the maintainer, after running the external
> > tests: one of the packages, I forget which, no longer works with the
> > sys.modules hack because the package's __init__ expects to find its
> > contents (already) in the proper place.
>
> I see. So based on Fred's answer I would really like you to move those
> packages back into testbrowser.

At the moment, Philippe's changes are not ready.  He's making
progress, but he has other things he needs to be doing as well.  My
time is not currently available in sufficient quantity to even take a
good look at this, though I'm trying to remain available to him for
questions.

I spent time a month or two ago trying to use zpkg on the Zope 2
trunk, and ran into troubles relating to Five; I don't remember the
details now.  I was assured that the newer version of Five would solve
those problems (and appearantly they did), but the merge into Zope 2
happened late in the Zope 2 release cycle.  That meant we didn't
really have enough time to deal with the zpkg issues then.

I do wish that I had realized we'd be running into the non-packaged
module problem at the time, because that could have been dealt with
separately, and would have avoided the current time-crunch.  (It was
not a problem for Zope 3 at that point, and I'm sufficiently distant
from Zope 2 that I didn't recognize the coming pain.)  I'm concerned
that we're completely re-structuring the build process right before a
release (in the Zope 2 case); that's not the way to create a stable
platform.


  -Fred

--
Fred L. Drake, Jr.    <fdrake at gmail.com>
"Society attacks early, when the individual is helpless." --B.F. Skinner