[Zope-dev] Re: International Objects

[Tim McLaughlin]

Roger,
I've identified a serious weirdness that causes InternationalObjects not
to work.  It's this...

InternationalObjects -
works on 2.4.0 and 2.4.0 upgraded to 2.4.1
but does not work on clean 2.4.1 install.

This indicates an disconnect between the upgrade and clean install paths
(at least that's my first thought).  Zope-devers, any ideas?  Anybody
know of any __getattr__ changes in the 2.4.0 to 2.4.1 transition?

Cheers,
Tim

Roger Espinosa wrote:
> 
> On Wed, 17 Oct 2001, Tim McLaughlin wrote:
> 
> >
> > If so, let me know what you think after you toy with it a bit.  Note
> > that it also works with ZClass props :)
> >
> 
> Still persisting, as the more I dwell on it, the more I like this approach
> --- one of the reasons I'm using Zope is the ease of mixing complicated
> code with simpler code (handy for the education environment), and this
> approach fits that ideal.
> 
> At any rate --- I continue to fail if I try the monkeypatch; oddly, if I
> do this bit of code:
> 
>         x = Item()
>         print Item.__getattr__(x, 'DEBUG')
> 
> it'll correctly work, but
> 
>         x.DEBUG
> 
> seems to skip it altogether; I even assigned the InternationalObjects
> __getattr__ to an unrelated method (e.g. Item.fetchValueForKey =
> __getattr__) and *that* works, which sure looks like something else is
> hijacking __getattr__.
> 
> Except when I just go patch the code into OFS.SimpleItem (I'm already
> hacking get_request, so what the heck :)...it works as hoped. (Which would
> tend to discount the hijacked __getattr__ business.)
> 
> Anyway, neat idea :)
> 
> Roger

-- 
Tim McLaughlin
iterationZERO - www.iterationzero.com
703.481.2233