-
-
Notifications
You must be signed in to change notification settings - Fork 1
enhance(s3): add suppor 10000 t in decorator, change module location #47
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think these changes will break other repos (energy-data, co2-data, poverty-data, and possibly etl, wherever datautils.io.s3
was used). Do you want to take care of refactoring accordingly?
@pabloarosado answering your points from #45 (review) that concern this PR.
That's correct. But if we keep it as it is, i.e.
I can see how this is getting into circular imports. |
@pabloarosado happy to refactor ー as long as we don't bump de version here and update the version dependency in |
I think bumping version here is irrelevant. I think all repos using datautils are specifying the version to install, so there's no danger for now. |
Codecov Report
@@ Coverage Diff @@
## main #47 +/- ##
==========================================
+ Coverage 87.45% 87.61% +0.15%
==========================================
Files 10 10
Lines 550 557 +7
==========================================
+ Hits 481 488 +7
Misses 69 69
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
owid.datautils.decorators.enable_file_download
owid.datautils.io.s3
-->owid.datautils.s3
. Why?s3
does not need to be something strictlyio
-related. Also, it might be a good practice to avoid circular imports betweenowid.datautils.io
andowid.datautils.decorators
:owid.datautils.io.json
andowid.datautils.io.archive
have imports fromowid.datautils.decorators
owid.datautils.decorators
has imports fromowid.datautils.s3