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: CONTRIBUTING.md
+19-11Lines changed: 19 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,20 +26,28 @@ Set up a virtualenv and run:
26
26
This will install the requirements, collect static files, migrate the database, and finally load all the existing fixtures into your database.
27
27
28
28
## Updating requirements
29
-
Add or remove the dependency from either `requirements.prod.in` or `requirements.dev.in` as appropriate.
29
+
Add a dependency with:
30
30
31
-
Run `make compile` and appropriate txt file will be updated.
31
+
uv add [--dev] <dependency>
32
+
33
+
Remove a dependency with:
34
+
35
+
uv remove [--dev] <dependency>
36
+
37
+
Update a single dependency with:
38
+
39
+
uv add [--dev] --upgrade-package <dependency>
32
40
33
41
## Add data for new versions of Django
34
-
1. Update the `requirements.prod.in` file to pin the new version of Django, eg `django==5.1`
35
-
1. Run `make compile` to compile this change to `requirements.prod.txt`
36
-
1.Run `python manage.py populate_cbv` to introspect the installed Django and populate the required objects in the database
37
-
1. Run `python manage.py fetch_docs_urls` to update the records in the database with the latest links to the Django documentation, this will fail at 1.9, this is expected
38
-
1.Export the new Django version into a fixture with `python manage.py cbv_dumpversion x.xx > cbv/fixtures/x.xx.json`
39
-
1. Remove the empty Generic module from the generated JSON
40
-
1.Add the fixture to git with `git add cbv/fixtures/<version>.git`
41
-
1. Restore the requirements files with `git restore requirements.*`
42
-
1.Commit and push your changes, they will be deployed once your PR is merged to main
42
+
1. Update Django with `uv add --upgrade-package django<N`, replacing `N` with
43
+
the version **after** the one you are updating to
44
+
1.Update the project's code to run under the target version of Django, as
45
+
necessary;
46
+
1.Use `uv run manage.py populate_cbv` to introspect the running Django
47
+
and populate the required objects in the database;
48
+
1.Use `uv run manage.py fetch_docs_urls`to update the records in the
49
+
database with the latest links to the Django documentation;
50
+
1.Export the new Django version into a fixture with: `uv run manage.py cbv_dumpversion x.xx > cbv/fixtures/x.xx.json`;
43
51
44
52
## Testing
45
53
Run `make test` to run the full test suite with coverage.
0 commit comments