Displaying 3 results from an estimated 3 matches for "default_messag".
Did you mean:
default_message
2007 Jan 29
3
Bug in should_not_be - What else to use?
...l" - this
would read nicer as "1 should not be == 1"
Where is the "nil" in the failure message coming from anyway? I digged a
little bit deeper into the sources and figured that out too:
In the Not class, instead of passing the not expected value as the
second argument to default_message, it gets appended to the message text,
so the missing argument will then be added by default_message() as nil.
I''ve already added a bug report.
bye,
Tobias
2010 Feb 11
1
[PATCH] Provides a reference implementation management server.
...onfig/middleware.py file.
+
+ """
+
+ @expose('ovirtserver.templates.error')
+ def document(self, *args, **kwargs):
+ """Render the error document"""
+ resp = request.environ.get('pylons.original_response')
+ default_message = ("<p>We're sorry but we weren't able to process "
+ " this request.</p>")
+ values = dict(prefix=request.environ.get('SCRIPT_NAME', ''),
+ code=request.params.get('code', resp.st...
2010 Feb 17
0
[PATCH] Provides the new node lifecycle events.
...onfig/middleware.py file.
-
- """
-
- @expose('ovirtserver.templates.error')
- def document(self, *args, **kwargs):
- """Render the error document"""
- resp = request.environ.get('pylons.original_response')
- default_message = ("<p>We're sorry but we weren't able to process "
- " this request.</p>")
- values = dict(prefix=request.environ.get('SCRIPT_NAME', ''),
- code=request.params.get('code', resp.st...