On Mar 6, 2007, at 3:03 AM, Uwe Oestermeier wrote:
My preference would be to leave everthing as it is
That's not possible, as we're changing out packaging technology.
(See my separate note to Baiju.)
and include zope.fssync
as a dependency and
zope.app.fssync as a part of the egg. Alternatively I can try to
code of zope.app.fssync
(and zope.app.file.fssync etc.) to zope.fssync.
Just move zope.app.file.fssync to it's own project.
I can live with both alternatives, of course, but in my opinion it
sense to leave the
Python API (independent of ZODB and locations etc.) in zope.fssync
(with security and location aware pickler) in zope.app.fssync.
Jim Fulton mailto:[EMAIL PROTECTED] Python
CTO (540) 361-1714
Zope Corporation http://www.zope.com http://www.zope.org
Zope3-dev mailing list