Task #8975: Provide environment variables to permit Django ORM to work in an async context - Pulp

Actions

Send by e-mail Copy link

Task #8975

closed

Task #8488: [EPIC] Upgrade to django 3.2

Provide environment variables to permit Django ORM to work in an async context

Added by dalley almost 3 years ago. Updated almost 3 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

dalley

Category:

Sprint/Milestone:

3.14.0

Start date:

Due date:

% Done:

100%

Estimated time:

Platform Release:

Groomed:

Sprint Candidate:

Tags:

Sprint:

Quarter:

Description

We will need to have provide for the worker processes the environment variable DJANGO_ALLOW_ASYNC_UNSAFE

https://docs.djangoproject.com/en/3.1/topics/async/#envvar-DJANGO_ALLOW_ASYNC_UNSAFE

Despite the warnings, we've tried to be careful about our usage of the ORM so that it remains safe within async code (not sharing querysets between coroutines), so it should be safe. In any case, it's just re-enabling what we've been doing for a long time.

At some point when Django introduces proper async ORM support we will definitely want to re-architect to take advantage of that.

Actions

Copy link

Updated by dalley almost 3 years ago

Subject changed from Provide environment variables to permit Django async to work in an async context to Provide environment variables to permit Django ORM to work in an async context

Actions

Copy link