That solved the confusion. I wasn't aware that gadfly support has been
removed from later versions of Zope.
Thanks,
Vimal
-Original Message-
From: zopyxfil...@googlemail.com [mailto:zopyxfil...@googlemail.com] On
Behalf Of Andreas Jung
Sent: 16 May 2009 17:32
To: Velayudhan, Vimalkumar
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 16, 2009, at 23:01 , Wichert Akkerman wrote:
Previously Sidnei da Silva wrote:
Now for another question: how do people feel about moving Zope 3 and
CMF bugs to a similar setup. That is, bug mail goes to a separate
mailing list instead of
On 16.05.09 22:33, Sidnei da Silva wrote:
On Sat, May 16, 2009 at 5:24 PM, filtered zopyxfil...@googlemail.com
wrote:
You were assimilated by Canonical?
I don't understand the question. I'm just asking if it makes sense to
have the same setup for CMF and Zope 3 as
Summary of messages to the zope-tests list.
Period Sat May 16 12:00:00 2009 UTC to Sun May 17 12:00:00 2009 UTC.
There were 8 messages: 8 from Zope Tests.
Tests passed OK
---
Subject: OK : Zope-2.10 Python-2.4.6 : Linux
From: Zope Tests
Date: Sat May 16 20:52:20 EDT 2009
URL:
Am 22.04.2009 um 14:48 schrieb Jacob Holm:
Michael Howitz wrote:
[...]
Anyone having an idea for a possibly working solution?
As I got no responsed, I'd like to put this issue into z3c.form's
bugtracker. But which is the correct one?
https://bugs.launchpad.net/zope3/ ?
I don't know about
Hi,
what is still to be done for the z3c.form 2.0 release?
Something I can help?
Yours sincerely,
--
Michael Howitz · m...@gocept.com · software developer
gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany
http://gocept.com · tel +49 345 1229889 8 · fax +49 345 1229889 1
On 5/15/09 7:33 AM, Martijn Faassen wrote:
Hanno Schlichting wrote:
Chris McDonough wrote:
I've created two codependent branches of zope.container and
zope.lifecyclevent:
[...]
I don't know if merging this stuff is reasonable. I do understand the
difference between lifecycle events and
Chris McDonough wrote:
These branches were merged. I made a new release of zope.lifecycleevent
(3.5.2)
to PyPI.
Thanks very much for doing this work.
As a reminder for the future, please do release changes in the API (as
in zope.lifecycleevent) as major releases (i.e. 3.6).
I realize
In SVN, as a result of changes to zope.container, zope.lifecycleevent,
zope.location, and zope.intid:
zope.intid/trunk/ OK (20 dependencies) (delta -14 dependencies)
zope.container/trunk/ OK (30 dependencies) (delta -2 dependencies)
zope.location/trunk/ OK (08 dependencies) (delta -0
I don't currently have access to publish zope.intid, but I think it's probably
ready for a release too, BTW.
- C
On 5/17/09 1:34 PM, Martijn Faassen wrote:
Chris McDonough wrote:
These branches were merged. I made a new release of zope.lifecycleevent
(3.5.2)
to PyPI.
Thanks very much
On Sun, May 17, 2009 at 3:15 AM, Jens Vagelpohl j...@dataflake.org wrote:
Same here. There is no reason for yet another mailing list. I see it
as needlessly duplicating what Launchpad already does.
So should we backtrack and undo the change to the zope-dev team which
made it send messages to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On May 17, 2009, at 22:53 , Sidnei da Silva wrote:
On Sun, May 17, 2009 at 3:15 AM, Jens Vagelpohl j...@dataflake.org
wrote:
Same here. There is no reason for yet another mailing list. I see it
as needlessly duplicating what Launchpad already
On 5/15/09 7:00 AM, Martijn Faassen wrote:
Hey,
Chris McDonough wrote:
I did a bit of research on the direct zope.app.* dependencies of
zope.formlib.
Cool!
- I looked into its dependency on zope.app.form. It
essentially uses a bunch of interfaces from the
13 matches
Mail list logo
