There are two places where a version is stated: ccxcon/settings.py and setup.py. We can store the version in a VERSION file and have that be the source of truth for the version, as a simple solution.
This also has the benefit of making updating the version as trivial as it can be with a release script (echo "$major.$minor.$patch" > VERSION)
But also, is there a reason we should keep setup.py? I'm cool with having it even just for onlookers who want to see some useful metadata, but I'm not sure if people will want to run CCXCon by installing it into a python environment (always possible, though). Thoughts?
I don't know many web apps that distribute their app via setuptools. There's clearly some metadata there, but I don't know that it's particularly useful. I'd be fine with not having it.
There are two places where a version is stated:
ccxcon/settings.py
andsetup.py
. We can store the version in aVERSION
file and have that be the source of truth for the version, as a simple solution.This also has the benefit of making updating the version as trivial as it can be with a release script (
echo "$major.$minor.$patch" > VERSION
)But also, is there a reason we should keep
setup.py
? I'm cool with having it even just for onlookers who want to see some useful metadata, but I'm not sure if people will want to run CCXCon by installing it into a python environment (always possible, though). Thoughts?