Skip to content

[pull] master from django-tenants:master - #83

Merged
pull[bot] merged 3 commits into
Dresdn:masterfrom
django-tenants:master
Jul 1, 2026
Merged

[pull] master from django-tenants:master#83
pull[bot] merged 3 commits into
Dresdn:masterfrom
django-tenants:master

Conversation

@pull

@pull pull Bot commented Jul 1, 2026

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

tomturner and others added 3 commits June 29, 2026 22:27
The multiprocessing executor's workers import the Postgres backend and
touch the Django app registry, which only works if the worker inherits
the parent's already-populated registry — i.e. the fork start method.
The pool previously relied on Python's implicit default start method.
Python 3.14 now warns when implicitly forking from a multi-threaded
parent and a future Python will change the default away from fork, which
would silently break this executor even on Linux.

Request a fork context explicitly where the platform supports it (Linux),
falling back to the default context elsewhere (e.g. Windows, which has no
fork). get_context('fork') returns a local context and does not mutate
the global default start method.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…utor-fork

Use fork start method in multiprocessing migration executor
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@pull pull Bot locked and limited conversation to collaborators Jul 1, 2026
@pull pull Bot added the ⤵️ pull label Jul 1, 2026
@pull
pull Bot merged commit 51d6ef3 into Dresdn:master Jul 1, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant