(CC'ing list this time)
On Tue, Sep 21, 2010 at 4:30 AM, Dieter Weber <dieter@...887...> wrote:
well, I was rethinking the patch again after sending it, and I got it
wrong. :-/ Accessing a deprecated property would give a KeyError with my
previous patch, as this property is never set. To support deprecated
options and display warning messages, one needs some kind of custom
__getitem__ method. I've appended a diff where such a method is created
"on demand" if the verbosity level is 'helpful' or more.
Which is why I left it to people more familiar with the code to do a
more, ahem, thorough review. Still, I wonder if there's a better way
to maintain the runtime boost without needing a __getitem__...
Need coffee for that.
Graduate Research Assistant
School of Meteorology
University of Oklahoma