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.
#2436 greatly simplified how logging is set up in Flask. Part of that removed the
LOGGER_NAME
config and hard-coded"flask.app"
. However, #2866 points out that due to this it is no longer possible to distinguish logs when dispatching multiple apps.This partially reverts the logger name behavior change from 1.0. There is still no config, but the logger's name is now the same as
app.name
(basically the value passed toFlask(import_name)
).The information that's currently logged does make sense as coming from the user's project rather than Flask itself, although we may introduce the
"flask.app"
logger again in the future for logging things truly internal to Flask and not the user's app.This may require projects to update their logging config to reference their app's name instead of
"flask.app"
.Closes #2866