in reply to Re^5: log level in modules
in thread log level in modules

I'm confused. Are you trying to help or get off on some power trip?

I ask questions here because I know someone has the answer. But it never fails: ask a simple question and you get asked for your life story. Ask a question with context then people worry about everything but the question.

If you know why get_logger isn't getting the modified logger, great! Tell me.

If you know how to fix my problem, great! Tell me.

If you're trying to give constructive feedback on my post so I can better ask any future questions, your failing.

Replies are listed 'Best First'.
Re^7: log level in modules
by ikegami (Patriarch) on Aug 22, 2009 at 03:32 UTC

    If you know how to fix my problem, great! Tell me.

    I would if I knew. I don't, so I asked you question to help fix it. Maybe you should consider answering them instead of this ...whatever it is?

    I don't know why you expect changes to some variable to have some some effect on the return value of get_logger. You haven't shown anything tying the two together. You provided so little information that all I can do is rule out causes until you provide more information.

    Waiting for answers to:

    • When you say "forks", are you actually referring to the creation of new threads? (Eventually answered)
    • Why do you think it has anything to do with forking?
    • Why do you think it has anything to do with signals?
    • Why do you think changes to one variable should have some effect in the return value of get_logger
    • Where can I find a minimal runnable demonstration of the problem?
      Why do you think it has anything to do with forking?

      Don't recall saying it did. Forking was mentioned as part of context and when answering questions

      Why do you think it has anything to do with signals?

      Don't recall saying it did. Simply mentioned that I'm using a signal to trigger the change in level. Again, context.

      Why do you think changes to one variable should have some effect in the return value of get_logger

      My understanding is that get_logger returnes a reference to the logger. Making changes using that reference would then make changes to the logger. Why wouldn't subsequent calls to get_logger return the modified logger?

        Don't recall saying it did.

        More importantly, you didn't say it didn't. You thought it was related enough to mention, so please go rule it out.

        Still waiting for code.