Not really.  The verbosity level can be 0-3 for management commands.  In the logging library is can be 0, 10, 20, 30, 40, and 50.  That's not really an even mapping, especially considering that we don't even use the CRITICAL or WARNING levels.  Also, the default verbosity level for management commands is `1`.  Thus, logging.INFO should map to the default verbosity level.  There are no more logging levels above that besides DEBUG.  It seems way simpler to me to just have this small dict and use it for explicit mapping of verbosity to log levels.