In Zope 2.10 exception views were acquisition-wrapped in the publisher
context. This appears to have changed in Zope 2.12: exception views are
now wrapped in the exception. This is problematic since it means you can
no longer use the context when rendering an error page, so things like
On Tue, Feb 23, 2010 at 10:56 AM, Wichert Akkerman wich...@wiggy.net wrote:
In Zope 2.10 exception views were acquisition-wrapped in the publisher
context.
In Zope 2.10, exception views didn't exist in Zope2. They were only
introduced in Zope 2.11.
This appears to have changed in Zope 2.12:
Wichert Akkerman wrote:
On 2/23/10 11:09 , Hanno Schlichting wrote:
On Tue, Feb 23, 2010 at 10:56 AM, Wichert Akkermanwich...@wiggy.net
wrote:
In Zope 2.10 exception views were acquisition-wrapped in the publisher
context.
In Zope 2.10, exception views didn't exist in Zope2. They were
On 2/23/10 12:33 , Martin Aspeli wrote:
Wichert Akkerman wrote:
On 2/23/10 11:09 , Hanno Schlichting wrote:
On Tue, Feb 23, 2010 at 10:56 AM, Wichert Akkermanwich...@wiggy.net
wrote:
In Zope 2.10 exception views were acquisition-wrapped in the publisher
context.
In Zope 2.10, exception
Summary of messages to the zope-tests list.
Period Mon Feb 22 12:00:00 2010 UTC to Tue Feb 23 12:00:00 2010 UTC.
There were 6 messages: 6 from Zope Tests.
Tests passed OK
---
Subject: OK : Zope-2.10 Python-2.4.6 : Linux
From: Zope Tests
Date: Mon Feb 22 20:36:49 EST 2010
URL:
Hi,
A lot of the forms I write perform a redirect at the end of the action
handler for a successfully submitted form.
z3c.form's __call__() indiscriminately calls update() and then render().
This means that even if something in update() (the action handler in
this case) causes a redirect, the
On 2/23/10 15:33 , Martin Aspeli wrote:
Hi,
A lot of the forms I write perform a redirect at the end of the action
handler for a successfully submitted form.
z3c.form's __call__() indiscriminately calls update() and then render().
This means that even if something in update() (the action
On Tuesday 23 February 2010, Martin Aspeli wrote:
Grok's forms do something like this:
def __call__(self):
self.update()
if self.request.response.getStatus() not in (301, 302):
return self.render()
return u''
Would it be an idea for z3c.form to do the
On Tue, Feb 23, 2010 at 08:57:09AM -0500, Benji York wrote:
On Sat, Feb 20, 2010 at 7:53 AM, Ross Patterson m...@rpatterson.net wrote:
I started a branch for doing W3C HTML validation on responses to
zope.testbrowser requests:
On Tue, Feb 23, 2010 at 9:57 AM, Marius Gedminas mar...@gedmin.as wrote:
I'd like to chime in and suggest using WSGI to hook up zope.testbrowser
and zope.app.testing.functional (or a better-designed replacement for
the latter). Then you could plug in W3CValidatingMiddleware (if one
doesn't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
In order to make zope.schema more useful outside of Zope, I would like
to make the dependency on zope.i18nmessageid optional. I have checked
in a branch which does this:
http://svn.zope.org/zope.schema/branches/tseaver-optional_i18nmessageid
On Tuesday 23 February 2010, Tres Seaver wrote:
In order to make zope.schema more useful outside of Zope, I would like
to make the dependency on zope.i18nmessageid optional. I have checked
in a branch which does this:
On Tue, Feb 23, 2010 at 04:57:02PM +0200, Marius Gedminas wrote:
On Tue, Feb 23, 2010 at 08:57:09AM -0500, Benji York wrote:
On Sat, Feb 20, 2010 at 7:53 AM, Ross Patterson m...@rpatterson.net wrote:
I started a branch for doing W3C HTML validation on responses to
zope.testbrowser
It looks good. But, the try/except and instanciation of the
MessageFactory could be done only once, in the __init__ of the package
for instance. That would be a central place to change it and to import
from.
2010/2/23 Stephan Richter srich...@cosmos.phy.tufts.edu:
On Tuesday 23 February 2010,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Souheil CHELFOUH wrote:
It looks good. But, the try/except and instanciation of the
MessageFactory could be done only once, in the __init__ of the package
for instance. That would be a central place to change it and to import
from.
I foresee
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hanno Schlichting wrote:
On Tue, Feb 23, 2010 at 1:26 AM, Tres Seaver tsea...@palladion.com wrote:
Hanno Schlichting wrote:
-2.12.1 (unreleased)
+2.13.0 (unreleased)
---
+- Avoid defining ``__getnewargs__`` as not to defeat the
16 matches
Mail list logo
