`version.py` in version control

[felixhekhorn]

RE the version file, I've reverted it back. imho there's no perfect solution, but what we do in NNPDF/nnpdf is to create a fake _version.py at build time, which gets ignored and imported by the real version.py https://github.com/NNPDF/nnpdf/blob/bf9a8ec9ab0cc3a4bb356732efc1c9077983b06d/pyproject.toml#L121

thinking about this perhaps it would be better if pre-commit would ensure that it gets back to 0.0.0? I wonder whether there's a ready made hook for that...

Originally posted by @scarlehoff in #470 (comment)

[felixhekhorn]

we should also check if this is the intended behaviour:

not sure why but poetry lock fills the version.py files

[evagroenendijk]

@felixhekhorn Could you elaborate a little bit on what is the problem? It's not entirely clear to me, at a first glance for me the versioning seems to work fine. Thanks!

[felixhekhorn]

The question is if that file should be under version control or not. At nnpdf (I understand from the comment above) this is not the case, but here it is - which one is correct? As you can check from #470 some manual work was needed (e.g. 03bcbc1) - why? Did I do something wrong there? Let's also check what other projects do.

This issue may or may not require changes in the code, but we should sort out the correct behaviour here and document that.