Import export in CLI

[hhsecond]

Motivation and Context

Why is this change required? What problem does it solve?:

Introducing import-export utility over the command line

If it fixes an open issue, please link to the issue here:

This PR won't solve issue #72 completely but starting with image import and export. Also, the release is going to be experimental and the APIs are subjective to change

Description

Describe your changes in detail:

• Moving CLI as a module
• Introducing import option using click
• Introducing export option using click
• Base class for the introduction of plugin system

Types of changes

What types of changes does your code introduce? Put an x in all the boxes that apply:

• Documentation update
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Is this PR ready for review, or a work in progress?

• Ready for review
• Work in progress

How Has This Been Tested?

Put an x in the boxes that apply:

• Current tests cover modifications made
• New tests have been added to the test suite
• Modifications were made to existing tests to support these changes
• Tests may be needed, but they are not included when the PR was proposed
• I don't know. Help!

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have signed (or will sign when prompted) the tensorwork CLA.
• I have added tests to cover my changes.
• All new and existing tests passed.

[rlizzo]

Hey @hhsecond I took the code you started on and did a massive overhaul of it. Basically took heavy inspiration from scikit-image's plugin infrastructure and utility. The interface needs to be cleaned up a bit still, and we need tests, but both importing and exporting works!

Let me know what you think!

[hhsecond]

@rlizzo Wow! that's indeed massive. Are we pushing this in 0.2? I was thinking of a basic stable interface which we could push into 0.2

[rlizzo]

Why don't we push it to 0.3? We can make that a quick release.

If we're going to put it in 0.2 I'd rather not include a plugin the system (which we haven't had time to thoroughly review and test.) I suppose we could just hard code pillow is a dependency and only allow the file types that it could support. That would serve as a decent proof-of-concept?

What are your thoughts? Should we put a limited version in 0.2? Or just push it all to 0.3? (It'll be a short turn around time for that release)

[hhsecond]

@rlizzo do you wanna go back to my last commit and push that for 0.2
It has exactly this. Only pillow loader nothing else. Then we can keep your updates for 0.3?

[codecov]

Codecov Report

Merging #103 into master will decrease coverage by 0.38%.
The diff coverage is 86.84%.

@@            Coverage Diff             @@
##           master     #103      +/-   ##
==========================================
- Coverage   92.54%   92.16%   -0.38%     
==========================================
  Files          51       59       +8     
  Lines        9448     9858     +410     
  Branches      930      990      +60     
==========================================
+ Hits         8743     9085     +342     
- Misses        511      561      +50     
- Partials      194      212      +18

Impacted Files	Coverage Δ
src/hangar/remote/config.py	70.37% <ø> (+0.81%)	⬆️
tests/test_cli.py	100% <100%> (ø)	⬆️
tests/test_cli_plugin.py	100% <100%> (ø)
src/hangar/cli/__init__.py	100% <100%> (ø)
src/hangar/repository.py	96.52% <100%> (+6.92%)	⬆️
tests/test_cli_io.py	100% <100%> (ø)
src/hangar/cli/io/__init__.py	100% <100%> (ø)
src/hangar/cli/io/_io.py	50% <50%> (ø)
src/hangar/cli/io/_plugins/pil_plugin.py	50% <50%> (ø)
src/hangar/cli/io/_plugins/matplotlib_plugin.py	81.82% <81.82%> (ø)
... and 16 more

[rlizzo]

Hey @hhsecond can you give this a review? The tests are passing now (even though a few more are needed) and the quality is close to where I'm OK with it for the time being.

[hhsecond]

Overall looks good. I would say we need a PluginManager class eventually instead of several functions and few global containers floating around. What do you think?

[rlizzo]

Ok. Going to merge this now.