[on the subject of dtml picking the wrong context to look in first]
>>> I dont see a way to test this constraint, and it has proven impossible
>>> to avoid the problems using design rules. I recently checked some of
>>> our recent products using strategically placed debugging __getattr__
>>> hook
On Tue, 26 Sep 2000 07:42:29 -0400, Jim Fulton <[EMAIL PROTECTED]>
wrote:
>Toby Dickenson wrote:
>>
>> >I'm not sure exactly what problem you are refering to. It sound's
>> >like an issue of depending on a specific acquired name and having
>> >the name overridden with something bogus. Is that it
Toby Dickenson wrote:
>
(snip)
> >I'm not sure exactly what problem you are refering to. It sound's
> >like an issue of depending on a specific acquired name and having
> >the name overridden with something bogus. Is that it?
>
> There are two related issues that conspire to make the problem har
On Mon, 25 Sep 2000 12:41:21 -0400, Jim Fulton <[EMAIL PROTECTED]>
wrote:
>But Zope.debug uses the Zope environment. Unless you consider ZServer
>a critical part of the Zope environment. It is extremely
>rare for the difference between something like ZServer and
>ZPublisher.Test to have any not
Note that this conversation hasn't had anything to do
with ZEO for some time, so I'm moving it over to zope-dev.
Toby Dickenson wrote:
>
(snip)
> >I think it is really much easier to use ZPublisher/Test
> >(which is also available as Zope.debug:
> >
> > import Zope
> > Zope.debug(url)
> >
>
