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.

まず、リンク先の loguru-mypy の質問と loguru の元の pull request を確認し、その後、ここに示されている連鎖した opt(...).info(...) 呼び出しを mypy がどのように処理するかを調べます。この issue ではファイル、テスト、または確定した実装方針が特定されていません。完了するには、これらの呼び出し全体で logger オブジェクトを追跡するための合意された方法と、明確に定義された検証ケースが必要です。