Remove custom_scope_suffix
parameter of Logfire.log
#399
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on the script below, it's about 20% faster to use
logfire.with_settings(custom_scope_suffix='my_scope')
rather thanlogfire.log(..., custom_scope_suffix='my_scope')
. That's not a huge difference, but I was expecting it to be bigger.The issue with
logfire.log(..., custom_scope_suffix=...)
is that it creates a new tracer each time. Fortunately these tracers go into aWeakKeyDictionary
so they don't stick around for long, but if this changed it could lead to a memory leak.Besides that,
custom_scope_suffix
is really only for very advanced users, so no need to bloat the API docs to make it more convenient.These aren't super strong reasons, but this seems like an improvement overall, and I'd like to make this change now before we release v1 of the SDK.