-
Notifications
You must be signed in to change notification settings - Fork 31
Project versioning: Use versioningit
#757
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Important Review skippedAuto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
crate-2.0.0.post42+g1c30e65.d20251220.tar.gz crate-2.0.0.post42+g1c30e65.d20251220-py3-none-any.whl
>>> import crate.client >>> crate.client.__version__ '2.0.0.post43+g7ceffbb.d20251220'
- Removes buildout; test_layer now fetches the crate package itself - Removes setup.py - Removes stale bin/test - Removes stale requirements.txt - Updates DEVELOP.rst - Removes poethepoet. Most python developers are familiar with `ruff`, `mypy` and `pytest`, no need to add an extra DSL on top that obfuscates what's being used. - Removes `bootstrap.sh`. `python -m venv` or `uv venv` are trivial enough and Python developers should be familiar with them. - Removes the `devtools/create_tag.sh` script. It used `python setup.py --version` to get the new version, which since #757 was broken - running into a chicken and egg problem: Can't read the version from git to when about to create a new version tag. Must use `git tag -s <version>` instead. - Updates the release job, which used `python -m build`, which wasn't specified as dependency anywhere. `hatch` is now used which `uv build` will pickup.
- Removes buildout; test_layer now fetches the crate package itself - Removes setup.py - Removes stale bin/test - Removes stale requirements.txt - Updates DEVELOP.rst - Removes poethepoet. Most python developers are familiar with `ruff`, `mypy` and `pytest`, no need to add an extra DSL on top that obfuscates what's being used. - Removes `bootstrap.sh`. `python -m venv` or `uv venv` are trivial enough and Python developers should be familiar with them. - Removes the `devtools/create_tag.sh` script. It used `python setup.py --version` to get the new version, which since #757 was broken - running into a chicken and egg problem: Can't read the version from git to when about to create a new version tag. Must use `git tag -s <version>` instead. - Updates the release job, which used `python -m build`, which wasn't specified as dependency anywhere. `hatch` is now used which `uv build` will pickup.
- Removes buildout; test_layer now fetches the crate package itself - Removes setup.py - Removes stale bin/test - Removes stale requirements.txt - Updates DEVELOP.rst - Removes poethepoet. Most python developers are familiar with `ruff`, `mypy` and `pytest`, no need to add an extra DSL on top that obfuscates what's being used. - Removes `bootstrap.sh`. `python -m venv` or `uv venv` are trivial enough and Python developers should be familiar with them. - Removes the `devtools/create_tag.sh` script. It used `python setup.py --version` to get the new version, which since #757 was broken - running into a chicken and egg problem: Can't read the version from git to when about to create a new version tag. Must use `git tag -s <version>` instead. - Updates the release job, which used `python -m build`, which wasn't specified as dependency anywhere. `hatch` is now used which `uv build` will pickup.
- Removes buildout; test_layer now fetches the crate package itself - Removes setup.py - Removes stale bin/test - Removes stale requirements.txt - Updates DEVELOP.rst - Removes poethepoet. Most python developers are familiar with `ruff`, `mypy` and `pytest`, no need to add an extra DSL on top that obfuscates what's being used. - Removes `bootstrap.sh`. `python -m venv` or `uv venv` are trivial enough and Python developers should be familiar with them. - Removes the `devtools/create_tag.sh` script. It used `python setup.py --version` to get the new version, which since #757 was broken - running into a chicken and egg problem: Can't read the version from git to when about to create a new version tag. Must use `git tag -s <version>` instead. - Updates the release job, which used `python -m build`, which wasn't specified as dependency anywhere. `hatch` is now used which `uv build` will pickup.
- Removes buildout; test_layer now fetches the crate package itself - Removes setup.py - Removes stale bin/test - Removes stale requirements.txt - Updates DEVELOP.rst - Removes poethepoet. Most python developers are familiar with `ruff`, `mypy` and `pytest`, no need to add an extra DSL on top that obfuscates what's being used. - Removes `bootstrap.sh`. `python -m venv` or `uv venv` are trivial enough and Python developers should be familiar with them. - Removes the `devtools/create_tag.sh` script. It used `python setup.py --version` to get the new version, which since #757 was broken - running into a chicken and egg problem: Can't read the version from git when about to create a new version tag. Must use `git tag -s <version>` instead. - Updates the release job. It used `python -m build`, which wasn't specified as dependency anywhere. `hatch` is now used which `uv build` will pickup.
- Removes buildout; test_layer now fetches the crate package itself - Removes setup.py - Removes stale bin/test - Removes stale requirements.txt - Updates DEVELOP.rst - Removes poethepoet. Most python developers are familiar with `ruff`, `mypy` and `pytest`, no need to add an extra DSL on top that obfuscates what's being used. - Removes `bootstrap.sh`. `python -m venv` or `uv venv` are trivial enough and Python developers should be familiar with them. - Removes the `devtools/create_tag.sh` script. It used `python setup.py --version` to get the new version, which since #757 was broken - running into a chicken and egg problem: Can't read the version from git when about to create a new version tag. Must use `git tag -s <version>` instead. - Updates the release job. It used `python -m build`, which wasn't specified as dependency anywhere. `hatch` is now used which `uv build` will pickup.
- Removes buildout; test_layer now fetches the crate package itself - Removes setup.py - Removes stale bin/test - Removes stale requirements.txt - Updates DEVELOP.rst - Removes poethepoet. Most python developers are familiar with `ruff`, `mypy` and `pytest`, no need to add an extra DSL on top that obfuscates what's being used. - Removes `bootstrap.sh`. `python -m venv` or `uv venv` are trivial enough and Python developers should be familiar with them. - Removes the `devtools/create_tag.sh` script. It used `python setup.py --version` to get the new version, which since #757 was broken - running into a chicken and egg problem: Can't read the version from git when about to create a new version tag. Must use `git tag -s <version>` instead. - Updates the release job. It used `python -m build`, which wasn't specified as dependency anywhere. `hatch` is now used which `uv build` will pickup.
- Removes buildout; test_layer now fetches the crate package itself - Removes setup.py - Removes stale bin/test - Removes stale requirements.txt - Updates DEVELOP.rst - Removes poethepoet. Most python developers are familiar with `ruff`, `mypy` and `pytest`, no need to add an extra DSL on top that obfuscates what's being used. - Removes `bootstrap.sh`. `python -m venv` or `uv venv` are trivial enough and Python developers should be familiar with them. - Removes the `devtools/create_tag.sh` script. It used `python setup.py --version` to get the new version, which since #757 was broken - running into a chicken and egg problem: Can't read the version from git when about to create a new version tag. Must use `git tag -s <version>` instead. - Updates the release job. It used `python -m build`, which wasn't specified as dependency anywhere. `hatch` is now used which `uv build` will pickup.
- Removes buildout; test_layer now fetches the crate package itself - Removes setup.py - Removes stale bin/test - Removes stale requirements.txt - Updates DEVELOP.rst - Removes poethepoet. Most python developers are familiar with `ruff`, `mypy` and `pytest`, no need to add an extra DSL on top that obfuscates what's being used. - Removes `bootstrap.sh`. `python -m venv` or `uv venv` are trivial enough and Python developers should be familiar with them. - Removes the `devtools/create_tag.sh` script. It used `python setup.py --version` to get the new version, which since #757 was broken - running into a chicken and egg problem: Can't read the version from git when about to create a new version tag. Must use `git tag -s <version>` instead. - Updates the release job. It used `python -m build`, which wasn't specified as dependency anywhere. `hatch` is now used which `uv build` will pickup.
About
Use versioningit like with other projects, to have more granular versioning, directly based on Git tags, so releasing no longer needs the version bumping step, among other goodies.
Details
The more granular versioning condensates on built artefacts, and the built-in module
__version__inquiry.