Open anders-kiaer opened 5 years ago
A good way forward could probably be to use automatic Travis pypi deployment every time there is version tag release in this github repository. This is how segyio
has done it as well.
To get all webviz
functionality in this repository installed it should probably be enough for the user to do pip install webviz
.
Currently there are many setup.py
files in the repository. Advantages of this includes
webviz
.Currently every setup.py
in this repository has a version number, which is not updated in practice (rather the webviz
overall version number is increased).
Should we remove the version
flag of each individual setup.py
, and instead have a setup.py
at root level collecting content of the different setup.py
deeper in the directory structure automatically? As long as we are in the same github repository, it requires some bookkeeping probably to use the github tag release system together with individual version number of each setup.py
(which anyway looks to not be updated).
A placeholder for webviz
is reserved at pypi
, while waiting for real deployment from the pypi
account statoil-travis.
Getting
webviz
onpypi
would make it easier and quicker for end users, as well as for other softwares depending onwebviz
, to get it installed.