README.rst 6.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183
  1. Incremental
  2. ===========
  3. |gha|
  4. |pypi|
  5. |coverage|
  6. Incremental is a small library that versions your Python projects.
  7. API documentation can be found `here <https://twisted.org/incremental/docs/>`_.
  8. .. contents::
  9. Quick Start
  10. -----------
  11. Using setuptools
  12. ~~~~~~~~~~~~~~~~
  13. Add Incremental to your ``pyproject.toml``:
  14. .. code-block:: toml
  15. [build-system]
  16. requires = [
  17. "setuptools",
  18. "incremental>=24.7.2", # ← Add incremental as a build dependency
  19. ]
  20. build-backend = "setuptools.build_meta"
  21. [project]
  22. name = "<projectname>"
  23. dynamic = ["version"] # ← Mark the version dynamic
  24. dependencies = [
  25. "incremental>=24.7.2", # ← Depend on incremental at runtime
  26. ]
  27. # ...
  28. [tool.incremental] # ← Activate Incremental's setuptools plugin
  29. It's fine if the ``[tool.incremental]`` table is empty, but it must be present.
  30. Remove any ``[project] version =`` entry and any ``[tool.setuptools.dynamic] version =`` entry.
  31. Next, `initialize the project`_.
  32. Using Hatchling
  33. ~~~~~~~~~~~~~~~
  34. If you're using `Hatchling <https://hatch.pypa.io/>`_ to package your project,
  35. activate Incremental's Hatchling plugin by altering your ``pyproject.toml``:
  36. .. code:: toml
  37. [build-system]
  38. requires = [
  39. "hatchling",
  40. "incremental>=24.7.2", # ← Add incremental as a build dependency
  41. ]
  42. build-backend = "hatchling.build"
  43. [project]
  44. name = "<projectname>"
  45. dynamic = ["version"] # ← Mark the version dynamic
  46. dependencies = [
  47. "incremental>=24.7.2", # ← Depend on incremental at runtime
  48. ]
  49. # ...
  50. [tool.hatch.version]
  51. source = "incremental" # ← Activate Incremental's Hatchling plugin
  52. Incremental can be configured as usual in an optional ``[tool.incremental]`` table.
  53. The ``hatch version`` command will report the Incremental-managed version.
  54. Use the ``python -m incremental.update`` command to change the version (setting it with ``hatch version`` is not supported).
  55. Next, `initialize the project`_.
  56. Using ``setup.py``
  57. ~~~~~~~~~~~~~~~~~~
  58. Incremental may be used from ``setup.py`` instead of ``pyproject.toml``.
  59. Add this to your ``setup()`` call, removing any other versioning arguments:
  60. .. code:: python
  61. setup(
  62. use_incremental=True,
  63. setup_requires=['incremental'],
  64. install_requires=['incremental'], # along with any other install dependencies
  65. ...
  66. }
  67. Then `initialize the project`_.
  68. Initialize the project
  69. ~~~~~~~~~~~~~~~~~~~~~~
  70. Install Incremental to your local environment with ``pip install incremental[scripts]``.
  71. Then run ``python -m incremental.update <projectname> --create``.
  72. It will create a file in your package named ``_version.py`` like this:
  73. .. code:: python
  74. from incremental import Version
  75. __version__ = Version("<projectname>", 24, 1, 0)
  76. __all__ = ["__version__"]
  77. Then, so users of your project can find your version, in your root package's ``__init__.py`` add:
  78. .. code:: python
  79. from ._version import __version__
  80. Subsequent installations of your project will then use Incremental for versioning.
  81. Incremental Versions
  82. --------------------
  83. ``incremental.Version`` is a class that represents a version of a given project.
  84. It is made up of the following elements (which are given during instantiation):
  85. - ``package`` (required), the name of the package this ``Version`` represents.
  86. - ``major``, ``minor``, ``micro`` (all required), the X.Y.Z of your project's ``Version``.
  87. - ``release_candidate`` (optional), set to 0 or higher to mark this ``Version`` being of a release candidate (also sometimes called a "prerelease").
  88. - ``post`` (optional), set to 0 or higher to mark this ``Version`` as a postrelease.
  89. - ``dev`` (optional), set to 0 or higher to mark this ``Version`` as a development release.
  90. You can extract a PEP-440 compatible version string by using the ``.public()`` method, which returns a ``str`` containing the full version. This is the version you should provide to users, or publicly use. An example output would be ``"13.2.0"``, ``"17.1.2dev1"``, or ``"18.8.0rc2"``.
  91. Calling ``repr()`` with a ``Version`` will give a Python-source-code representation of it, and calling ``str()`` on a ``Version`` produces a string like ``'[Incremental, version 16.10.1]'``.
  92. Updating
  93. --------
  94. Incremental includes a tool to automate updating your Incremental-using project's version called ``incremental.update``.
  95. It updates the ``_version.py`` file and automatically updates some uses of Incremental versions from an indeterminate version to the current one.
  96. It requires ``click`` from PyPI.
  97. ``python -m incremental.update <projectname>`` will perform updates on that package.
  98. The commands that can be given after that will determine what the next version is.
  99. - ``--newversion=<version>``, to set the project version to a fully-specified version (like 1.2.3, or 17.1.0dev1).
  100. - ``--rc``, to set the project version to ``<year-2000>.<month>.0rc1`` if the current version is not a release candidate, or bump the release candidate number by 1 if it is.
  101. - ``--dev``, to set the project development release number to 0 if it is not a development release, or bump the development release number by 1 if it is.
  102. - ``--patch``, to increment the patch number of the release. This will also reset the release candidate number, pass ``--rc`` at the same time to increment the patch number and make it a release candidate.
  103. - ``--post``, to set the project postrelease number to 0 if it is not a postrelease, or bump the postrelease number by 1 if it is. This will also reset the release candidate and development release numbers.
  104. If you give no arguments, it will strip the release candidate number, making it a "full release".
  105. Incremental supports "indeterminate" versions, as a stand-in for the next "full" version. This can be used when the version which will be displayed to the end-user is unknown (for example "introduced in" or "deprecated in"). Incremental supports the following indeterminate versions:
  106. - ``Version("<projectname>", "NEXT", 0, 0)``
  107. - ``<projectname> NEXT``
  108. When you run ``python -m incremental.update <projectname> --rc``, these will be updated to real versions (assuming the target final version is 17.1.0):
  109. - ``Version("<projectname>", 17, 1, 0, release_candidate=1)``
  110. - ``<projectname> 17.1.0rc1``
  111. Once the final version is made, it will become:
  112. - ``Version("<projectname>", 17, 1, 0)``
  113. - ``<projectname> 17.1.0``
  114. .. |coverage| image:: https://codecov.io/gh/twisted/incremental/branch/master/graph/badge.svg?token=K2ieeL887X
  115. .. _coverage: https://codecov.io/gh/twisted/incremental
  116. .. |gha| image:: https://github.com/twisted/incremental/actions/workflows/tests.yaml/badge.svg
  117. .. _gha: https://github.com/twisted/incremental/actions/workflows/tests.yaml
  118. .. |pypi| image:: http://img.shields.io/pypi/v/incremental.svg
  119. .. _pypi: https://pypi.python.org/pypi/incremental