-
-
Notifications
You must be signed in to change notification settings - Fork 30.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[3.10] gh-89452: GHA: Set --with-dbmliborder to avoid issues with homebrew's gdbm 1.24 #125112
Conversation
…th homebrew's gdbm 1.24 Per python#89452 (comment), the issue is fixed in configure for 3.11+, and > For older Python versions, the workaround is to build with: > > ./configure --with-dbmliborder=gdbm:ndbm We need this workaround in GitHub Actions, otherwise the tests fail.
@pablogsal @ambv, given #89452 (comment), does this look reasonable to you, as a workaround for a buildsystem/homebrew incompatibility which was fixed better in 3.11+? If so, I'll also backport to 3.9 and update the Devguide homebrew instructions. |
Makes sense to me. |
Sorry, @encukou and @ambv, I could not cleanly backport this to
|
…h homebrew's gdbm 1.24 (pythonGH-125112) Per https://github.com/python/cpython/issues/89452GH-issuecomment-1116329316, the issue is fixed in configure for 3.11+, and > For older Python versions, the workaround is to build with: > > ./configure --with-dbmliborder=gdbm:ndbm We need this workaround in GitHub Actions, otherwise the tests fail. (cherry picked from commit 850189a)
GH-125176 is a backport of this pull request to the 3.9 branch. |
…brew's gdbm 1.24 (GH-125112) (#125176) Per https://github.com/python/cpython/issues/89452GH-issuecomment-1116329316, the issue is fixed in configure for 3.11+, and > For older Python versions, the workaround is to build with: > > ./configure --with-dbmliborder=gdbm:ndbm We need this workaround in GitHub Actions, otherwise the tests fail. (cherry picked from commit 850189a) Co-authored-by: Łukasz Langa <[email protected]>
Per #89452 (comment), the issue is fixed in configure for 3.11+, and
We need this workaround in GitHub Actions, otherwise the tests fail.
See also: gh-105304