This repository was archived by the owner on Mar 29, 2026. It is now read-only.
Fixed build with python-3.13#1111
Merged
Merged
Conversation
According to https://docs.python.org/3.13/whatsnew/3.13.html: Remove PyEval_InitThreads() and PyEval_ThreadsInitialized() functions, deprecated in Python 3.9. Since Python 3.7, Py_Initialize() always creates the GIL: calling PyEval_InitThreads() did nothing and PyEval_ThreadsInitialized() always returned non-zero. (Contributed by Victor Stinner in python/cpython#105182.) If support for < python-3.7 is required, conditionals have to be added Signed-off-by: Jaroslav Škarvada <jskarvad@redhat.com>
|
|
dl1jbe
pushed a commit
to dl1jbe/urh
that referenced
this pull request
Nov 15, 2025
According to https://docs.python.org/3.13/whatsnew/3.13.html: Remove PyEval_InitThreads() and PyEval_ThreadsInitialized() functions, deprecated in Python 3.9. Since Python 3.7, Py_Initialize() always creates the GIL: calling PyEval_InitThreads() did nothing and PyEval_ThreadsInitialized() always returned non-zero. (Contributed by Victor Stinner in python/cpython#105182.) If support for < python-3.7 is required, conditionals have to be added Signed-off-by: Jaroslav Škarvada <jskarvad@redhat.com>
dl1jbe
pushed a commit
to dl1jbe/urh
that referenced
this pull request
Nov 15, 2025
According to https://docs.python.org/3.13/whatsnew/3.13.html: Remove PyEval_InitThreads() and PyEval_ThreadsInitialized() functions, deprecated in Python 3.9. Since Python 3.7, Py_Initialize() always creates the GIL: calling PyEval_InitThreads() did nothing and PyEval_ThreadsInitialized() always returned non-zero. (Contributed by Victor Stinner in python/cpython#105182.) If support for < python-3.7 is required, conditionals have to be added Signed-off-by: Jaroslav Škarvada <jskarvad@redhat.com>
dl1jbe
pushed a commit
to dl1jbe/urh
that referenced
this pull request
Nov 23, 2025
According to https://docs.python.org/3.13/whatsnew/3.13.html: Remove PyEval_InitThreads() and PyEval_ThreadsInitialized() functions, deprecated in Python 3.9. Since Python 3.7, Py_Initialize() always creates the GIL: calling PyEval_InitThreads() did nothing and PyEval_ThreadsInitialized() always returned non-zero. (Contributed by Victor Stinner in python/cpython#105182.) If support for < python-3.7 is required, conditionals have to be added Signed-off-by: Jaroslav Škarvada <jskarvad@redhat.com>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 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.
According to https://docs.python.org/3.13/whatsnew/3.13.html:
Remove PyEval_InitThreads() and PyEval_ThreadsInitialized() functions, deprecated in Python 3.9. Since Python 3.7, Py_Initialize() always creates the GIL: calling PyEval_InitThreads() did nothing and PyEval_ThreadsInitialized() always returned non-zero. (Contributed by Victor Stinner in python/cpython#105182.)
If support for < python-3.7 is required, conditionals have to be added