[ZPatterns] Newbie asks about ZPatterns reliability. Was: Why is class_default_for_ method unbound?

[Gary Poster]

OK, forgive a de-lurking newbie who is trying to get up to speed on
ZPatterns.  The exchange below suddenly made me very nervous.  While
ZPatterns is, after all, listed as "Development" software, I had hoped that
it might be somewhat reasonable to base a production system on it...with
appropriate testing, yes, but with some confidence in ZPatterns' stability.
This exchange seemed to call my hope into question.

Would anyone care to give me a feeling for where they think this product
stands?  Should I base my app on it, or look elsewhere for now, keeping an
eye on later ZPatterns releases?

Sorry for the newbie question. :-{  Thank you for what looks to be a very
elegant and well-thought-out approach, be it usable now or only in the
future!

Thanks

Gary


> At 09:43 AM 8/23/01 +1000, Itai Tavor wrote:
> >>At 09:36 AM 8/22/01 +1000, Itai Tavor wrote:
> >>>It bothers me that nobody else ever hit this problem. So nobody ever
had
> >>>the need to use class_default_ for web-callable methods.
> >>
> >>No, just web-callable methods placed in the Python class.
> >
> >Ok... so is the alternative supposed to be
> >class_default_for_method=DTMLFile('method', globals())? Or are there
other
> >ways?
> >
> >The above, BTW, breaks LoginManager. But since breathing too heavily near
> >the computer breaks LoginManager, I don't feel like investigating it.
>
> I'm hoping Ty and I will both have some bandwidth soon (maybe during
> September) to address the many outstanding issues affecting ZPatterns and
> LoginManager.  It is likely that we'll target Zope 2.4 after a brief
> transition period to 2.3.  Right now, our production systems using
> ZPatterns and LoginManager are all still stuck on 2.2.  We've both been
> busy with different, but very involved projects involving other systems,
> and personal projects such as Ty's currently ongoing move.