Use --with-dbmliborder or macOS+Homebrew on 3.10 and below by encukou · Pull Request #1433 · python/devguide · GitHub
Conversation
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
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.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.
Footer
You can’t perform that action at this time.
As detailed in python/cpython#89452 (comment), Homebrew makes a specific change to gdbm that confuses the build of 3.10 and below into picking incompatible headers/libs, so dbm segfaults at runtime.
It's fixed in 3.11; older source-only releases only get a workaround: pass --with-dbmliborder=gdbm:ndbm to configure.
(3.8 is now EOL, but I don't want to remove mentions of it in this PR, even if it's textually nearby.)
📚 Documentation preview 📚: https://cpython-devguide--1433.org.readthedocs.build/