Logging displays every module as "logging.py"

[carver]

What is wrong?

eg~

  DEBUG2  03-29 10:00:50            logging.py  Setting decoded storage in account 0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa & slot 1 to value 2
  DEBUG2  03-29 10:00:50            logging.py  Setting decoded storage in account 0xbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb & slot 1 to value 2
  DEBUG2  03-29 10:00:50            logging.py  commit all checkpoints
  DEBUG2  03-29 10:00:50            logging.py  Setting storage key 0xb10e2d527612073b26eecdfd717e6a320cf44b4afac2b0732d9fcbe2b7fa0cf6 to value 0x02
  DEBUG2  03-29 10:00:50            logging.py  Setting storage key 0xb10e2d527612073b26eecdfd717e6a320cf44b4afac2b0732d9fcbe2b7fa0cf6 to value 0x02
  DEBUG2  03-29 10:00:50            logging.py  Setting decoded storage in account 0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa & slot 3 to value 4
  DEBUG2  03-29 10:00:50            logging.py  Setting decoded storage in account 0xbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb & slot 3 to value 5
  DEBUG2  03-29 10:00:50            logging.py  commit all checkpoints
  DEBUG2  03-29 10:00:50            logging.py  Setting storage key 0xc2575a0e9e593c00f959f8c92f12db2869c3395a3b0502d05e2516446f71f85b to value 0x04
  DEBUG2  03-29 10:00:50            logging.py  Setting storage key 0xc2575a0e9e593c00f959f8c92f12db2869c3395a3b0502d05e2516446f71f85b to value 0x05

How can it be fixed

Probably just a weird logging config thing, didn't get a chance to look yet.

Vaguely related: maybe move the HasExtendedDebugLogger (or whatever it's called) from trinity into eth-utils and use that here.

[pipermerriam]

a little bike-sheddy

Maybe the logging thing belongs in it's own library (feels kind of odd in eth-utils...). I searched for a while and was surprised that there aren't any well established libraries for this.