reverse(...) is better than using
reverse_lazy(...) when the url is being reversed after
URLConf has been loaded.
Django looks up the URL name as defined in
URLConf to generate the URL. There are times when we want to use a URL before the
URLConf has been loaded, such as:
URLConf has been loaded there is no need to use
reverse_lazy(...) - just use
reverse(...), becasue doing otherwise adds unecessary complexity.
If our GitHub code review bot spots this issue in your pull request it gives this advice:
Code Review Doctor will run this check by default. No configuration is needed but the check can be turned on/off using check code
reverse-lazy-misuse in your pyproject.toml file.