feat: Add version number and checks

[KelvinChung2000]

Add the package version when creating a project. If the project version is less than the starting version, add a warning during package setup.

It can further improve to raise errors when the project version and the package version have major version differences. But this can be done later.

[IAmMarcelJung]

Cool, thanks for this! :) The fabulous version that is written to the file is a bit weird (it shows 0.0.post754 for me), but I guess this due to the current python setup?

[KelvinChung2000]

I am showing 1.0.post157+dirty. Maybe I am on a more recent install?

Let's delay the merge until we do the release. I don't want to rebase again.

[IAmMarcelJung]

Okay then probably I did something wrong although I just cloned your fork and checked out your version-check branch and did the usual pip install -r requirements.txt and pip install -e . installaton process in a fresh venv.

Delaying the merge might make sense as I think you put a lot of effort into the rebase and this should indeed not be done too often :)

[KelvinChung2000]

This could be due to the branch checkout. But ultimately, this should not matter.

[IAmMarcelJung]

Okay so you also implemented the change in the master? Or what do you mean? As you said it does not matter but I personally would like to understand what happens and if I probably did something wrong.

[KelvinChung2000]

I implemented the change in the development. The installation will depend on the pyproject.toml, and the version is automatically decided by it.

[EverythingElseWasAlreadyTaken]

Okay so you also implemented the change in the master? Or what do you mean? As you said it does not matter but I personally would like to understand what happens and if I probably did something wrong.

You did nothing wrong, for a clean venv with Kelvins branch, it should be 0.0.post754, I guess. At least its also the same for me. This is just how the versioning with seuptools is configured and when you did the pip install -e . for your current venv.

The version Kelvin showed, seems to have some artifacts from whenever he installed FABulous in his venv.

It's all based on the git history. The first numbers 0.0 shows the last tags in the git history and for me, there were no tags on Kelvins repo, this is 0.0. The post754 is the number of commits after the latest tag. The +dirty means, that there were uncommitted changes while the installation.

Here can you find more information about versioning: https://setuptools-git-versioning.readthedocs.io/en/stable/schemas/tag/dirty_version.html

[EverythingElseWasAlreadyTaken]

I think it's a bit too much simplified, if we just check if project version is not newer than your current fabulous version. Older fabulous versions can't handle newer projects as well.

I'm also not sure, if we should check for the whole version string, technically breaking changes should only happen in major releases.

I think we should at least not throw warnings for patch, and dirty versions.

[KelvinChung2000]

I will make the changes once we decide what we want for versioning. Probably using something like packaging should allow us to do more fine control.

[EverythingElseWasAlreadyTaken]

This is a really nice improvement!

We should discuss, how we treat the versioning for the checks.