Bug in matplotlibrc regarding verbosity

Community matplotlib-users
1

It appears that the recent CVS versions *require* verbose.level and verbose.fileo to be set in the rc file, as per the lines (923-930) matplotlib/__init__.py:

         if i == 1:
             key = 'verbose.level'
             val, line, cnt = rc_temp.pop(key)
         elif i == 2:
             key = 'verbose.fileo'
             val, line, cnt = rc_temp.pop(key)
         else:
             key, (val, line, cnt) = rc_temp.popitem()

What's wrong with letting the default values slide through?

-Rob.

···

-----
Rob Hetland, Assistant Professor
Dept of Oceanography, Texas A&M University
p: 979-458-0096, f: 979-845-6331
e: hetland@...760..., w: http://pong.tamu.edu

2

I needed to validate the verbose settings first, so reports could be generated
during the rest of the validation process. I hadn't considered that rc files
might not include these settings. Thanks for the report, it's fixed in cvs.

Darren

···

On Thursday 02 February 2006 11:06, Robert Hetland wrote:

It appears that the recent CVS versions *require* verbose.level and
verbose.fileo to be set in the rc file, as per the lines (923-930)
matplotlib/__init__.py:

         if i == 1:
             key = 'verbose.level'
             val, line, cnt = rc_temp.pop(key)
         elif i == 2:
             key = 'verbose.fileo'
             val, line, cnt = rc_temp.pop(key)
         else:
             key, (val, line, cnt) = rc_temp.popitem()

What's wrong with letting the default values slide through?