You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the upcoming release of Python 3.13, there is an experimental feature allowing Python to run without the Global Interpreter Lock (GIL). This feature is described in PEP 703, which introduces the "free-threaded" mode for CPython.
You can find more details about this feature in the Free-threaded CPython documentation.
Since TA-Lib is a widely used library for technical analysis, especially in multithreaded environments, it would be beneficial to ensure compatibility with Python's GIL-free mode. This will allow users to fully utilize multi-core processors for parallel processing without the limitations of GIL.
Would it be possible to test and, if necessary, update TA-Lib to support this new mode? Your attention to this matter would be greatly appreciated by the community.
Thank you for your continuous support and development of TA-Lib!
Hello TA-Lib maintainers,
With the upcoming release of Python 3.13, there is an experimental feature allowing Python to run without the Global Interpreter Lock (GIL). This feature is described in PEP 703, which introduces the "free-threaded" mode for CPython.
You can find more details about this feature in the Free-threaded CPython documentation.
Since TA-Lib is a widely used library for technical analysis, especially in multithreaded environments, it would be beneficial to ensure compatibility with Python's GIL-free mode. This will allow users to fully utilize multi-core processors for parallel processing without the limitations of GIL.
Would it be possible to test and, if necessary, update TA-Lib to support this new mode? Your attention to this matter would be greatly appreciated by the community.
Thank you for your continuous support and development of TA-Lib!
Originally posted by @gitctrlx in TA-Lib/ta-lib-python#675
The text was updated successfully, but these errors were encountered: