Skip to content

Commit 19f2a02

Browse files
authored
Remove direct usage of redis in application code (#67)
This appeared to only be required by RedisLock, which was unused. We are still depending on redis itself as the celery backend.
1 parent d5648f2 commit 19f2a02

3 files changed

Lines changed: 0 additions & 71 deletions

File tree

pyproject.toml

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -51,7 +51,6 @@ server = [
5151
"djangorestframework~=3.15.1",
5252
"google-cloud-bigquery",
5353
"pyyaml",
54-
"redis[hiredis]",
5554
"whitenoise~=6.6.0",
5655
]
5756

requirements.txt

Lines changed: 0 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -8,8 +8,6 @@ amqp==5.3.1
88
# via kombu
99
asgiref==3.8.1
1010
# via django
11-
async-timeout==5.0.1
12-
# via redis
1311
attrs==24.2.0
1412
# via
1513
# jsonschema
@@ -91,8 +89,6 @@ grpcio-status==1.68.1
9189
# via google-api-core
9290
gunicorn==22.0.0
9391
# via WebCompatManager (pyproject.toml)
94-
hiredis==3.1.0
95-
# via redis
9692
idna==3.10
9793
# via requests
9894
josepy==1.14.0
@@ -142,8 +138,6 @@ python-dateutil==2.9.0.post0
142138
# google-cloud-bigquery
143139
pyyaml==6.0.2
144140
# via WebCompatManager (pyproject.toml)
145-
redis==5.2.0
146-
# via WebCompatManager (pyproject.toml)
147141
referencing==0.35.1
148142
# via
149143
# jsonschema

server/server/utils.py

Lines changed: 0 additions & 64 deletions
This file was deleted.

0 commit comments

Comments
 (0)