Repository navigation
Conversation
Tracks LadybugDB/ladybug#1435, which renames debug_enable_multi_writes to enable_multi_writes and flips the engine default to true. Mirror that default here so the binding does not silently pin single-writer mode.
This was referenced Oct 27, 2026
Contributor
Author
|
Superseded by #77, which takes the fuller approach: all settings default to None (engine default) instead of just flipping this one value. |
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
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.
Tracks LadybugDB/ladybug#1435, which renames
debug_enable_multi_writestoenable_multi_writesand flips the engine default totrue.This binding passes its own default explicitly, so without this change Python users would silently stay on single-writer mode despite the new engine default. Mirrors the flip in
database.py,_lbug_capi.py, andpy_database.cpp.