When import telegramify_markdown, the log record is invalid.

[finn-chan]

I set up logging in the program:

if settings.LOG_ENABLED:
    log_dir = os.path.dirname(settings.LOG_FILE_PATH)
    os.makedirs(log_dir, exist_ok=True)

    logging.basicConfig(
        level=logging.INFO,
        format='%(asctime)s - %(levelname)s - %(message)s',
        handlers=[
            logging.FileHandler(settings.LOG_FILE_PATH, mode='a'),
            logging.StreamHandler()
        ]
    )

I found that after I imported this library, I couldn't log to the file (but I could see the log content in the console).

Even if I block it, it still affects the log.

logging.getLogger('telegramify_markdown').setLevel(logging.CRITICAL)

How can I set it up?

[sudoskys]

Hmm seems to be causing some problems. I will remove the logger in the next version

Before that, you can import

telegramify_markdown.logger.logger to set it

https://github.com/sudoskys/telegramify-markdown/blob/main/src/telegramify_markdown/logger.py

[neutron-nerve]

Issue Report: Invalid Log Record upon Importing telegramify_markdown

Issue Overview

An issue was reported regarding the telegramify_markdown library affecting the logging system of the importing program. Specifically, after importing telegramify_markdown, log entries were not being recorded to a file as intended, although they appeared in the console. The attempt to adjust the log levels for the telegramify_markdown library using:

logging.getLogger('telegramify_markdown').setLevel(logging.CRITICAL)

did not resolve the issue.

Root Cause

The problem stemmed from the internal logger configuration within the telegramify_markdown library, which interfered with the existing logging setup of the main application.

Proposed Solution

The project maintainer, @sudoskys, acknowledged the issue and planned to remove the logger in the subsequent version of the library. As an interim solution, users were advised to manually adjust the logging settings by directly importing the library's logger:

import telegramify_markdown.logger.logger

This approach allowed users to reconfigure or disable the logger in a manner that harmonizes well with their own logging setups.

Final Outcome

The issue was formally closed on January 3, 2025, following the proposed interim workaround and the commitment to remove the conflicting logger in future iterations of the library.

Acknowledgments

We express our gratitude to @finn-chan for identifying the issue and to @sudoskys for providing a timely workaround and planning a permanent resolution.

[sudoskys]

We changed the logger to loguru global logger which is easier to configure.