You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/CONTRIBUTING.md
+15-28Lines changed: 15 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,15 +25,14 @@ But don't be afraid to open half-finished PRs and ask questions if something is
25
25
- Don’t break backwards-compatibility.
26
26
27
27
28
-
## Local Development Environment
28
+
## Local development environment
29
29
30
-
You can (and should) run our test suite using [*tox*].
31
-
However, you’ll probably want a more traditional environment as well.
30
+
First, **fork** the repository on GitHub and **clone** it using one of the alternatives that you can copy-paste by pressing the big green button labeled `<> Code`.
32
31
33
-
First, create a [virtual environment](https://virtualenv.pypa.io/) so you don't break your system-wide Python installation.
34
-
We recommend using the Python version from the `.python-version-default` file in project's root directory.
32
+
You can (and should) run our test suite using [*tox*](https://tox.wiki/).
33
+
However, you'll probably want a more traditional environment as well.
35
34
36
-
If you're using tools that understand `.python-version` files like [*pyenv*](https://github.com/pyenv/pyenv) does, you can make it a link to the `.python-version-default` file (`ln -s .python-version-default .python-version`).
35
+
We recommend using the Python version from the `.python-version-default` file in the project's root directory, because that's the one that is used in the CI by default, too.
37
36
38
37
If you're using [*direnv*](https://direnv.net), you can automate the creation of the project virtual environment with the correct Python version by adding the following `.envrc` to the project root:
> -**Before** you start working on a new pull request, use the "*Sync fork*" button in GitHub's web UI to ensure your fork is up to date.
52
+
> -**Always create a new branch off `main` for each new pull request.**
53
+
> Yes, you can work on `main` in your fork and submit pull requests.
54
+
> But this will *inevitably* lead to you not being able to synchronize your fork with upstream and having to start over.
58
55
59
-
or if you prefer to use *Git* via `https`:
56
+
Change into the newly created directory and after activating a virtual environment, install an editable version of this project along with its tests requirements:
$ pip install -e . --group dev # or `uv pip install -e . --group dev`
63
60
```
64
61
65
-
Change into the newly created directory and **after activating your virtual environment** install an editable version of *argon2-cffi* along with its tests and docs requirements:
0 commit comments