Introduce gpustat package

[wookayin]

I plan to switch to using a package, say gpustat, instead of writing everything in a single file gpustat.py.

As a lot of features are going to to added, I feel the necessity of doing this. In this way, we can also add (optional) features such as monitoring, web support, etc.

@Stonesjtu How do you think of this?

[Stonesjtu]

Can't agree more. The current main file has too many lines, and the single file executing makes little sense as dependencies are introduced in previous PR.

[Stonesjtu]

I think gpustat/gpustat.py is not clear enough, i recommend to use several separate files for clarification.

[Stonesjtu]

It would be better to put these classes in separate file e.g. gpu_stat_collection.py and gpu_stat.py.
So as the new_query and print_gpustat in utils.py

And I think the gpustat.gpustat is a little frustrating.
Naming conventions are to be discussed.

[wookayin]

gpustat.gpustat sounds funny, but I have no better naming. Having two files separately for those classes sounds too excessive, but agree with having print-related stuffs in a separate one.

[Stonesjtu]

When you have a package, you don't need the gpustat.py. A suggestion of file structure:

• gpu_stat_collection.py: classes GPUStat and GPUStatCollection
• display.py output.py or utils.py : the print-related stuffs (There are many lines related to that)
• main.py: the main function (currently .gpustat.main)

A reference: https://github.com/nicolargo/glances/

[wookayin]

Well, it is too verbose, and actually I am looking for something simple that can nicely embrace both classes.

[wookayin]

So we have core.py that implements the two classes, and __main__.py for some main-related stuffs (so that one can run via gpustat -m as well). Will merge soon.

[wookayin]

This is now on master.