Fixed generation of bilby_pipe/.version file

This patch fixes the generation of bilby_pipe/.version, especially when not building from the git repository (this was previously broken).

This does introduce a library change, namely that bilby_pipe.__version__ will now just contain the X.Y.Z version number, and not the git build information.

It looks like this failed due to the formatting. We added a code formatting checker (see https://lscsoft.docs.ligo.org/bilby_pipe/structure.html#code-format for details) the quick fix is to run something like

$ pip install black
$ black filename.py

added 2 commits

• 0e2704ab - bilby_pipe: store just the X.Y.Z version in __version__
• fe3bf870 - ci: print diffs in black check

Compare with previous version

Just to double check, the git has is still included for development installation, but not for the pip-installed version? If so that makes sense to me.

I don't really understand. For releases the git version information is frozen when the tarball is generated (presumably by you). So, whatever content is included at that time is included in the pip-installed versions.

Apologies, I wasn't very clear. I think I've understood now.

So for the "released" version, there will be no git hash (that makes sense), but I just wanted to check that if I installed the development version, there would still be a "git hash" appended to the version information. Looking at the code, I'm certain that the answer is yes so this is good to go.

approved this merge request

merged

mentioned in commit 50076d0e