Add tag for conda-build.

[skrah]

The conda version string relies on at least one tag, currently we get (https://anaconda.org/xnd/xndtools/files):

xndtools-0.2.0dev3-py36_NA.tar.bz2

With a tag we should get something like:

libndtypes-0.2.0dev3-py36_153_g9b6806c.tar.bz2

Any named tag is fine, I'm using v0.2.0b2, meaning that dev3 will lead either to b3or to a release.

[skrah]

The tag only needs to be in xndtools, the subtrees in xnd-all should not have tags I think.

[pearu]

Where do you add the tag? I'd like to use a tag derived from git commit id.

[pearu]

@skrah Note that 0.2.0dev3 does not comply PEP 440,
it should read 0.2.0.dev3.

[skrah]

I know, but I think I had some conda issues with 0.2.0.dev3 (conda may have normalized something, I don't recall exactly), but try 0.2.0.dev3.

I missed the v0.2.0dev3 tag in ndtypes, so I'd do in xndtools:

$ git tag "v0.2.0dev3" -a
$ git describe --tags
v0.2.0dev3

Conda uses git describe --tags, so after the next commit you get the commit id automatically:

$ vi README.md 
$ git add -u
$ 
$ git commit
[master 5dee7da] Example commit.
 1 file changed, 1 deletion(-)
$ 
$ git describe --tags
v0.2.0dev3-1-g5dee7da

[skrah]

It may also have been distutils issues with 0.2.0.dev3. I just recall that something did not work, perhaps even uploading to PyPI.

[pearu]

In xndtools I am using 0.2.0.dev3 because when using PYTHONWARNINGS=default then I remember seeing a warning that 0.2.0dev3 is converted to 0.2.0.dev3.
I'll keep using it to see where it causes problems.

[skrah]

Yes, let's watch it.