Provide __version__ attribute

[shoyer]

It's a convention for Python projects to set the __version__ attribute to a string representing the current version. This facilitates debugging and version checking by downstream projects (e.g., xarray).

[alexamici]

@shoyer I'm using zest.releaser for version management and they suggest adding this snippet to cfgrib/__init__.py:

import pkg_resources

__version__ = pkg_resources.get_distribution('cfgib').version

in order to still keep one single master version in setup.py. Would that work for you?

[shoyer]

I'm sure that would work fine.

…

On Mon, Nov 12, 2018 at 2:57 AM Alessandro Amici ***@***.***> wrote: @shoyer <https://github.com/shoyer> I'm using zest.releaser <https://zestreleaser.readthedocs.io/en/stable/> for version management and they suggest <https://zestreleaser.readthedocs.io/en/stable/versions.html#using-the-version-number-in-setup-py-or-setup-cfg-as-version> adding this snippet to cfgrib/__init__.py: import pkg_resources __version__ = pkg_resources.get_distribution('cfgib').version in order to still keep one single master version in setup.py. Would that work for you? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#31 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABKS1mPR4S9C0jwBSH_CGAgZxRsV6M7Gks5uuVQLgaJpZM4YYsW5> .

[alexamici]

Ok, things got a bit more complicated than that, but now cfgrib.__version__ return the currently installed version.

Will be in the next release.

[alexamici]

That was too fast. Current master has a circular import problem that prevents setting __version__.

[shoyer]

versioneer is one commonly used tool for this: https://github.com/warner/python-versioneer

(We use it in xarray, pandas and dask)

[alexamici]

Looks like I could implement the single-sourcing the package version using method 1 of: https://packaging.python.org/guides/single-sourcing-package-version/

Trying to close again.