René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Question Regarding Global Statements","articleBody":"Hello! \r\n\r\nI wanted to read more on the references on this page https://docs.quantifiedcode.com/python-anti-patterns/maintainability/using_the_global_statement.html\r\n\r\nI know the book entails things you should \"NEVER\" do in practice. So I ask this in the context of putting things in the global scope.\r\n\r\nDo we consider instantiating built in modules like logger anti patterns? Or should this be something that should be encapsulated in its own class.\r\n\r\n```\r\nimport logging\r\nlogging.basicConfig(level=logging.INFO)\r\nlogger = logging.getLogger(__name__)\r\n```\r\n\r\nOr perhaps this was meant to deter a developer from using the `global` statement. \r\n\r\nThe logging function is something I want to instantiate on any files that logs and it seems safe if I define it everywhere. \r\n```The logging module is intended to be thread-safe without any special work needing to be done by its clients. It achieves this though using threading locks; there is one lock to serialize access to the module’s shared data, and each handler also creates a lock to serialize access to its underlying I/O.```\r\nhttps://docs.python.org/3/library/logging.html#thread-safety","author":{"url":"https://github.com/Keydex","@type":"Person","name":"Keydex"},"datePublished":"2021-02-07T14:42:09.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/154/python-anti-patterns/issues/154"}