Jun-te Kim 7aea692521 historic EPC: read via infrastructure/s3, not the utils.s3 utility ... HistoricEpcS3Repository reached into utils/s3.py (read_csv_gz_from_s3 + parse_s3_uri), the legacy utility that self-constructs boto3 inside free functions. The other S3 repositories deliberately depend on the infrastructure/s3 layer instead (UnstandardisedAddressListCsvS3Repository injects a CsvS3Client). Bring historic EPC into line. - Add GzipCsvS3Client(S3Client) in infrastructure/s3: read_csv_gz(key) -> DataFrame (get_object + gzip decode). - Inject it into HistoricEpcS3Repository; the bucket lives in the client and the repo only builds the per-postcode key + maps rows (no S3/HTTP code). Add with_default_s3_client(s3_root) for composition roots. - Update main.py and the match_addresses_for_postcode seam to the factory. - Repo tests inject a real GzipCsvS3Client over a controlled boto stub (exact key assertions + AccessDenied); add a moto-based client test and a factory test covering s3_root -> bucket+key. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MQE5TsSuQTeNSCSz9A9GQf		2026-06-30 09:19:57 +00:00
..
epc	historic EPC: read via infrastructure/s3, not the utils.s3 utility	2026-06-30 09:19:57 +00:00
__init__.py	further breaking up code	2023-07-20 12:24:34 +01:00
datatypes.py	further breaking up code	2023-07-20 12:24:34 +01:00
enums.py	completed build of new demo portfolio - some fixed required still	2023-11-20 14:42:16 +00:00