CHANGELOG

v0.3.4 (2024-12-27)

Bug Fixes

  • code_variables: Update yaml files, and rename some variables (9a7fd47)

v0.3.3 (2024-12-27)

v0.3.2 (2024-12-27)

Bug Fixes

  • code: Fix problems with code structure to enable ebtetr tests config and better notebook examples (750c455)

  • data: Add important data (15b2937)

v0.3.1 (2024-12-26)

v0.3.0 (2024-12-26)

Bug Fixes

  • code: Fix changelog.md and pyproject.toml (1e32042)

Features

  • code: Refactor code, and update package usage (1d55ae0)

  • readthedocs: Fix python version in yaml file (32b31ce)

v0.2.0 (2024-12-26)

Features

  • refacto: Proceed to refactorign, and some major bugs fixing (63040e3)

  • refacto: Refactor the code for better maintenance (585cbdc)

Refactoring

  • Add newline at end of file (283a64c)

It is recommended to put a newline at the end of the file.

  • Put docstring into a single line (982aeb3)

If a docstring fits in a single line (72 characters according to PEP8), it is recommended to have the quotes on the same line.

v0.1.4 (2024-12-05)

Bug Fixes

  • apis: Patch the call of open weather map api call (7b0d001)

  • dependencies: Correct notebook and fix some dependences (722507a)

  • docs: Fix notebook example (61312f8)

  • dvc: Fix local temporary storage to s3 storage (b7d89e7)

  • dvc: Second try to make sure the fix of Update weather.yml is working (3b17b9a)

  • dvc: Still trying to fix weather.yml by incorporating write issues permissions (f390cb0)

  • dvc: Update weather.yml (a322365)

  • dvc: Update weather.yml (1913c5a)

  • dvc: Update weather.yml (87380c6)

  • dvc: Update weather.yml (7bd44c8)

  • dvc: Update weather.yml (274289c)

  • dvc: Update weather.yml (323c3d8)

  • dvc: Update weather.yml (2f1ecdb)

  • dvc: Update weather.yml (5992e6f)

  • dvc: Update weather.yml (3b8fe11)

  • fixtures: Start using dvc for fixutres versioning (1015f21)

  • fixtures: Stop tracking tests/apis/fixtures/daily_weather.csv (bb56d80)

  • notebook: Fix notebboks (e0f4202)

  • notebook: Fix notebook (b112a9f)

  • notebook: Fix notebook execution during documentation building (8f3e13a)

  • notebook: Notebook rendering (6b76bb8)

  • notebook: Stiill fixing notebook and packages basics (4e45cd9)

  • notebook: Still fixing matplotlib impor tint the notebook (b3f3bd2)

  • notebook: Still fixing notebook (56676cd)

  • notebook: Still fixing notebook (e165275)

  • setup: Correct initial package setup (80f2923)

  • src: Create different folders to match different folders present in tests (7ee826f)

  • test: Create different folders of tests for different purposes (4a4f217)

  • test: Fix weather.yml to use dvc data (b51562a)

  • weather: Correct directory configurations for tests (8a3e780)

Chores

  • docs: Write docs (1813ff0)

  • readme: Add info to readme (11b0950)

  • readme: Fix equatiosn writing (c453581)

  • readme: Fix readme links (1c3991c)

Continuous Integration

Features

  • buildings: Fetch buildings dpe, and configure corresponding tests (7f5d7c7)

  • buildings: Finalize buildings necessary infos to proceed (7fc29a8)

  • buildings: Get a mapping of DPE into energy consumption (b2fbe4f)

  • costs: Compute daily energy costs (329ea6a)

  • dependencies: Resolving some dependencies conflicts (8af134e)

  • docs: Still fixing docs and notebook (12bb5d9)

  • dpt: Get department according to city (7d2f3d2)

  • notebook: Fixing notebook output (b718c54)

  • seasons: A simple function to determine the exact season based on a datetime obejct (80a41ef)

  • weather: Define apis to get weather information, with their corresponding tests (545fd5f)

Refactoring

  • Add newline at end of file (c4a410c)

It is recommended to put a newline at the end of the file.

  • Add newline at end of file (447cc09)

It is recommended to put a newline at the end of the file.

  • Add newline at end of file (e3771bb)

It is recommended to put a newline at the end of the file.

  • Add newline at end of file (fa7ed70)

It is recommended to put a newline at the end of the file.

  • Refactor unnecessary else / elif when if block has a return statement (d66698e)

The use of else or elif becomes redundant and can be dropped if the last statement under the leading if / elif block is a return statement. In the case of an elif after return, it can be written as a separate if block. For else blocks after return, the statements can be shifted out of else. Please refer to the examples below for reference.

Refactoring the code this way can improve code-readability and make it easier to maintain.

  • Refactor unnecessary else / elif when if block has a return statement (d443c4a)

The use of else or elif becomes redundant and can be dropped if the last statement under the leading if / elif block is a return statement. In the case of an elif after return, it can be written as a separate if block. For else blocks after return, the statements can be shifted out of else. Please refer to the examples below for reference.

Refactoring the code this way can improve code-readability and make it easier to maintain.

  • Refactor unnecessary else / elif when if block has a return statement (2dba06b)

The use of else or elif becomes redundant and can be dropped if the last statement under the leading if / elif block is a return statement. In the case of an elif after return, it can be written as a separate if block. For else blocks after return, the statements can be shifted out of else. Please refer to the examples below for reference.

Refactoring the code this way can improve code-readability and make it easier to maintain.

  • Remove unnecessary del statement from local scope (2e49b0f)

Passing a local variable to a del statement results in that variable being removed from the local namespace. When exiting a function all local variables are deleted, so it is unnecessary to explicitly delete variables in such cases.

  • Remove unnecessary f-string (c1b9417)

It is wasteful to use f-string mechanism if there are no expressions to be extrapolated. It is recommended to use regular strings instead.

  • Replace range(len(…)) with enumerate(…) (dd35420)

Using range(len(...)) is not pythonic. Python does not have not index-based loops. Instead, it uses collection iterators. Python has a built-in method enumerate which adds a counter to an iterable.