Fix: Make URL cache clearing thread-safe in _django_set_urlconf
#1233
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
When running tests in parallel with
pytest-xdist
, the@pytest.mark.urls
fixture can cause a race condition. Multiple test workers may try to modify the globalROOT_URLCONF
and clear the URL cache at the same time, leading to unpredictable behavior and intermittent test failures.Solution
This change introduces a
threading.Lock()
around the URL configuration and cache-clearing logic in the_django_set_urlconf
fixture. This ensures that these operations are atomic, preventing multiple threads from interfering with each other and making the URL cache clearing thread-safe.