RE: [Zope-dev] Class attr hotfix

I noticed that the most recent hotfix completely denies access to the getClassAttr, setClassAttr and delClassAttr from DTML. Is this going to be the behavior for future Zope versions? Yes - I think that manipulating actual class objects from DTML is a Bad Thing. I know this will break

Re: [Zope-dev] Class attr hotfix

Brian Lloyd wrote: I noticed that the most recent hotfix completely denies access to the getClassAttr, setClassAttr and delClassAttr from DTML. Is this going to be the behavior for future Zope versions? Yes - I think that manipulating actual class objects from DTML is a Bad Thing.

Re: [Zope-dev] Class attr hotfix

Casey Duncan wrote: Oh nothing too scary. Mostly I have used it to store a counter to automatically assign ids to new ZClass instances. I was really thinking of this as a way to store properties across all instances of a ZClass. I agree that manipulating objects from DTML is BAD. My

[Zope-dev] Class attr hotfix

I noticed that the most recent hotfix completely denies access to the getClassAttr, setClassAttr and delClassAttr from DTML. Is this going to be the behavior for future Zope versions? I know this will break code, so it might be prudent to alert people when the fix is rolled into the next Zope