From: Nick Porter <nick@portercomputing.co.uk>
Date: Tue, 23 May 2023 17:37:32 +0000 (+0100)
Subject: Remove old Python 2 specific module config
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=0886259112b241de2c4e03af66037c144636b2a4;p=thirdparty%2Ffreeradius-server.git

Remove old Python 2 specific module config
---

diff --git a/raddb/mods-available/python b/raddb/mods-available/python
index db6241082b1..748852f6214 100644
--- a/raddb/mods-available/python
+++ b/raddb/mods-available/python
@@ -32,34 +32,6 @@ python {
 	#
 	module = example
 
-	#
-	#  cext_compat::
-	#
-	#  Uncomment the following line (and set to true) if you need
-	#  to call Python C extensions that acquire the GIL.
-	#
-	#  This will use the first Python interpreter (*not a sub-interpreter*)
-	#  to provide the execution environment for this module instance.
-	#
-	#  The tradeoff is, that any module instance with `cext_compat = true`,
-	#  will share the same environment, and will use the same user
-	#  configurable configuration items, and `python_path`, as the first
-	#  instance of `rlm_python` to be loaded with `cext_compat` enabled.
-	#
-	#  Not all Python functions use the GIL as it prevents parallel
-	#  execution.  A good indication of whether `cext_compat` is needed
-	#  is whether your script locks up or crashes when calling a
-	#  Python C extension.
-	#
-	#  [NOTE]
-	#  ====
-	#  This functionality is only available when building with Python 2.7
-	#  or below.  For Python 3 you should build against Python 3.8 which
-	#  has a proper fix for this issue (per interpreter GILs)
-	#  ====
-	#
-#	cext_compat = false
-
 	#
 	#  [NOTE]
 	#  ====