Add VACUMM to UV-CDAT

[stefraynaud]

How about adding VACUMM to UV-CDAT since mandatory dependecies are already satisfied ?
Here is the up-to-date web site: http://relay.actimar.fr/~raynaud/vacumm/ (the officiel one is http://www.ifremer.fr/vacumm).
It makes an intensive usage of (UV-)CDAT and may have its place here too.

[doutriaux1]

I like this idea! Adding this to 2.0 milestone. Will let you know as soon as I have added it to the build, so that you can test it.

[doutriaux1]

I'm fine with using the tarball. But if you want to switch to git repo then we can use that as well/instead

[stefraynaud]

The management of VACUMM also depends on the IFREMER side, and they have not git on their forge.
Thus, lets work on tarballs for the moment.

VACUMM also used a few other optional packages:

• paramiko (for SSH connexions).
• xlwt (that usually goes with xlrd and xlutils).

[doutriaux1]

Do these need to be installed BEFORE we install VACCUM or can they be installed after the fact?

[stefraynaud]

They can be installed AFTER because they are optional.

[aashish24]

@stefraynaud I am ok with adding this to the UV-CDAT if by default it would be Off. We are trying to downsize the core packages of UV-CDAT so that it is more accessible. I hope you understand. Thanks for the suggestion.

[stefraynaud]

Ok, no problem.

What would be a reasonable maximal size for allowing a new package?

[doutriaux1]

I think it is more about the number of dependencies it brings in rather than the size. Any pure python will most likely be fine. If I had to put a "size limit" I guess I'd say no worries up to 5Mb, 15-20Mb would start to trigger some attention, above that it would probably need to be widely used.

[durack1]

@doutriaux1 you might want to review this and reset it back to a 2.2 milestone if all goes well with travis

[durack1]

@doutriaux1 @aashish24 this also requires configobj and six to be installed - I'll issue another PR to bring this right up to date tomorrow

[durack1]

@doutriaux1 @aashish24 this issue should really be reopened until I've solved these additional dependencies..

[aashish24]

Ah, I checked the setup.py and I didn't see those requirements. Should I revert the merge?

[aashish24]

Okay, I have reset so that it is no longer in master now.

[durack1]

@aashish24 @doutriaux1 great, I'll fix this up and reissue a PR to bring things inline..

[durack1]

@aashish24 @doutriaux1 this should be good to go #1089

[durack1]

@aashish24 @doutriaux1 let's wait with #1089 until we get an all clear from @stefraynaud, apparently pytz was needed in the most recent vacumm version.