Jens Vagelpohl wrote:
I'm assuming the unit tests still run successfully and you added unit
tests for your changes.
All unit tests are passing with my chances. I've to write some tests
before merging my branch. I'll write them after somebody seconds my fix.
Christian
Florent Guillaume wrote:
I had trouble finding your branch because you put it in
Zope/tiran-zpt-pydefer instead of Zope/branches/tiran-zpt-pydefer.
Could you move it ?
Ups, done :)
Christian
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org
Christian Heimes wrote:
* DeferWrapper didn't cache the result of the expression like ordinary
vars do.
This was intended, though you couldn't know that since I never
documented this. Consider the following terrible example:
This should evaluate to:
x is 0
x is 1
x is 2
Why?? I d
Dieter Maurer wrote:
Maybe, the feature could get documented as well...
An undocumented feature is only half valuable...
+1
Is there anybody out there who can help me with the docs? I need someone
to translate my english into real and nice english and someone with the
permissions to update the ZP
Evan Simpson wrote:
Christian Heimes wrote:
* DeferWrapper didn't cache the result of the expression like
ordinary vars do.
This was intended, though you couldn't know that since I never
documented this. Consider the following terrible example:
This should evaluate to:
x is 0
x is 1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian Heimes wrote:
> Dieter Maurer wrote:
>
>> Maybe, the feature could get documented as well...
>>
>> An undocumented feature is only half valuable...
>
>
> +1
>
> Is there anybody out there who can help me with the docs? I need someone
> to
Christian Heimes wrote:
That's an interessting use case. Do you want me to keep the code and
make up a new expression? I'm thinking about "lazy:".
If you have a particular use for "defer:" that would justify the split,
please go ahead. I have no particular interest in keeping it.
Cheers,
Evan @
Evan Simpson wrote:
Christian Heimes wrote:
That's an interessting use case. Do you want me to keep the code and
make up a new expression? I'm thinking about "lazy:".
If you have a particular use for "defer:" that would justify the split,
please go ahead. I have no particular interest in keepin
Tres Seaver wrote:
I'd be glad to help with that, Christian.
I've added a doc string to the DeferExpr module. Do you want me to write
more docs is it enough to be added to the ZPT guide?
Also I need a little help for the unit tests. How can I emulate
tal:content or similar inside an expression
