Jim Fulton wrote:
We need to stitch zope.app into Zope 2 more carefully than we are now. Much of what we are stitching is unreleased in Zope3 and depends on things not stitched nto Zope 2.
Among other things, this means that we can't use
python2.4 test.py -m.
to run all tests without getting test failures.
It would be great if someone would sort this out before we do any Zope 2.9 releases. :)
Well, from that vague "we need to do it more carefully" I deduce that you would like to stitch in zope.app like we stitch in zope, i.e. each package individually. Unfortunately, that will not work equally well because there are several text files at zope.app, more than just the __init__.py: DEPENDENCIES.cfg PACKAGE.cfg PUBLICATION.cfg browser.zcml configure.zcml content_types.py datetimeutils.py decorator.py ftesting.zcml menus.zcml meta.zcml servicenames.py timezones.py At least the Python modules and zpkgutils files will be needed in Zope 2 as well. The real problem is that svn:externals doesn't work on files, just on directories. So, we'd have to manage separate copies of those files. Are you sure we want to get into that? Philipp