behavior of verbose.report

I would like to use verbose.report during the rc

    > validation process to fix this. The problem is that
    > verbose is initialized as 'silent', and is only changed to
    > the user-selected level after the rest of the rc-file has
    > been read. One solution might be to move the verbose
    > entries to the top of matplotlibrc, another might be to
    > modify __init__.py to validate the verbose settings first,
    > no matter where they are located in the matplotlibrc. I
    > favor the second approach.

    > Thoughts, opinions, suggestions?

I am not in favor of moving them to the top, since I like to have the
most commonly changed ones there. Nor am I wild about a 2 pass
approach.

Would it work for you to buffer the rc messages during initialization,
and then output them at the end of the rc read depending on the
verbose settings?

JDH

That's a good idea. I'll work on it as soon as I get a chance, probably
tomorrow morning.

Darren

···

On Friday 27 January 2006 09:50, John Hunter wrote:

    > I would like to use verbose.report during the rc
    > validation process to fix this. The problem is that
    > verbose is initialized as 'silent', and is only changed to
    > the user-selected level after the rest of the rc-file has
    > been read. One solution might be to move the verbose
    > entries to the top of matplotlibrc, another might be to
    > modify __init__.py to validate the verbose settings first,
    > no matter where they are located in the matplotlibrc. I
    > favor the second approach.

    > Thoughts, opinions, suggestions?

I am not in favor of moving them to the top, since I like to have the
most commonly changed ones there. Nor am I wild about a 2 pass
approach.

Would it work for you to buffer the rc messages during initialization,
and then output them at the end of the rc read depending on the
verbose settings?

changed in cvs

···

On Friday 27 January 2006 09:50, John Hunter wrote:

    > I would like to use verbose.report during the rc
    > validation process to fix this. The problem is that
    > verbose is initialized as 'silent', and is only changed to
    > the user-selected level after the rest of the rc-file has
    > been read. One solution might be to move the verbose
    > entries to the top of matplotlibrc, another might be to
    > modify __init__.py to validate the verbose settings first,
    > no matter where they are located in the matplotlibrc. I
    > favor the second approach.

    > Thoughts, opinions, suggestions?

I am not in favor of moving them to the top, since I like to have the
most commonly changed ones there. Nor am I wild about a 2 pass
approach.

Would it work for you to buffer the rc messages during initialization,
and then output them at the end of the rc read depending on the
verbose settings?