Maintenance: split ndinterp long __init__.py file functions into separate files #416
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #415
The
__init__.pyfile of thedask_image.ndinterphas become very large (~780 lines), and currently contains five public API functions, plus associated helper functions. This is not ideal, since bigger files are harder to understand and maintain, and if anyone else adds a new function to thendinterppackage it'll push the file size over what's generally considered best practice (pylint suggests a maximum line limit of around 1000)To avoid future problems, in this PR I've split the ndinterp init.py file into separate smaller files while keeping the git history preserved for each line. Now you can more easily see which part of the code is the most relevant, and each file is a more manageable size (roughly150-250 lines).
I followed this guide to split the files while still preserving the full git history.