Hi All,
I'm still working on zope.fssync and zope.app.fssync. When I started, I
had the hope to finish this work before the 3.4 release, but as always it
took longer than expected. Now I'm unsure how to proceed.
I have refactored zope.fssync and zope.app.fssync into two clearly
separated
On May 2, 2007, at 3:00 AM, Uwe Oestermeier wrote:
...
Therefore I propose to postpone the release of zope.fssync until
the next
release cycle.
fssync isn't included in releases, so I don't think it matters. I
suggest you *move* these two packages out of the Zope 3 tree to their
own
On May 2, 2007, at 7:30 AM, Michael Howitz wrote:
Hi,
I discovered an unecpected behavior ob zc.buildout:
I have a package which depends in its setup.py on zc.form=0.1dev-
r74753.
In my buildout.cfg I decaled zc.form as a develop-egg by pointing
to its svn-checkout.
The problem is that
Am 02.05.2007 um 14:43 schrieb Jim Fulton:
[...]
It is expected behavior. buildout will always prefer a develop egg
that meets the given requirements.
I wanted to point out that in my case this is not true. buildout
preferes the released egg if it required with a minimum version.
Without
On May 2, 2007, at 9:31 AM, Michael Howitz wrote:
Am 02.05.2007 um 15:12 schrieb Jim Fulton:
Assuming that you have a checkout of the trunk zc.form, then you
are mistaken. The version number in the setup.py file:
http://svn.zope.org/zc.form/trunk/setup.py?view=auto
is 0.1dev. This is
