2009/5/21 David Glick davidgl...@onenw.org:
Won't this cause problems if a z3c.form uses a template which calls a macro
from a traditional Zope page template? That is, make it impossible to use
z3c.form in a site that isn't using z3c.pt for everything?
That was the reason for z3c.ptcompat; it
Summary of messages to the zope-tests list.
Period Thu May 21 12:00:00 2009 UTC to Fri May 22 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: Thu May 21 21:01:38 EDT 2009
URL:
I released a new version of zope.app.component to fix a bug introduced in
the recently deprecation of its metadirectives. Packages that were broken
by this should use this new version.
--
Alex Smith
Software Engineer
Zope Corporation
___
Zope-Dev
I just released a new version of zope.app.publisher. The changes in this
version are largely related to reducing dependencies on zope.app.component
and zope.app.container.
--
Alex Smith
Software Engineer
Zope Corporation
___
Zope-Dev maillist -
On May 21, 2009, at 11:09 PM, Malthe Borch wrote:
2009/5/21 David Glick davidgl...@onenw.org:
Won't this cause problems if a z3c.form uses a template which calls
a macro
from a traditional Zope page template? That is, make it impossible
to use
z3c.form in a site that isn't using
Alexander J Smith wrote:
I released a new version of zope.app.component to fix a bug introduced
in the recently deprecation of its metadirectives. Packages that were
broken by this should use this new version.
Oops: sorry for the breakage and thanks very much for the fix!
Regards,
Martijn
Hey,
Chris McDonough wrote:
[snip]
I tried to go after this today (reversing the dependency setup between
zope.formlib and zope.app.form). There are hundreds of changes that need to
be
made to move interfaces to zope.formlib. I made them (more or less
mechanically) but then couldn't
Hey,
Alexander J Smith wrote:
I just released a new version of zope.app.publisher. The changes in
this version are largely related to reducing dependencies on
zope.app.component and zope.app.container.
Thanks very much for doing this work!
I could actually remove the (direct)
Hi there,
This is a progress report on the package dependency refactoring work.
We've had a lot of people contribute to this process (thanks
everybody!), and bit by bit we are able to make a serious impact on
dependencies. Yay!
Let's take for example zope.app.publisher, which a few weeks ago
On 5/22/09 1:11 PM, Martijn Faassen wrote:
After some work we'd gotten it down to this:
http://startifact.com/depgraphs/zope_app_publisher_cycles2.svg
And by now the main cycles left are these:
http://startifact.com/depgraphs/zope_app_publisher_cycles3.svg
So, the only dependency cycles
I just released a new version of zope.mimetype. This version no longer
depends on zope.app.component directly.
--
Alex Smith
Software Engineer
Zope Corporation
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
Chris McDonough wrote:
On 5/22/09 1:11 PM, Martijn Faassen wrote:
After some work we'd gotten it down to this:
http://startifact.com/depgraphs/zope_app_publisher_cycles2.svg
And by now the main cycles left are these:
http://startifact.com/depgraphs/zope_app_publisher_cycles3.svg
So, the
Hi,
So, we determined that OFS.Traversable's unrestrictedTraverse()
shouldn't grow support for IPublishTraverse, which is fair enough. We're
now using an ITraversable adapter instead (++namespace++).
However, we found another inconsistency. In URL traversal, this works:
13 matches
Mail list logo
