From 1e18b201f5259fd328e8db738fc73fa9449bd5c6 Mon Sep 17 00:00:00 2001 From: Bradlee Speice Date: Tue, 30 Jun 2020 14:31:26 -0400 Subject: [PATCH] Repository URL --- _posts/2020-06-29-release-the-gil-pt.-2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2020-06-29-release-the-gil-pt.-2.md b/_posts/2020-06-29-release-the-gil-pt.-2.md index 534df85..bb4eaf2 100644 --- a/_posts/2020-06-29-release-the-gil-pt.-2.md +++ b/_posts/2020-06-29-release-the-gil-pt.-2.md @@ -24,7 +24,7 @@ techniques below for managing the GIL in a Python extension. The motto of [Pybind11](https://github.com/pybind/pybind11) is "seamless operability between C++11 and Python", and they certainly deliver on that. Setting up a hybrid project where C++ (using CMake) and Python (using setuptools) could coexist was straight-forward, and the repository also works as -[a template](LINK HERE) for future projects. +[a template](https://github.com/speice-io/release-the-gil-pybind11/settings) for future projects. Just like the previous post, we'll examine a simple Fibonacci sequence implementation to demonstrate how Python's threading model interacts with Pybind11: