1
1
Development
2
2
===========
3
3
4
- To contribute to `pytest-base-url ` you can use `Poetry <https://python-poetry.org / >`_ to manage
4
+ To contribute to `pytest-base-url ` you can use `Hatch <https://hatch.pypa.io/latest / >`_ to manage
5
5
a python virtual environment and `pre-commit <https://pre-commit.com/ >`_ to help you with
6
6
styling and formatting.
7
7
8
8
To setup the virtual environment and pre-commit, run:
9
9
10
10
.. code-block :: bash
11
11
12
- $ poetry install
13
- $ poetry run pre-commit install
12
+ $ hatch -e test run pre-commit install
14
13
15
- If you're not using ``Poetry ``, to install ``pre-commit ``, run:
14
+ If you're not using ``Hatch ``, to install ``pre-commit ``, run:
16
15
17
16
.. code-block :: bash
18
17
@@ -30,14 +29,14 @@ Running Tests
30
29
-------------
31
30
32
31
You will need `Tox <https://tox.wiki/en/latest/ >`_ installed to run the tests
33
- against the supported Python versions. If you're using ``Poetry `` it will be
32
+ against the supported Python versions. If you're using ``Hatch `` it will be
34
33
installed for you.
35
34
36
- With ``Poetry ``, run:
35
+ With ``Hatch ``, run:
37
36
38
37
.. code-block :: bash
39
38
40
- $ poetry run tox
39
+ $ hatch -e test run tox
41
40
42
41
Otherwise, to install and run, do:
43
42
@@ -57,6 +56,6 @@ Follow these steps to release a new version of the project:
57
56
#. Commit and push the new branch and then create a new pull request
58
57
#. Wait for tests and reviews and then merge the branch
59
58
#. Once merged, update your local master again (``git pull --rebase upstream master ``)
60
- #. Tag the release with the new release version (``git tag v <new tag> ``)
59
+ #. Tag the release with the new release version (``git tag <new tag> ``)
61
60
#. Push the tag (``git push upstream --tags ``)
62
61
#. Done.
0 commit comments