[Zope-CMF] unit test weirdness.

Dieter Maurer dieter@handshake.de
Fri, 21 Feb 2003 19:44:00 +0100

Tres Seaver wrote at 2003-2-20 17:48 -0500:
 > On Thu, 2003-02-20 at 15:37, Dieter Maurer wrote:
 > > Tres Seaver wrote at 2003-2-20 08:27 -0500:
 > >  > ...
 > >  > The "Zope.startup()" dance is a *very* recent requirement for Zope,
 > >  > introduced only after 2.6.0
 > > 
 > > How was this with new features only in major releases and just bug fixes
 > > in minor releases?
 > That change wasn't really a feature;  it was working around a "smoking
 > crater" problem in a particular startup scenario.

It could have been handled differently:

  The particular startup scenario sets the environment variable.
  Without is, "startup" is automatically called.

This unexpected change drove a colleague of mine (almost) into
crazyness and gave him a bad feeling about Zope:

  A stand-alone ZEO automation script was no longer able to
  find "Persistence.Persistent" and after this problem has been
  resolved (with an additional "import ZODB")
  it did no longer handle "INSTANCE_HOME" and threw strange

How Guido said:

  All agree that minor releases should only contain bug fixes (which
  do not brake anything) *but* with the exception of ones own
  small features ...