@@ -32,33 +32,34 @@ When including the library in a list of project dependencies, in order to
3232avoid installing future incompatible releases, it is recommended to specify
3333the major and minor version numbers.
3434
35- As an example, the expression ``eventsourcing<=9.3.99999 `` would install the
36- latest version of the 9.3 series, allowing future bug fixes released with
37- point version number increments. You can use this expression in a ``pip install ``
38- command, in a ``requirements.txt `` file, or in a ``setup.py `` file.
35+ As an example, the expression ``eventsourcing>=9.4.0,<9.5.0 `` would install the
36+ latest version of the 9.4 series, allowing future bug fixes released with
37+ point version number increments. You can use this expression in a ``pip install `` command.
3938
4039::
4140
42- $ pip install "eventsourcing< =9.4.99999 "
41+ $ pip install "eventsourcing> =9.4.0,<9.5.0 "
4342
44- If you are specifying the dependencies of your project in a ``pyproject.toml ``
45- file, and for example using the Poetry build tool, you can specify the
46- dependency on this library in the following way.
43+ You can use the same expression in `` requirements.txt `` files, in a ``setup.py `` files, and
44+ in a `` pyproject.toml `` files. For example, if you are specifying the dependencies of your project
45+ in a `` pyproject.toml `` file, you can specify the dependency on this library in the following way.
4746
4847::
4948
50- [tool.poetry.dependencies]
51- python = "^3.9"
52- eventsourcing = { version = "~9.4" }
49+ [project]
50+ requires-python = ">=3.9.2"
51+ dependencies = [
52+ "eventsourcing>=9.4.0,<9.5.0",
53+ ]
5354
5455
55- Specifying the major and minor version number in this way will avoid any
56- potentially destabilising additional features introduced with minor version
57- number increments, and also avoid all backward incompatible changes introduced
58- with major version number increments.
56+ Requiring a specific major and minor version number in this way will avoid any
57+ potentially destabilising additional features with minor version increments, and
58+ also avoid all backward incompatible changes introduced with major version number
59+ increments.
5960
6061Upgrading to new minor versions is encouraged, but it is recommended to
61- do this manually so that you are sure your project isn't inadvertently
62+ do this carefully so that you can be sure your project isn't inadvertently
6263broken by changes in the library. Migrating to new major versions is
6364also encouraged, but by definition this may involve your making changes
6465to your project to adjust for the backward incompatibilities introduced
0 commit comments