Re: [Zope-dev] Re: 2.3.3 - 2.5.1b2 upgrade problem

2002-04-18 Thread Chris Withers
Shane Hathaway wrote: http://dev.zope.org/Wikis/DevSite/Proposals/BetterTracebacks All the work described (besides the documentation and Dieter's suggestion of adding error_tb to the default standard_error_message) is checked into the trunk. No more invalid HTML. :-) Well, it's only

[Zope-dev] Re: 2.3.3 - 2.5.1b2 upgrade problem

2002-04-17 Thread Simon Michael
R. David Murray [EMAIL PROTECTED] writes: Probably, but I naively imagined that I was sophisticated enough to be finding a real problem...but I'm obviously not smart enough to realize that a breakage this fundamental could be due to a package like ZDebug. I wasn't either.. I think the word

Re: [Zope-dev] Re: 2.3.3 - 2.5.1b2 upgrade problem

2002-04-17 Thread Shane Hathaway
Simon Michael wrote: R. David Murray [EMAIL PROTECTED] writes: Probably, but I naively imagined that I was sophisticated enough to be finding a real problem...but I'm obviously not smart enough to realize that a breakage this fundamental could be due to a package like ZDebug. I wasn't

Re: [Zope-dev] Re: 2.3.3 - 2.5.1b2 upgrade problem

2002-04-17 Thread Chris Withers
Shane Hathaway wrote: I've been putting in code for Zope 2.6 that replaces the functionality of ZDebug. ZDebug was always woefully unsafe. Zope 2.6 will have improved tracebacks. Does that mean we can turn them off when we don't want them and there's no more of that damn awful appending

Re: [Zope-dev] Re: 2.3.3 - 2.5.1b2 upgrade problem

2002-04-17 Thread Shane Hathaway
On Wed, 17 Apr 2002, Chris Withers wrote: Shane Hathaway wrote: I've been putting in code for Zope 2.6 that replaces the functionality of ZDebug. ZDebug was always woefully unsafe. Zope 2.6 will have improved tracebacks. Does that mean we can turn them off when we don't want them

[Zope-dev] Re:2.3.3?

2001-04-13 Thread Chris Withers
The next stable release may very well (very probably) be a 2.3.3 release. Which will still be a Python 1.5.2 release. I have the idea that you think that either the 2.3.x line will switch to Python 2.1 now (and 2.3.3 is to be released soon) or that no more development on the 2.3.x line will