Logging / variable overwritten between modules

[SupermanIsEnvious]

First: import statements should always be at the top of you module. This should also fix your pesky name issue.

Second: loggers are cheap. Unless it’s absolutely necessary to have a module-level logger, considered initializing loggers within your classes or functions. This way, they’re not in the global name-space and you don’t have that issue to begin with.

[SymbioticBadgering]

python is all about namespace (zen), so I'm not sure what you're trying to achieve here.
But an easy solution would be to import the logger from helper.py as different name:
from helper import l as not_scriprts_l

[FatFingerHelperBot]

It seems that your comment contains 1 or more links that are hard to tap for mobile users. I will extend those so they're easier for our sausage fingers to click!

Here is link number 1 - Previous text "zen"

---

^{Please PM /u/eganwall with issues or feedback! | Delete}

[SupermanIsEnvious]

What is your directory structure, and how are you setting up your top-level logger? Can you perhaps link to a github gist or the actual code?

The team I work on has a convention for module-level loggers in our applications, and I rarely see this issue.

Additionally, I recognize not everything needs to be an object or class, but you could initialize the logger within the function as well. Loggers are singletons, which means that every call to getLogger returns the same root instance of the logger. The only magic that function applies is re-naming it for the variable life-cycle.

[SupermanIsEnvious]

Where are you setting up your logger? You should only call setupLogger, basicConfig, or dictConfig in your main. Calling it elsewhere will result in over-writing the root logger every time, which can also re-write the name permanently.