Inconsisten version - Github Tags vs. _version.py

[jan-janssen]

The _version.py files are always one version behind, for example:
https://github.com/materialsproject/emmet/blob/v0.38.0/emmet-core/_version.py

[munrojm]

Yes, unfortunately this will always be the case as that version is updated after release using automated actions. We only use the version files for easy internal version detection in our code deployment pipelines.

That being said, the code in main will always be up to date with the latest release. Additionally, this should not affect users as code like

from emmet.core import __version__

will always show the correctly installed version.

[jan-janssen]

But it affects pip check.

[munrojm]

Can you provide me more details about what issue you are running into?

[jan-janssen]

I provided a pull request to demonstrate how currently the installation from source fails:
#565

[munrojm]

Perfect, thank you. I will take a look ASAP.

[munrojm]

One more change on my end. Once things look good I will close this issue.

[munrojm]

Reverted for now to fix deployment issues. Re-opening this until a new solution is found.

[jan-janssen]

The issue I have with the latest version is that the version is generated based on the git tag:

emmet-core 0.1.dev76+g7b6631a.d20221023.

rather than

emmet-core 0.36.4

[munrojm]

What is that messing up for you specifically?

[jan-janssen]

conda-forge/emmet-core-feedstock#18

[munrojm]

Hm, okay I will take a look.

[jan-janssen]

It seems this issue was fixed with the release of 0.38.9.