Closed philngo closed 7 years ago
What if logging emitted to a named logger instead? e.g.
logger = logging.getLogger("eemeter") https://docs.python.org/3.1/library/logging.html
Then you can attach to that logger if you want the logs. Seems a little more flexible than emitting the blob of logs in the meter run results.
Yeah, you're right. The logging stuff as set up right now is over-engineered and over-restrictive. Let's go with the more standard method you describe, but maybe we should use logger = logging.getLogger(__name__)
.
This is a release candidate for eemeter 0.4. It includes a large set of updates at every layer, including in basic data structures, import/export tooling, weather handling and caching, meter structure, and logging.
Weather:
Energy Traces:
ConsumptionData
toEnergyTrace
, which recognize that not all the energy data we process is actually "Consumption."Serializer
s fromEnergyTrace
objectsMeters:
Period
withIntervention
periods andModelingPeriod
s. This adds future proofing for as we develop ways to handle different projectsModelingPeriodSet
s andEnergyTraceSet
sFormatter
Validator
, andModel
interfaces, allowing more precise and predictable definitions models.CI tooling:
Documentation: