Tracking variable whereabouts in a plugin

Please provide more information to help us understand the issue:

• Type: question
• Referecenes:
  • question
  • orig PR
• Expected behavior: being able to track down variable i.e. from a process it was initialized.
  Code below should illustrate an expected behavior.
• Actual behavior: n/a
• mypy version: >=0.770

from luguru import logger

LOG_A = logger.opt(lazy=False)
LOG_B = logger.opt(lazy=True)

LOG_A.info('Test {}', lambda x: x)    # should work
LOG_B.info('Test {}', lambda x: x)    # error

logger.opt(lazy=False).info('Test {c}', c=lambda x: x)  # should work
logger.opt(lazy=True).info('Test {d}', d=lambda x: x)   # error

In short: with loguru you can use Callable[[], Any] for lazy loggers to avoid costly computations. But those have to be non-argument callables. Above you can find non-lazy loggers that will work just fine by doing str(callable). In other words, to rephrase question from above, how can we:

track a variable/object on which behalf a method was called?

This is quite vital because type checking cannot be done solely on a method call level because we need something from another call. There is opt method being called but having call details from it without anything to tie them to will not help too much.

Inizia esaminando la domanda collegata su loguru-mypy e la pull request originale di loguru, quindi analizza come mypy gestisce le chiamate concatenate opt(...).info(...) mostrate qui. L’issue non identifica alcun file, test o approccio di implementazione definito; per considerarla completata sarebbe necessario concordare un modo per tracciare l’oggetto logger attraverso queste chiamate e definire chiaramente un caso di validazione.