Skip to content
This repository has been archived by the owner on Sep 4, 2023. It is now read-only.

Commit

Permalink
Support both django3.2 and django4 (#4)
Browse files Browse the repository at this point in the history
  • Loading branch information
cunla authored Mar 24, 2022
1 parent fcf5fe6 commit 6094cd5
Show file tree
Hide file tree
Showing 3 changed files with 29 additions and 37 deletions.
6 changes: 3 additions & 3 deletions .github/workflows/test.yml
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ jobs:
strategy:
max-parallel: 4
matrix:
python-version: ['3.10']
python-version: ['3.9', '3.10']
redis-version: ['6']

steps:
Expand Down Expand Up @@ -47,10 +47,10 @@ jobs:
- uses: mshick/add-pr-comment@v1
with:
message: |
Coverage report:
Coverage report python ${{ matrix.python-version }} (python 3.9 tests with django 3.2, while 3.10 tests with latest):
```
${{ steps.coverage_report.outputs.stdout }}
```
repo-token: ${{ secrets.GITHUB_TOKEN }}
repo-token-user-login: 'github-actions[bot]'
allow-repeats: false
allow-repeats: true
53 changes: 21 additions & 32 deletions poetry.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

7 changes: 5 additions & 2 deletions pyproject.toml
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ name = "django-rqscheduler4"
packages = [
{ include = "scheduler" },
]
version = "2022.3.1"
version = "2022.3.2"
description = "A database backed job scheduler for Django RQ with Django"
readme = "README.md"
keywords = ["django", "rq", "django-rq", "rq-scheduler"]
Expand All @@ -31,7 +31,10 @@ homepage = "https://github.com/cunla/django-rqscheduler"

[tool.poetry.dependencies]
python = "^3.8"
django = "^3.2 || ^4.0"
django = [
{version="^3.2", markers="python_version == '3.9'"},
{version="^4.0", markers="python_version >= '3.10'"}
]
django-model-utils = "^4.2.0"
django-rq = "^2.4.1"
rq-scheduler = "^0.11.0"
Expand Down

0 comments on commit 6094cd5

Please sign in to comment.