[EMAIL PROTECTED] wrote:
> The dtml-in batching mechanisms are quite difficult to debug - the DTML
> documentation I have has examples which break it and there's no indication
> of why. It turns out the DT_In renderwb() code gobbles all exceptions from
> the rendering of the previous and next blocks. I've hacked my code so that
> there's no try/except clause any more. I'm not sure what exception it's
> trying to catch, but could it perhaps be made a little more picky?
And here's a diff - I'm pretty sure this was the intended behaviour...
*** /tmp/DT_In.py.orig Mon Jan 22 12:00:53 2001
--- DT_In.py Mon Jan 22 12:00:58 2001
*** 561,566 ****
--- 561,570 ----
# there are more items, without actually
# computing a length:
+ except IndexError:
+ if self.elses: result=render(self.elses, md)
+ else: result=''
*** 568,576 ****
- if self.elses: result=render(self.elses, md)
- else: result=''
result = 
--- 572,577 ----
Senior Software Developer, Bizar Software (www.bizarsoftware.com.au)
Zope-Dev maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists -