These are chat archives for SHTOOLS/SHTOOLS
localizedspectralanalysisinto one subpackage
spectralto avoid long names?
shwindow.pyinto something like
coresubpackage? I mean, there will be another classes...
spectralanalysis. Let me think about shortening it even more....
shcoeffsgrid. I don't really care what the subpackage name is that hold the classes. Are there any other ideas?
concerning the release procedure, I just noted this in the setup.py file
# This flag has to be True if the version number indicated in the file # VERSION has already been released and to False if this is a development # version of a future release. ISRELEASED = True
Should we set this to false on the develop branch? And if not, perhaps we should clarify what this means. It is not really clear to me...
setup.pywill try to get version from tag first, next it will try to check if there any changes were made from tag's commit. If not, then version is equal to the tag, if yes, then it'll add
.postto version if isreleased is True and
.devif it is not True.
.postis supposed to be used for small changes after major release and
.devis for development stage in which we are now. So, now, nearly before release, we should change it to False and change version in VERSION file to 4.0. This versioning system actually does not welcome any
ISRELEASED=False. If something will needed to be changed in master, then a new branch can be created for this purpose. In other words,
developis always for the next release