hi again, does the dagster logger allow lazy logging? it doesn't like having extra args for string formatting in the way the normal python logger does e.g.

<http://log.info|log.info>("the next train is at %s", never)

it doesn't at the moment

That isn't a thing in Python anymore

f strings aren't lazily evaluated though and errors in the string formatting are handled differently. a colleague has also had issues with log aggregation when log statements have f-strings though i have no experience with that https://medium.com/swlh/why-it-matters-how-you-log-in-python-1a1085851205

Not sure what you mean by lazy evaluation then

sorry, i have an appointment with some wine so I will come back to this on monday!

hah @Noah K in this case lazy evaluation just refers to the fact that IF relying on the inbuilt logging module - like @Josh Karlin posted in the original post - string formatting only happens if the logging level is hit - i.e. if you have very many DEBUG logs but your log level is INFO or WARNING etc, the DEBUG logs' strings won't get formatted. However if you format the string yourself, e.g. by using an f-string or

"something %s this" % "like"

then formatting happens when the execution goes over that line of code, whether or not it actually logs

You mean re: delaying the call to str?