[ZPatterns] ZPatterns 0.4.3p2 breaks LoginManager; 0.4.3p1 works fine

[Itai Tavor]

Steve Alexander wrote:
>Itai Tavor wrote:
>>Thanks, Steve. I skipped that message when it arrived, it didn't 
>>look interesting at a quick glance. Didn't realize it was talking 
>>about the same problem.
>
>"Subject: Problem in latest ZPatterns: ..."
>Can't get much clearer than that ;-)

Ok, if you want to get technical :) 1) It mentioned setattr and id in 
the title - nothing about _v_parent or anything which would make it 
seem like it was the same problem, 2) It said you're using Zope 2.4, 
so I thought, I'm using 2.3.2, and a setattr problem would most 
likely affect all ZPatterns objects, not only Login Manager - which 
was not the case in my case, so it just didn't seem relevant to me. I 
had to read past a lot of code to find that your problem involved the 
_v_parent error. So I think it was reasonable for me to miss it :)

>
>>did you have a chance to test your patch with Zope 2.3.x yet?
>
>Nope. The only time I use Zope 2.3 now is to upgrade an application 
>to Zope 2.4 :)

Well, hopefully, now that we know of the bug, a tested fix can be 
incorporated into the official release? Phillip?

>If there's demand, I'll look at making TransactionAgents and the 
>accompanying ZPatterns variant work with Zope 2.3. It shouldn't be 
>very hard.
>
>I'd rather people upgrade to Zope 2.4/Python 2.1 though.

I can understand that... but at least for me, life's hard enough 
already without adding any more problems to it. Seeing all the 
original and interesting ways in which my projects can break under 
2.4/2.1 is not something I'm particularly looking forward to.

-- 
--
Itai Tavor                      -- "Je sautille, donc je suis."    --
itai@optusnet.com.au            --               - Kermit the Frog --
--                                                                 --
-- "If you haven't got your health, you haven't got anything"      --