Fix database migrations failing on platforms where SQLite is configured with SQLITE_DBCONFIG_DEFENSIVE by default, such as macOS.#19690
Merged
reivilibre merged 3 commits intodevelopfrom Apr 15, 2026
Conversation
MadLittleMods
approved these changes
Apr 14, 2026
| ``` | ||
|
|
||
| This example uses python 3.13, but choose whichever version you want. | ||
|
|
Contributor
There was a problem hiding this comment.
This is removing the workaround docs from #19615
(no longer necessary)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes: #19616
This caused 2+ people trouble now, so worth batting away with a low-effort change if we can.
Only seen on macOS so far, but nothing stops SQLite being configured in defensive mode by default on other platforms, so it is not necessarily entirely specific to macOS.
We could also do this for Python < 3.12 but it'd be more effort and I don't know if it's worth it.
(For context @kegsay says the interpreter with this problem was installed through
pyenv install.)