2025-09-08T08:04:47,116 Created temporary directory: /tmp/pip-build-tracker-1ycv8e62 2025-09-08T08:04:47,116 Initialized build tracking at /tmp/pip-build-tracker-1ycv8e62 2025-09-08T08:04:47,117 Created build tracker: /tmp/pip-build-tracker-1ycv8e62 2025-09-08T08:04:47,117 Entered build tracker: /tmp/pip-build-tracker-1ycv8e62 2025-09-08T08:04:47,117 Created temporary directory: /tmp/pip-wheel-h8pokkub 2025-09-08T08:04:47,120 Created temporary directory: /tmp/pip-ephem-wheel-cache-ffzms3dv 2025-09-08T08:04:47,181 Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple 2025-09-08T08:04:47,183 2 location(s) to search for versions of wlsqm: 2025-09-08T08:04:47,183 * https://pypi.org/simple/wlsqm/ 2025-09-08T08:04:47,183 * https://www.piwheels.org/simple/wlsqm/ 2025-09-08T08:04:47,183 Fetching project page and analyzing links: https://pypi.org/simple/wlsqm/ 2025-09-08T08:04:47,184 Getting page https://pypi.org/simple/wlsqm/ 2025-09-08T08:04:47,185 Found index url https://pypi.org/simple/ 2025-09-08T08:04:47,255 Fetched page https://pypi.org/simple/wlsqm/ as application/vnd.pypi.simple.v1+json 2025-09-08T08:04:47,256 Found link https://files.pythonhosted.org/packages/5f/96/f6d5fa383518531edc30427b7fd3bfc3f167ac6463d9d5291670c062f8f8/wlsqm-0.1.1.tar.gz (from https://pypi.org/simple/wlsqm/), version: 0.1.1 2025-09-08T08:04:47,257 Found link https://files.pythonhosted.org/packages/33/7b/f806e20db120ea51dca5653104e9d41275aaa99d907367b98d3d526fd3fd/wlsqm-0.1.2.tar.gz (from https://pypi.org/simple/wlsqm/), version: 0.1.2 2025-09-08T08:04:47,257 Found link https://files.pythonhosted.org/packages/31/8a/bef4d04d38bdb9eabfd437bf6bf240d77adf7196eeb2266e7bbd018f5f95/wlsqm-0.1.3.tar.gz (from https://pypi.org/simple/wlsqm/), version: 0.1.3 2025-09-08T08:04:47,257 Found link https://files.pythonhosted.org/packages/7c/7f/f001e1470a15feb956b2d5803b1b9691c4aeb23f0a8afcec6f72224115cf/wlsqm-0.1.4.tar.gz (from https://pypi.org/simple/wlsqm/), version: 0.1.4 2025-09-08T08:04:47,257 Found link https://files.pythonhosted.org/packages/0f/37/d6e09c5fa4d2437dd239681b483a1a2c28f52673a2e6c80c0865420cf907/wlsqm-0.1.5.tar.gz (from https://pypi.org/simple/wlsqm/), version: 0.1.5 2025-09-08T08:04:47,258 Found link https://files.pythonhosted.org/packages/bf/87/a4e1adc45e69f5032971b0b47251c0b87d1cd70b277b1548e3197f9af479/wlsqm-0.1.6.tar.gz (from https://pypi.org/simple/wlsqm/), version: 0.1.6 2025-09-08T08:04:47,258 Fetching project page and analyzing links: https://www.piwheels.org/simple/wlsqm/ 2025-09-08T08:04:47,258 Getting page https://www.piwheels.org/simple/wlsqm/ 2025-09-08T08:04:47,259 Found index url https://www.piwheels.org/simple/ 2025-09-08T08:04:47,352 Fetched page https://www.piwheels.org/simple/wlsqm/ as text/html 2025-09-08T08:04:47,352 Skipping link: not a file: https://www.piwheels.org/simple/wlsqm/ 2025-09-08T08:04:47,352 Skipping link: not a file: https://pypi.org/simple/wlsqm/ 2025-09-08T08:04:47,374 Given no hashes to check 1 links for project 'wlsqm': discarding no candidates 2025-09-08T08:04:47,375 Collecting wlsqm==0.1.6 2025-09-08T08:04:47,377 Created temporary directory: /tmp/pip-unpack-jc6rn6nu 2025-09-08T08:04:47,652 Downloading wlsqm-0.1.6.tar.gz (1.1 MB) 2025-09-08T08:04:47,994 Added wlsqm==0.1.6 from https://files.pythonhosted.org/packages/bf/87/a4e1adc45e69f5032971b0b47251c0b87d1cd70b277b1548e3197f9af479/wlsqm-0.1.6.tar.gz to build tracker '/tmp/pip-build-tracker-1ycv8e62' 2025-09-08T08:04:47,995 Running setup.py (path:/tmp/pip-wheel-h8pokkub/wlsqm_1e9dfb9debf34ee197e1e383223af1af/setup.py) egg_info for package wlsqm 2025-09-08T08:04:47,995 Created temporary directory: /tmp/pip-pip-egg-info-eqlq8q5_ 2025-09-08T08:04:47,995 Preparing metadata (setup.py): started 2025-09-08T08:04:47,996 Running command python setup.py egg_info 2025-09-08T08:04:48,711 /tmp/pip-wheel-h8pokkub/wlsqm_1e9dfb9debf34ee197e1e383223af1af/setup.py:149: DeprecationWarning: Attribute s is deprecated and will be removed in Python 3.14; use value instead 2025-09-08T08:04:48,711 version = ast.parse(line).body[0].value.s 2025-09-08T08:04:51,377 warning: wlsqm/fitter/infra.pxd:36:90: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:51,381 warning: wlsqm/fitter/infra.pxd:104:134: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:51,381 warning: wlsqm/fitter/infra.pxd:105:73: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:51,382 warning: wlsqm/fitter/infra.pxd:106:64: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:51,386 warning: wlsqm/fitter/infra.pxd:185:212: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:51,447 performance hint: wlsqm/fitter/expert.pyx:774:0: Exception check on 'expert_prepare_one_3D' will always require the GIL to be acquired. 2025-09-08T08:04:51,447 Possible solutions: 2025-09-08T08:04:51,447 1. Declare 'expert_prepare_one_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:51,447 2. Use an 'int' return type on 'expert_prepare_one_3D' to allow an error code to be returned. 2025-09-08T08:04:51,448 performance hint: wlsqm/fitter/expert.pyx:785:0: Exception check on 'expert_prepare_one_2D' will always require the GIL to be acquired. 2025-09-08T08:04:51,448 Possible solutions: 2025-09-08T08:04:51,448 1. Declare 'expert_prepare_one_2D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:51,448 2. Use an 'int' return type on 'expert_prepare_one_2D' to allow an error code to be returned. 2025-09-08T08:04:51,448 performance hint: wlsqm/fitter/expert.pyx:796:0: Exception check on 'expert_prepare_one_1D' will always require the GIL to be acquired. 2025-09-08T08:04:51,448 Possible solutions: 2025-09-08T08:04:51,449 1. Declare 'expert_prepare_one_1D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:51,449 2. Use an 'int' return type on 'expert_prepare_one_1D' to allow an error code to be returned. 2025-09-08T08:04:51,461 performance hint: wlsqm/fitter/expert.pyx:806:0: Exception check on 'expert_solve_one_basic' will always require the GIL to be acquired. 2025-09-08T08:04:51,461 Possible solutions: 2025-09-08T08:04:51,461 1. Declare 'expert_solve_one_basic' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:51,461 2. Use an 'int' return type on 'expert_solve_one_basic' to allow an error code to be returned. 2025-09-08T08:04:52,857 performance hint: wlsqm/fitter/expert.pyx:278:33: Exception check after calling 'CaseManager_del' will always require the GIL to be acquired. 2025-09-08T08:04:52,858 Possible solutions: 2025-09-08T08:04:52,858 1. Declare 'CaseManager_del' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:52,858 2. Use an 'int' return type on 'CaseManager_del' to allow an error code to be returned. 2025-09-08T08:04:52,886 performance hint: wlsqm/fitter/expert.pyx:391:49: Exception check after calling 'expert_prepare_one_3D' will always require the GIL to be acquired. 2025-09-08T08:04:52,886 Possible solutions: 2025-09-08T08:04:52,886 1. Declare 'expert_prepare_one_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:52,886 2. Use an 'int' return type on 'expert_prepare_one_3D' to allow an error code to be returned. 2025-09-08T08:04:52,891 performance hint: wlsqm/fitter/expert.pyx:394:49: Exception check after calling 'expert_prepare_one_3D' will always require the GIL to be acquired. 2025-09-08T08:04:52,891 Possible solutions: 2025-09-08T08:04:52,891 1. Declare 'expert_prepare_one_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:52,891 2. Use an 'int' return type on 'expert_prepare_one_3D' to allow an error code to be returned. 2025-09-08T08:04:52,896 performance hint: wlsqm/fitter/expert.pyx:402:49: Exception check after calling 'expert_prepare_one_2D' will always require the GIL to be acquired. 2025-09-08T08:04:52,896 Possible solutions: 2025-09-08T08:04:52,896 1. Declare 'expert_prepare_one_2D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:52,896 2. Use an 'int' return type on 'expert_prepare_one_2D' to allow an error code to be returned. 2025-09-08T08:04:52,900 performance hint: wlsqm/fitter/expert.pyx:405:49: Exception check after calling 'expert_prepare_one_2D' will always require the GIL to be acquired. 2025-09-08T08:04:52,901 Possible solutions: 2025-09-08T08:04:52,901 1. Declare 'expert_prepare_one_2D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:52,901 2. Use an 'int' return type on 'expert_prepare_one_2D' to allow an error code to be returned. 2025-09-08T08:04:52,905 performance hint: wlsqm/fitter/expert.pyx:413:49: Exception check after calling 'expert_prepare_one_1D' will always require the GIL to be acquired. 2025-09-08T08:04:52,905 Possible solutions: 2025-09-08T08:04:52,905 1. Declare 'expert_prepare_one_1D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:52,905 2. Use an 'int' return type on 'expert_prepare_one_1D' to allow an error code to be returned. 2025-09-08T08:04:52,909 performance hint: wlsqm/fitter/expert.pyx:416:49: Exception check after calling 'expert_prepare_one_1D' will always require the GIL to be acquired. 2025-09-08T08:04:52,909 Possible solutions: 2025-09-08T08:04:52,909 1. Declare 'expert_prepare_one_1D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:52,909 2. Use an 'int' return type on 'expert_prepare_one_1D' to allow an error code to be returned. 2025-09-08T08:04:52,931 performance hint: wlsqm/fitter/expert.pyx:535:50: Exception check after calling 'expert_solve_one_basic' will always require the GIL to be acquired. 2025-09-08T08:04:52,931 Possible solutions: 2025-09-08T08:04:52,931 1. Declare 'expert_solve_one_basic' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:52,931 2. Use an 'int' return type on 'expert_solve_one_basic' to allow an error code to be returned. 2025-09-08T08:04:52,935 performance hint: wlsqm/fitter/expert.pyx:538:50: Exception check after calling 'expert_solve_one_basic' will always require the GIL to be acquired. 2025-09-08T08:04:52,935 Possible solutions: 2025-09-08T08:04:52,935 1. Declare 'expert_solve_one_basic' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:52,936 2. Use an 'int' return type on 'expert_solve_one_basic' to allow an error code to be returned. 2025-09-08T08:04:52,937 performance hint: wlsqm/fitter/expert.pyx:549:41: Exception check after calling 'Case_get_fi' will always require the GIL to be acquired. 2025-09-08T08:04:52,937 Possible solutions: 2025-09-08T08:04:52,937 1. Declare 'Case_get_fi' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:52,937 2. Use an 'int' return type on 'Case_get_fi' to allow an error code to be returned. 2025-09-08T08:04:52,944 performance hint: wlsqm/fitter/expert.pyx:556:50: Exception check after calling 'expert_solve_one_basic' will always require the GIL to be acquired. 2025-09-08T08:04:52,944 Possible solutions: 2025-09-08T08:04:52,944 1. Declare 'expert_solve_one_basic' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:52,944 2. Use an 'int' return type on 'expert_solve_one_basic' to allow an error code to be returned. 2025-09-08T08:04:52,947 performance hint: wlsqm/fitter/expert.pyx:559:50: Exception check after calling 'expert_solve_one_basic' will always require the GIL to be acquired. 2025-09-08T08:04:52,947 Possible solutions: 2025-09-08T08:04:52,948 1. Declare 'expert_solve_one_basic' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:52,948 2. Use an 'int' return type on 'expert_solve_one_basic' to allow an error code to be returned. 2025-09-08T08:04:52,948 performance hint: wlsqm/fitter/expert.pyx:563:41: Exception check after calling 'Case_get_fi' will always require the GIL to be acquired. 2025-09-08T08:04:52,948 Possible solutions: 2025-09-08T08:04:52,949 1. Declare 'Case_get_fi' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:52,949 2. Use an 'int' return type on 'Case_get_fi' to allow an error code to be returned. 2025-09-08T08:04:52,985 performance hint: wlsqm/fitter/expert.pyx:606:41: Exception check after calling 'Case_get_fi' will always require the GIL to be acquired. 2025-09-08T08:04:52,985 Possible solutions: 2025-09-08T08:04:52,985 1. Declare 'Case_get_fi' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:52,985 2. Use an 'int' return type on 'Case_get_fi' to allow an error code to be returned. 2025-09-08T08:04:53,016 performance hint: wlsqm/fitter/expert.pyx:645:41: Exception check after calling 'Case_get_fi' will always require the GIL to be acquired. 2025-09-08T08:04:53,017 Possible solutions: 2025-09-08T08:04:53,017 1. Declare 'Case_get_fi' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:53,017 2. Use an 'int' return type on 'Case_get_fi' to allow an error code to be returned. 2025-09-08T08:04:53,036 performance hint: wlsqm/fitter/expert.pyx:781:18: Exception check after calling 'make_c_3D' will always require the GIL to be acquired. 2025-09-08T08:04:53,036 Possible solutions: 2025-09-08T08:04:53,036 1. Declare 'make_c_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:53,036 2. Use an 'int' return type on 'make_c_3D' to allow an error code to be returned. 2025-09-08T08:04:53,036 performance hint: wlsqm/fitter/expert.pyx:782:15: Exception check after calling 'make_A' will always require the GIL to be acquired. 2025-09-08T08:04:53,036 Possible solutions: 2025-09-08T08:04:53,036 1. Declare 'make_A' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:53,036 2. Use an 'int' return type on 'make_A' to allow an error code to be returned. 2025-09-08T08:04:53,036 performance hint: wlsqm/fitter/expert.pyx:783:21: Exception check after calling 'preprocess_A' will always require the GIL to be acquired. 2025-09-08T08:04:53,036 Possible solutions: 2025-09-08T08:04:53,037 1. Declare 'preprocess_A' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:53,037 2. Use an 'int' return type on 'preprocess_A' to allow an error code to be returned. 2025-09-08T08:04:53,037 performance hint: wlsqm/fitter/expert.pyx:791:18: Exception check after calling 'make_c_2D' will always require the GIL to be acquired. 2025-09-08T08:04:53,037 Possible solutions: 2025-09-08T08:04:53,037 1. Declare 'make_c_2D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:53,037 2. Use an 'int' return type on 'make_c_2D' to allow an error code to be returned. 2025-09-08T08:04:53,037 performance hint: wlsqm/fitter/expert.pyx:792:15: Exception check after calling 'make_A' will always require the GIL to be acquired. 2025-09-08T08:04:53,038 Possible solutions: 2025-09-08T08:04:53,038 1. Declare 'make_A' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:53,038 2. Use an 'int' return type on 'make_A' to allow an error code to be returned. 2025-09-08T08:04:53,038 performance hint: wlsqm/fitter/expert.pyx:793:21: Exception check after calling 'preprocess_A' will always require the GIL to be acquired. 2025-09-08T08:04:53,038 Possible solutions: 2025-09-08T08:04:53,038 1. Declare 'preprocess_A' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:53,038 2. Use an 'int' return type on 'preprocess_A' to allow an error code to be returned. 2025-09-08T08:04:53,038 performance hint: wlsqm/fitter/expert.pyx:801:18: Exception check after calling 'make_c_1D' will always require the GIL to be acquired. 2025-09-08T08:04:53,038 Possible solutions: 2025-09-08T08:04:53,038 1. Declare 'make_c_1D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:53,039 2. Use an 'int' return type on 'make_c_1D' to allow an error code to be returned. 2025-09-08T08:04:53,039 performance hint: wlsqm/fitter/expert.pyx:802:15: Exception check after calling 'make_A' will always require the GIL to be acquired. 2025-09-08T08:04:53,039 Possible solutions: 2025-09-08T08:04:53,039 1. Declare 'make_A' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:53,039 2. Use an 'int' return type on 'make_A' to allow an error code to be returned. 2025-09-08T08:04:53,039 performance hint: wlsqm/fitter/expert.pyx:803:21: Exception check after calling 'preprocess_A' will always require the GIL to be acquired. 2025-09-08T08:04:53,039 Possible solutions: 2025-09-08T08:04:53,039 1. Declare 'preprocess_A' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:53,039 2. Use an 'int' return type on 'preprocess_A' to allow an error code to be returned. 2025-09-08T08:04:53,039 performance hint: wlsqm/fitter/expert.pyx:807:21: Exception check after calling 'Case_set_fi' will always require the GIL to be acquired. 2025-09-08T08:04:53,040 Possible solutions: 2025-09-08T08:04:53,040 1. Declare 'Case_set_fi' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:53,040 2. Use an 'int' return type on 'Case_set_fi' to allow an error code to be returned. 2025-09-08T08:04:53,040 performance hint: wlsqm/fitter/expert.pyx:808:14: Exception check after calling 'solve' will always require the GIL to be acquired. 2025-09-08T08:04:53,040 Possible solutions: 2025-09-08T08:04:53,040 1. Declare 'solve' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:53,040 2. Use an 'int' return type on 'solve' to allow an error code to be returned. 2025-09-08T08:04:53,041 performance hint: wlsqm/fitter/expert.pyx:812:21: Exception check after calling 'Case_set_fi' will always require the GIL to be acquired. 2025-09-08T08:04:53,041 Possible solutions: 2025-09-08T08:04:53,041 1. Declare 'Case_set_fi' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:53,041 2. Use an 'int' return type on 'Case_set_fi' to allow an error code to be returned. 2025-09-08T08:04:53,041 performance hint: wlsqm/fitter/expert.pyx:813:31: Exception check after calling 'solve_iterative' will always require the GIL to be acquired. 2025-09-08T08:04:53,041 Possible solutions: 2025-09-08T08:04:53,041 1. Declare 'solve_iterative' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:53,041 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:53,051 performance hint: wlsqm/fitter/expert.pyx:862:41: Exception check after calling 'interpolate_3D' will always require the GIL to be acquired. 2025-09-08T08:04:53,051 Possible solutions: 2025-09-08T08:04:53,051 1. Declare 'interpolate_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:53,051 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:53,055 performance hint: wlsqm/fitter/expert.pyx:865:41: Exception check after calling 'interpolate_3D' will always require the GIL to be acquired. 2025-09-08T08:04:53,055 Possible solutions: 2025-09-08T08:04:53,055 1. Declare 'interpolate_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:53,055 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:53,058 performance hint: wlsqm/fitter/expert.pyx:869:41: Exception check after calling 'interpolate_2D' will always require the GIL to be acquired. 2025-09-08T08:04:53,058 Possible solutions: 2025-09-08T08:04:53,058 1. Declare 'interpolate_2D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:53,058 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:53,062 performance hint: wlsqm/fitter/expert.pyx:872:41: Exception check after calling 'interpolate_2D' will always require the GIL to be acquired. 2025-09-08T08:04:53,062 Possible solutions: 2025-09-08T08:04:53,062 1. Declare 'interpolate_2D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:53,062 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:53,065 performance hint: wlsqm/fitter/expert.pyx:876:41: Exception check after calling 'interpolate_1D' will always require the GIL to be acquired. 2025-09-08T08:04:53,065 Possible solutions: 2025-09-08T08:04:53,065 1. Declare 'interpolate_1D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:53,065 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:53,068 performance hint: wlsqm/fitter/expert.pyx:879:41: Exception check after calling 'interpolate_1D' will always require the GIL to be acquired. 2025-09-08T08:04:53,068 Possible solutions: 2025-09-08T08:04:53,068 1. Declare 'interpolate_1D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:53,068 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:53,856 warning: wlsqm/fitter/infra.pxd:36:90: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:53,860 warning: wlsqm/fitter/infra.pxd:104:134: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:53,860 warning: wlsqm/fitter/infra.pxd:105:73: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:53,861 warning: wlsqm/fitter/infra.pxd:106:64: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:53,865 warning: wlsqm/fitter/infra.pxd:185:212: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:54,202 warning: wlsqm/utils/lapackdrivers.pxd:82:95: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:54,202 warning: wlsqm/utils/lapackdrivers.pxd:88:63: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:54,202 warning: wlsqm/utils/lapackdrivers.pxd:90:67: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:54,203 warning: wlsqm/utils/lapackdrivers.pxd:91:73: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:54,203 warning: wlsqm/utils/lapackdrivers.pxd:92:86: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:54,204 warning: wlsqm/utils/lapackdrivers.pxd:94:78: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:54,204 warning: wlsqm/utils/lapackdrivers.pxd:95:91: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:54,205 warning: wlsqm/utils/lapackdrivers.pxd:97:78: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:54,205 warning: wlsqm/utils/lapackdrivers.pxd:98:91: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:54,206 warning: wlsqm/utils/lapackdrivers.pxd:100:84: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:54,206 warning: wlsqm/utils/lapackdrivers.pxd:101:97: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:54,207 warning: wlsqm/utils/lapackdrivers.pxd:102:97: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:54,207 warning: wlsqm/utils/lapackdrivers.pxd:103:110: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:54,209 warning: wlsqm/utils/lapackdrivers.pxd:109:61: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:54,209 warning: wlsqm/utils/lapackdrivers.pxd:111:65: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:54,210 warning: wlsqm/utils/lapackdrivers.pxd:112:71: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:54,210 warning: wlsqm/utils/lapackdrivers.pxd:113:84: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:54,211 warning: wlsqm/utils/lapackdrivers.pxd:115:76: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:54,211 warning: wlsqm/utils/lapackdrivers.pxd:116:89: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:54,212 warning: wlsqm/utils/lapackdrivers.pxd:118:76: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:54,212 warning: wlsqm/utils/lapackdrivers.pxd:119:89: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:54,213 warning: wlsqm/utils/lapackdrivers.pxd:121:82: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:54,213 warning: wlsqm/utils/lapackdrivers.pxd:122:95: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:54,214 warning: wlsqm/utils/lapackdrivers.pxd:123:95: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:54,214 warning: wlsqm/utils/lapackdrivers.pxd:124:108: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:54,215 warning: wlsqm/utils/lapackdrivers.pxd:130:68: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:54,276 performance hint: wlsqm/fitter/impl.pyx:43:0: Exception check on 'make_c_nD' will always require the GIL to be acquired. 2025-09-08T08:04:54,276 Possible solutions: 2025-09-08T08:04:54,276 1. Declare 'make_c_nD' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:54,276 2. Use an 'int' return type on 'make_c_nD' to allow an error code to be returned. 2025-09-08T08:04:54,276 performance hint: wlsqm/fitter/impl.pyx:66:0: Exception check on 'make_c_3D' will always require the GIL to be acquired. 2025-09-08T08:04:54,277 Possible solutions: 2025-09-08T08:04:54,277 1. Declare 'make_c_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:54,277 2. Use an 'int' return type on 'make_c_3D' to allow an error code to be returned. 2025-09-08T08:04:54,277 performance hint: wlsqm/fitter/impl.pyx:284:0: Exception check on 'make_c_2D' will always require the GIL to be acquired. 2025-09-08T08:04:54,277 Possible solutions: 2025-09-08T08:04:54,277 1. Declare 'make_c_2D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:54,277 2. Use an 'int' return type on 'make_c_2D' to allow an error code to be returned. 2025-09-08T08:04:54,277 performance hint: wlsqm/fitter/impl.pyx:449:0: Exception check on 'make_c_1D' will always require the GIL to be acquired. 2025-09-08T08:04:54,277 Possible solutions: 2025-09-08T08:04:54,278 1. Declare 'make_c_1D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:54,278 2. Use an 'int' return type on 'make_c_1D' to allow an error code to be returned. 2025-09-08T08:04:54,278 performance hint: wlsqm/fitter/impl.pyx:568:0: Exception check on 'make_A' will always require the GIL to be acquired. 2025-09-08T08:04:54,278 Possible solutions: 2025-09-08T08:04:54,278 1. Declare 'make_A' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:54,278 2. Use an 'int' return type on 'make_A' to allow an error code to be returned. 2025-09-08T08:04:54,278 performance hint: wlsqm/fitter/impl.pyx:622:0: Exception check on 'preprocess_A' will always require the GIL to be acquired. 2025-09-08T08:04:54,278 Possible solutions: 2025-09-08T08:04:54,278 1. Declare 'preprocess_A' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:54,278 2. Use an 'int' return type on 'preprocess_A' to allow an error code to be returned. 2025-09-08T08:04:54,279 performance hint: wlsqm/fitter/impl.pyx:734:0: Exception check on 'solve' will always require the GIL to be acquired. 2025-09-08T08:04:54,279 Possible solutions: 2025-09-08T08:04:54,279 1. Declare 'solve' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:54,279 2. Use an 'int' return type on 'solve' to allow an error code to be returned. 2025-09-08T08:04:54,279 performance hint: wlsqm/fitter/impl.pyx:863:0: Exception check on 'solve_contig' will always require the GIL to be acquired. 2025-09-08T08:04:54,279 Possible solutions: 2025-09-08T08:04:54,279 1. Declare 'solve_contig' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:54,280 2. Use an 'int' return type on 'solve_contig' to allow an error code to be returned. 2025-09-08T08:04:54,280 performance hint: wlsqm/fitter/impl.pxd:47:24: No exception value declared for 'solve_iterative' in pxd file. 2025-09-08T08:04:54,280 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:04:54,280 Suggest adding an explicit exception value. 2025-09-08T08:04:55,579 performance hint: wlsqm/fitter/impl.pyx:45:17: Exception check after calling 'make_c_3D' will always require the GIL to be acquired. 2025-09-08T08:04:55,580 Possible solutions: 2025-09-08T08:04:55,580 1. Declare 'make_c_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:55,580 2. Use an 'int' return type on 'make_c_3D' to allow an error code to be returned. 2025-09-08T08:04:55,580 performance hint: wlsqm/fitter/impl.pyx:47:17: Exception check after calling 'make_c_2D' will always require the GIL to be acquired. 2025-09-08T08:04:55,580 Possible solutions: 2025-09-08T08:04:55,580 1. Declare 'make_c_2D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:55,580 2. Use an 'int' return type on 'make_c_2D' to allow an error code to be returned. 2025-09-08T08:04:55,580 performance hint: wlsqm/fitter/impl.pyx:49:17: Exception check after calling 'make_c_1D' will always require the GIL to be acquired. 2025-09-08T08:04:55,580 Possible solutions: 2025-09-08T08:04:55,580 1. Declare 'make_c_1D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:55,581 2. Use an 'int' return type on 'make_c_1D' to allow an error code to be returned. 2025-09-08T08:04:55,601 performance hint: wlsqm/fitter/impl.pyx:267:27: Exception check after calling 'Case_make_weights' will always require the GIL to be acquired. 2025-09-08T08:04:55,601 Possible solutions: 2025-09-08T08:04:55,601 1. Declare 'Case_make_weights' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:55,601 2. Use an 'int' return type on 'Case_make_weights' to allow an error code to be returned. 2025-09-08T08:04:55,626 performance hint: wlsqm/fitter/impl.pyx:432:27: Exception check after calling 'Case_make_weights' will always require the GIL to be acquired. 2025-09-08T08:04:55,626 Possible solutions: 2025-09-08T08:04:55,626 1. Declare 'Case_make_weights' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:55,626 2. Use an 'int' return type on 'Case_make_weights' to allow an error code to be returned. 2025-09-08T08:04:55,634 performance hint: wlsqm/fitter/impl.pyx:546:27: Exception check after calling 'Case_make_weights' will always require the GIL to be acquired. 2025-09-08T08:04:55,634 Possible solutions: 2025-09-08T08:04:55,634 1. Declare 'Case_make_weights' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:55,634 2. Use an 'int' return type on 'Case_make_weights' to allow an error code to be returned. 2025-09-08T08:04:55,640 performance hint: wlsqm/fitter/impl.pyx:646:29: Exception check after calling 'copygeneral_c' will always require the GIL to be acquired. 2025-09-08T08:04:55,640 Possible solutions: 2025-09-08T08:04:55,640 1. Declare 'copygeneral_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:55,641 2. Use an 'int' return type on 'copygeneral_c' to allow an error code to be returned. 2025-09-08T08:04:55,641 performance hint: wlsqm/fitter/impl.pyx:655:58: Exception check after calling 'rescale_ruiz2001_c' will always require the GIL to be acquired. 2025-09-08T08:04:55,641 Possible solutions: 2025-09-08T08:04:55,641 1. Declare 'rescale_ruiz2001_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:55,641 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:55,641 performance hint: wlsqm/fitter/impl.pyx:656:27: Exception check after calling 'apply_scaling_c' will always require the GIL to be acquired. 2025-09-08T08:04:55,641 Possible solutions: 2025-09-08T08:04:55,641 1. Declare 'apply_scaling_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:55,641 2. Use an 'int' return type on 'apply_scaling_c' to allow an error code to be returned. 2025-09-08T08:04:55,642 performance hint: wlsqm/fitter/impl.pyx:681:29: Exception check after calling 'copygeneral_c' will always require the GIL to be acquired. 2025-09-08T08:04:55,642 Possible solutions: 2025-09-08T08:04:55,642 1. Declare 'copygeneral_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:55,642 2. Use an 'int' return type on 'copygeneral_c' to allow an error code to be returned. 2025-09-08T08:04:55,646 performance hint: wlsqm/fitter/impl.pyx:761:47: Exception check after calling 'Case_get_wrk' will always require the GIL to be acquired. 2025-09-08T08:04:55,646 Possible solutions: 2025-09-08T08:04:55,646 1. Declare 'Case_get_wrk' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:55,647 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:55,656 performance hint: wlsqm/fitter/impl.pyx:888:47: Exception check after calling 'Case_get_wrk' will always require the GIL to be acquired. 2025-09-08T08:04:55,656 Possible solutions: 2025-09-08T08:04:55,656 1. Declare 'Case_get_wrk' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:55,657 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:55,664 performance hint: wlsqm/fitter/impl.pyx:995:9: Exception check after calling 'solve' will always require the GIL to be acquired. 2025-09-08T08:04:55,664 Possible solutions: 2025-09-08T08:04:55,664 1. Declare 'solve' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:55,664 2. Use an 'int' return type on 'solve' to allow an error code to be returned. 2025-09-08T08:04:55,665 performance hint: wlsqm/fitter/impl.pyx:1000:47: Exception check after calling 'Case_get_fk_tmp' will always require the GIL to be acquired. 2025-09-08T08:04:55,665 Possible solutions: 2025-09-08T08:04:55,665 1. Declare 'Case_get_fk_tmp' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:55,665 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:55,665 performance hint: wlsqm/fitter/impl.pyx:1001:47: Exception check after calling 'Case_get_fi_tmp' will always require the GIL to be acquired. 2025-09-08T08:04:55,665 Possible solutions: 2025-09-08T08:04:55,665 1. Declare 'Case_get_fi_tmp' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:55,665 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:55,667 performance hint: wlsqm/fitter/impl.pyx:1025:29: Exception check after calling 'interpolate_nD' will always require the GIL to be acquired. 2025-09-08T08:04:55,667 Possible solutions: 2025-09-08T08:04:55,667 1. Declare 'interpolate_nD' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:55,667 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:55,668 performance hint: wlsqm/fitter/impl.pyx:1075:20: Exception check after calling 'solve_contig' will always require the GIL to be acquired. 2025-09-08T08:04:55,669 Possible solutions: 2025-09-08T08:04:55,669 1. Declare 'solve_contig' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:55,669 2. Use an 'int' return type on 'solve_contig' to allow an error code to be returned. 2025-09-08T08:04:55,733 warning: wlsqm/fitter/infra.pxd:36:90: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:55,738 warning: wlsqm/fitter/infra.pxd:104:134: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:55,739 warning: wlsqm/fitter/infra.pxd:105:73: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:55,739 warning: wlsqm/fitter/infra.pxd:106:64: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:55,743 warning: wlsqm/fitter/infra.pxd:185:212: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:55,770 warning: wlsqm/fitter/infra.pyx:227:90: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:55,776 warning: wlsqm/fitter/infra.pyx:302:134: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:55,781 warning: wlsqm/fitter/infra.pyx:353:73: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:55,784 warning: wlsqm/fitter/infra.pyx:380:64: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:55,785 warning: wlsqm/fitter/infra.pyx:385:66: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:55,797 warning: wlsqm/fitter/infra.pyx:537:212: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:55,816 warning: wlsqm/fitter/infra.pyx:790:52: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:56,037 performance hint: wlsqm/fitter/infra.pxd:18:23: No exception value declared for 'number_of_dofs' in pxd file. 2025-09-08T08:04:56,037 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:04:56,038 Suggest adding an explicit exception value. 2025-09-08T08:04:56,038 performance hint: wlsqm/fitter/infra.pxd:19:31: No exception value declared for 'number_of_reduced_dofs' in pxd file. 2025-09-08T08:04:56,038 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:04:56,038 Suggest adding an explicit exception value. 2025-09-08T08:04:56,038 performance hint: wlsqm/fitter/infra.pxd:20:14: No exception value declared for 'remap' in pxd file. 2025-09-08T08:04:56,038 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:04:56,038 Suggest adding an explicit exception value. 2025-09-08T08:04:56,039 performance hint: wlsqm/fitter/infra.pyx:276:0: Exception check on 'Allocator_free' will always require the GIL to be acquired. 2025-09-08T08:04:56,039 Possible solutions: 2025-09-08T08:04:56,039 1. Declare 'Allocator_free' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,039 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:04:56,039 performance hint: wlsqm/fitter/infra.pxd:39:33: No exception value declared for 'Allocator_size_remaining' in pxd file. 2025-09-08T08:04:56,040 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:04:56,040 Suggest adding an explicit exception value. 2025-09-08T08:04:56,040 performance hint: wlsqm/fitter/infra.pyx:285:0: Exception check on 'Allocator_del' will always require the GIL to be acquired. 2025-09-08T08:04:56,040 Possible solutions: 2025-09-08T08:04:56,040 1. Declare 'Allocator_del' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,040 2. Use an 'int' return type on 'Allocator_del' to allow an error code to be returned. 2025-09-08T08:04:56,041 performance hint: wlsqm/fitter/infra.pyx:467:0: Exception check on 'CaseManager_deallocate' will always require the GIL to be acquired. 2025-09-08T08:04:56,041 Possible solutions: 2025-09-08T08:04:56,041 1. Declare 'CaseManager_deallocate' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,041 2. Use an 'int' return type on 'CaseManager_deallocate' to allow an error code to be returned. 2025-09-08T08:04:56,041 performance hint: wlsqm/fitter/infra.pyx:489:0: Exception check on 'CaseManager_del' will always require the GIL to be acquired. 2025-09-08T08:04:56,041 Possible solutions: 2025-09-08T08:04:56,041 1. Declare 'CaseManager_del' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,042 2. Use an 'int' return type on 'CaseManager_del' to allow an error code to be returned. 2025-09-08T08:04:56,043 performance hint: wlsqm/fitter/infra.pyx:657:0: Exception check on 'Case_make_weights' will always require the GIL to be acquired. 2025-09-08T08:04:56,043 Possible solutions: 2025-09-08T08:04:56,043 1. Declare 'Case_make_weights' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,043 2. Use an 'int' return type on 'Case_make_weights' to allow an error code to be returned. 2025-09-08T08:04:56,043 performance hint: wlsqm/fitter/infra.pyx:699:0: Exception check on 'Case_determine_sizes' will always require the GIL to be acquired. 2025-09-08T08:04:56,043 Possible solutions: 2025-09-08T08:04:56,043 1. Declare 'Case_determine_sizes' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,043 2. Use an 'int' return type on 'Case_determine_sizes' to allow an error code to be returned. 2025-09-08T08:04:56,044 performance hint: wlsqm/fitter/infra.pyx:771:0: Exception check on 'Case_set_fi' will always require the GIL to be acquired. 2025-09-08T08:04:56,044 Possible solutions: 2025-09-08T08:04:56,044 1. Declare 'Case_set_fi' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,044 2. Use an 'int' return type on 'Case_set_fi' to allow an error code to be returned. 2025-09-08T08:04:56,044 performance hint: wlsqm/fitter/infra.pyx:781:0: Exception check on 'Case_get_fi' will always require the GIL to be acquired. 2025-09-08T08:04:56,044 Possible solutions: 2025-09-08T08:04:56,044 1. Declare 'Case_get_fi' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,044 2. Use an 'int' return type on 'Case_get_fi' to allow an error code to be returned. 2025-09-08T08:04:56,044 performance hint: wlsqm/fitter/infra.pyx:868:0: Exception check on 'Case_deallocate' will always require the GIL to be acquired. 2025-09-08T08:04:56,044 Possible solutions: 2025-09-08T08:04:56,045 1. Declare 'Case_deallocate' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,045 2. Use an 'int' return type on 'Case_deallocate' to allow an error code to be returned. 2025-09-08T08:04:56,045 performance hint: wlsqm/fitter/infra.pyx:917:0: Exception check on 'Case_del' will always require the GIL to be acquired. 2025-09-08T08:04:56,045 Possible solutions: 2025-09-08T08:04:56,045 1. Declare 'Case_del' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,045 2. Use an 'int' return type on 'Case_del' to allow an error code to be returned. 2025-09-08T08:04:56,306 performance hint: wlsqm/fitter/infra.pyx:474:31: Exception check after calling 'Case_deallocate' will always require the GIL to be acquired. 2025-09-08T08:04:56,306 Possible solutions: 2025-09-08T08:04:56,306 1. Declare 'Case_deallocate' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,307 2. Use an 'int' return type on 'Case_deallocate' to allow an error code to be returned. 2025-09-08T08:04:56,307 performance hint: wlsqm/fitter/infra.pyx:477:30: Exception check after calling 'Allocator_free' will always require the GIL to be acquired. 2025-09-08T08:04:56,307 Possible solutions: 2025-09-08T08:04:56,307 1. Declare 'Allocator_free' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,307 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:04:56,307 performance hint: wlsqm/fitter/infra.pyx:479:30: Exception check after calling 'Allocator_free' will always require the GIL to be acquired. 2025-09-08T08:04:56,307 Possible solutions: 2025-09-08T08:04:56,308 1. Declare 'Allocator_free' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,308 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:04:56,308 performance hint: wlsqm/fitter/infra.pyx:481:30: Exception check after calling 'Allocator_free' will always require the GIL to be acquired. 2025-09-08T08:04:56,308 Possible solutions: 2025-09-08T08:04:56,308 1. Declare 'Allocator_free' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,308 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:04:56,308 performance hint: wlsqm/fitter/infra.pyx:484:25: Exception check after calling 'Allocator_del' will always require the GIL to be acquired. 2025-09-08T08:04:56,308 Possible solutions: 2025-09-08T08:04:56,308 1. Declare 'Allocator_del' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,309 2. Use an 'int' return type on 'Allocator_del' to allow an error code to be returned. 2025-09-08T08:04:56,309 performance hint: wlsqm/fitter/infra.pyx:492:30: Exception check after calling 'CaseManager_deallocate' will always require the GIL to be acquired. 2025-09-08T08:04:56,310 Possible solutions: 2025-09-08T08:04:56,310 1. Declare 'CaseManager_deallocate' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,310 2. Use an 'int' return type on 'CaseManager_deallocate' to allow an error code to be returned. 2025-09-08T08:04:56,310 performance hint: wlsqm/fitter/infra.pyx:496:20: Exception check after calling 'Case_del' will always require the GIL to be acquired. 2025-09-08T08:04:56,310 Possible solutions: 2025-09-08T08:04:56,310 1. Declare 'Case_del' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,310 2. Use an 'int' return type on 'Case_del' to allow an error code to be returned. 2025-09-08T08:04:56,331 performance hint: wlsqm/fitter/infra.pyx:798:24: Exception check after calling 'Case_determine_sizes' will always require the GIL to be acquired. 2025-09-08T08:04:56,331 Possible solutions: 2025-09-08T08:04:56,331 1. Declare 'Case_determine_sizes' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,331 2. Use an 'int' return type on 'Case_determine_sizes' to allow an error code to be returned. 2025-09-08T08:04:56,340 performance hint: wlsqm/fitter/infra.pyx:872:22: Exception check after calling 'Allocator_free' will always require the GIL to be acquired. 2025-09-08T08:04:56,340 Possible solutions: 2025-09-08T08:04:56,340 1. Declare 'Allocator_free' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,340 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:04:56,340 performance hint: wlsqm/fitter/infra.pyx:874:22: Exception check after calling 'Allocator_free' will always require the GIL to be acquired. 2025-09-08T08:04:56,340 Possible solutions: 2025-09-08T08:04:56,340 1. Declare 'Allocator_free' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,341 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:04:56,341 performance hint: wlsqm/fitter/infra.pyx:877:22: Exception check after calling 'Allocator_free' will always require the GIL to be acquired. 2025-09-08T08:04:56,341 Possible solutions: 2025-09-08T08:04:56,341 1. Declare 'Allocator_free' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,341 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:04:56,341 performance hint: wlsqm/fitter/infra.pyx:880:22: Exception check after calling 'Allocator_free' will always require the GIL to be acquired. 2025-09-08T08:04:56,341 Possible solutions: 2025-09-08T08:04:56,341 1. Declare 'Allocator_free' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,341 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:04:56,341 performance hint: wlsqm/fitter/infra.pyx:882:22: Exception check after calling 'Allocator_free' will always require the GIL to be acquired. 2025-09-08T08:04:56,342 Possible solutions: 2025-09-08T08:04:56,342 1. Declare 'Allocator_free' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,342 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:04:56,342 performance hint: wlsqm/fitter/infra.pyx:886:26: Exception check after calling 'Allocator_free' will always require the GIL to be acquired. 2025-09-08T08:04:56,342 Possible solutions: 2025-09-08T08:04:56,342 1. Declare 'Allocator_free' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,342 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:04:56,342 performance hint: wlsqm/fitter/infra.pyx:888:26: Exception check after calling 'Allocator_free' will always require the GIL to be acquired. 2025-09-08T08:04:56,342 Possible solutions: 2025-09-08T08:04:56,342 1. Declare 'Allocator_free' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,343 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:04:56,343 performance hint: wlsqm/fitter/infra.pyx:890:26: Exception check after calling 'Allocator_free' will always require the GIL to be acquired. 2025-09-08T08:04:56,343 Possible solutions: 2025-09-08T08:04:56,343 1. Declare 'Allocator_free' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,343 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:04:56,343 performance hint: wlsqm/fitter/infra.pyx:892:26: Exception check after calling 'Allocator_free' will always require the GIL to be acquired. 2025-09-08T08:04:56,343 Possible solutions: 2025-09-08T08:04:56,343 1. Declare 'Allocator_free' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,343 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:04:56,343 performance hint: wlsqm/fitter/infra.pyx:895:26: Exception check after calling 'Allocator_free' will always require the GIL to be acquired. 2025-09-08T08:04:56,344 Possible solutions: 2025-09-08T08:04:56,344 1. Declare 'Allocator_free' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,344 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:04:56,344 performance hint: wlsqm/fitter/infra.pyx:897:26: Exception check after calling 'Allocator_free' will always require the GIL to be acquired. 2025-09-08T08:04:56,344 Possible solutions: 2025-09-08T08:04:56,344 1. Declare 'Allocator_free' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,344 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:04:56,344 performance hint: wlsqm/fitter/infra.pyx:900:26: Exception check after calling 'Allocator_free' will always require the GIL to be acquired. 2025-09-08T08:04:56,344 Possible solutions: 2025-09-08T08:04:56,344 1. Declare 'Allocator_free' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,345 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:04:56,345 performance hint: wlsqm/fitter/infra.pyx:902:26: Exception check after calling 'Allocator_free' will always require the GIL to be acquired. 2025-09-08T08:04:56,345 Possible solutions: 2025-09-08T08:04:56,345 1. Declare 'Allocator_free' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,345 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:04:56,346 performance hint: wlsqm/fitter/infra.pyx:919:23: Exception check after calling 'Case_deallocate' will always require the GIL to be acquired. 2025-09-08T08:04:56,346 Possible solutions: 2025-09-08T08:04:56,346 1. Declare 'Case_deallocate' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,346 2. Use an 'int' return type on 'Case_deallocate' to allow an error code to be returned. 2025-09-08T08:04:56,346 performance hint: wlsqm/fitter/infra.pyx:922:25: Exception check after calling 'Allocator_del' will always require the GIL to be acquired. 2025-09-08T08:04:56,346 Possible solutions: 2025-09-08T08:04:56,346 1. Declare 'Allocator_del' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:56,347 2. Use an 'int' return type on 'Allocator_del' to allow an error code to be returned. 2025-09-08T08:04:56,796 warning: wlsqm/fitter/infra.pxd:36:90: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:56,800 warning: wlsqm/fitter/infra.pxd:104:134: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:56,801 warning: wlsqm/fitter/infra.pxd:105:73: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:56,801 warning: wlsqm/fitter/infra.pxd:106:64: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:56,805 warning: wlsqm/fitter/infra.pxd:185:212: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:04:57,110 performance hint: wlsqm/fitter/interp.pxd:17:23: No exception value declared for 'interpolate_nD' in pxd file. 2025-09-08T08:04:57,110 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:04:57,111 Suggest adding an explicit exception value. 2025-09-08T08:04:57,111 performance hint: wlsqm/fitter/interp.pxd:19:23: No exception value declared for 'interpolate_3D' in pxd file. 2025-09-08T08:04:57,111 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:04:57,111 Suggest adding an explicit exception value. 2025-09-08T08:04:57,112 performance hint: wlsqm/fitter/interp.pxd:20:23: No exception value declared for 'interpolate_2D' in pxd file. 2025-09-08T08:04:57,112 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:04:57,112 Suggest adding an explicit exception value. 2025-09-08T08:04:57,112 performance hint: wlsqm/fitter/interp.pxd:21:23: No exception value declared for 'interpolate_1D' in pxd file. 2025-09-08T08:04:57,112 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:04:57,112 Suggest adding an explicit exception value. 2025-09-08T08:04:58,937 performance hint: wlsqm/fitter/interp.pyx:284:33: Exception check after calling 'taylor_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,937 Possible solutions: 2025-09-08T08:04:58,937 1. Declare 'taylor_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,937 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,942 performance hint: wlsqm/fitter/interp.pyx:344:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,942 Possible solutions: 2025-09-08T08:04:58,942 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,942 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,946 performance hint: wlsqm/fitter/interp.pyx:371:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,946 Possible solutions: 2025-09-08T08:04:58,946 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,946 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,949 performance hint: wlsqm/fitter/interp.pyx:398:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,949 Possible solutions: 2025-09-08T08:04:58,949 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,950 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,952 performance hint: wlsqm/fitter/interp.pyx:417:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,952 Possible solutions: 2025-09-08T08:04:58,952 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,952 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,954 performance hint: wlsqm/fitter/interp.pyx:433:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,955 Possible solutions: 2025-09-08T08:04:58,955 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,955 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,957 performance hint: wlsqm/fitter/interp.pyx:449:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,957 Possible solutions: 2025-09-08T08:04:58,957 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,957 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,959 performance hint: wlsqm/fitter/interp.pyx:465:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,960 Possible solutions: 2025-09-08T08:04:58,960 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,960 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,962 performance hint: wlsqm/fitter/interp.pyx:481:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,962 Possible solutions: 2025-09-08T08:04:58,962 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,962 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,964 performance hint: wlsqm/fitter/interp.pyx:497:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,965 Possible solutions: 2025-09-08T08:04:58,965 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,965 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,966 performance hint: wlsqm/fitter/interp.pyx:509:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,966 Possible solutions: 2025-09-08T08:04:58,966 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,967 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,968 performance hint: wlsqm/fitter/interp.pyx:518:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,968 Possible solutions: 2025-09-08T08:04:58,968 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,968 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,969 performance hint: wlsqm/fitter/interp.pyx:527:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,969 Possible solutions: 2025-09-08T08:04:58,969 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,970 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,971 performance hint: wlsqm/fitter/interp.pyx:536:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,971 Possible solutions: 2025-09-08T08:04:58,971 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,971 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,973 performance hint: wlsqm/fitter/interp.pyx:545:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,973 Possible solutions: 2025-09-08T08:04:58,973 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,973 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,974 performance hint: wlsqm/fitter/interp.pyx:554:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,975 Possible solutions: 2025-09-08T08:04:58,975 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,975 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,976 performance hint: wlsqm/fitter/interp.pyx:563:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,976 Possible solutions: 2025-09-08T08:04:58,976 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,976 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,977 performance hint: wlsqm/fitter/interp.pyx:572:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,978 Possible solutions: 2025-09-08T08:04:58,978 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,978 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,979 performance hint: wlsqm/fitter/interp.pyx:581:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,979 Possible solutions: 2025-09-08T08:04:58,979 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,979 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,980 performance hint: wlsqm/fitter/interp.pyx:590:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,981 Possible solutions: 2025-09-08T08:04:58,981 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,981 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,981 performance hint: wlsqm/fitter/interp.pyx:597:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,981 Possible solutions: 2025-09-08T08:04:58,981 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,982 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,982 performance hint: wlsqm/fitter/interp.pyx:601:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,982 Possible solutions: 2025-09-08T08:04:58,982 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,982 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,983 performance hint: wlsqm/fitter/interp.pyx:605:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,983 Possible solutions: 2025-09-08T08:04:58,983 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,983 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,984 performance hint: wlsqm/fitter/interp.pyx:609:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,984 Possible solutions: 2025-09-08T08:04:58,984 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,984 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,985 performance hint: wlsqm/fitter/interp.pyx:613:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,985 Possible solutions: 2025-09-08T08:04:58,985 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,985 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,985 performance hint: wlsqm/fitter/interp.pyx:617:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,986 Possible solutions: 2025-09-08T08:04:58,986 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,986 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,986 performance hint: wlsqm/fitter/interp.pyx:621:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,986 Possible solutions: 2025-09-08T08:04:58,986 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,987 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,987 performance hint: wlsqm/fitter/interp.pyx:625:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,987 Possible solutions: 2025-09-08T08:04:58,987 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,987 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,988 performance hint: wlsqm/fitter/interp.pyx:629:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,988 Possible solutions: 2025-09-08T08:04:58,988 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,988 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,989 performance hint: wlsqm/fitter/interp.pyx:633:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,989 Possible solutions: 2025-09-08T08:04:58,989 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,989 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,990 performance hint: wlsqm/fitter/interp.pyx:637:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,990 Possible solutions: 2025-09-08T08:04:58,990 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,990 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,990 performance hint: wlsqm/fitter/interp.pyx:641:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,991 Possible solutions: 2025-09-08T08:04:58,991 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,991 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,991 performance hint: wlsqm/fitter/interp.pyx:645:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,991 Possible solutions: 2025-09-08T08:04:58,991 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,992 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,992 performance hint: wlsqm/fitter/interp.pyx:649:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,992 Possible solutions: 2025-09-08T08:04:58,992 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,992 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,993 performance hint: wlsqm/fitter/interp.pyx:653:34: Exception check after calling 'general_3D' will always require the GIL to be acquired. 2025-09-08T08:04:58,993 Possible solutions: 2025-09-08T08:04:58,993 1. Declare 'general_3D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,993 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,995 performance hint: wlsqm/fitter/interp.pyx:682:33: Exception check after calling 'taylor_2D' will always require the GIL to be acquired. 2025-09-08T08:04:58,995 Possible solutions: 2025-09-08T08:04:58,995 1. Declare 'taylor_2D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,995 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:58,998 performance hint: wlsqm/fitter/interp.pyx:732:34: Exception check after calling 'general_2D' will always require the GIL to be acquired. 2025-09-08T08:04:58,998 Possible solutions: 2025-09-08T08:04:58,998 1. Declare 'general_2D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:58,998 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:59,000 performance hint: wlsqm/fitter/interp.pyx:749:34: Exception check after calling 'general_2D' will always require the GIL to be acquired. 2025-09-08T08:04:59,001 Possible solutions: 2025-09-08T08:04:59,001 1. Declare 'general_2D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:59,001 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:59,002 performance hint: wlsqm/fitter/interp.pyx:764:34: Exception check after calling 'general_2D' will always require the GIL to be acquired. 2025-09-08T08:04:59,003 Possible solutions: 2025-09-08T08:04:59,003 1. Declare 'general_2D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:59,003 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:59,004 performance hint: wlsqm/fitter/interp.pyx:776:34: Exception check after calling 'general_2D' will always require the GIL to be acquired. 2025-09-08T08:04:59,004 Possible solutions: 2025-09-08T08:04:59,005 1. Declare 'general_2D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:59,005 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:59,006 performance hint: wlsqm/fitter/interp.pyx:788:34: Exception check after calling 'general_2D' will always require the GIL to be acquired. 2025-09-08T08:04:59,006 Possible solutions: 2025-09-08T08:04:59,006 1. Declare 'general_2D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:59,006 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:59,007 performance hint: wlsqm/fitter/interp.pyx:799:34: Exception check after calling 'general_2D' will always require the GIL to be acquired. 2025-09-08T08:04:59,008 Possible solutions: 2025-09-08T08:04:59,008 1. Declare 'general_2D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:59,008 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:59,009 performance hint: wlsqm/fitter/interp.pyx:807:34: Exception check after calling 'general_2D' will always require the GIL to be acquired. 2025-09-08T08:04:59,009 Possible solutions: 2025-09-08T08:04:59,009 1. Declare 'general_2D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:59,009 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:59,010 performance hint: wlsqm/fitter/interp.pyx:815:34: Exception check after calling 'general_2D' will always require the GIL to be acquired. 2025-09-08T08:04:59,010 Possible solutions: 2025-09-08T08:04:59,010 1. Declare 'general_2D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:59,010 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:59,011 performance hint: wlsqm/fitter/interp.pyx:823:34: Exception check after calling 'general_2D' will always require the GIL to be acquired. 2025-09-08T08:04:59,011 Possible solutions: 2025-09-08T08:04:59,012 1. Declare 'general_2D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:59,012 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:59,012 performance hint: wlsqm/fitter/interp.pyx:830:34: Exception check after calling 'general_2D' will always require the GIL to be acquired. 2025-09-08T08:04:59,012 Possible solutions: 2025-09-08T08:04:59,012 1. Declare 'general_2D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:59,012 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:59,013 performance hint: wlsqm/fitter/interp.pyx:834:34: Exception check after calling 'general_2D' will always require the GIL to be acquired. 2025-09-08T08:04:59,013 Possible solutions: 2025-09-08T08:04:59,013 1. Declare 'general_2D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:59,013 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:59,014 performance hint: wlsqm/fitter/interp.pyx:838:34: Exception check after calling 'general_2D' will always require the GIL to be acquired. 2025-09-08T08:04:59,014 Possible solutions: 2025-09-08T08:04:59,014 1. Declare 'general_2D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:59,014 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:59,015 performance hint: wlsqm/fitter/interp.pyx:842:34: Exception check after calling 'general_2D' will always require the GIL to be acquired. 2025-09-08T08:04:59,015 Possible solutions: 2025-09-08T08:04:59,015 1. Declare 'general_2D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:59,015 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:59,015 performance hint: wlsqm/fitter/interp.pyx:846:34: Exception check after calling 'general_2D' will always require the GIL to be acquired. 2025-09-08T08:04:59,016 Possible solutions: 2025-09-08T08:04:59,016 1. Declare 'general_2D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:59,016 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:59,017 performance hint: wlsqm/fitter/interp.pyx:874:33: Exception check after calling 'taylor_1D' will always require the GIL to be acquired. 2025-09-08T08:04:59,017 Possible solutions: 2025-09-08T08:04:59,017 1. Declare 'taylor_1D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:59,017 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:59,020 performance hint: wlsqm/fitter/interp.pyx:910:34: Exception check after calling 'general_1D' will always require the GIL to be acquired. 2025-09-08T08:04:59,020 Possible solutions: 2025-09-08T08:04:59,020 1. Declare 'general_1D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:59,020 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:59,021 performance hint: wlsqm/fitter/interp.pyx:922:34: Exception check after calling 'general_1D' will always require the GIL to be acquired. 2025-09-08T08:04:59,021 Possible solutions: 2025-09-08T08:04:59,021 1. Declare 'general_1D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:59,021 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:59,022 performance hint: wlsqm/fitter/interp.pyx:932:34: Exception check after calling 'general_1D' will always require the GIL to be acquired. 2025-09-08T08:04:59,022 Possible solutions: 2025-09-08T08:04:59,022 1. Declare 'general_1D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:59,022 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:59,023 performance hint: wlsqm/fitter/interp.pyx:939:34: Exception check after calling 'general_1D' will always require the GIL to be acquired. 2025-09-08T08:04:59,023 Possible solutions: 2025-09-08T08:04:59,023 1. Declare 'general_1D' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:04:59,023 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:04:59,693 performance hint: wlsqm/fitter/polyeval.pxd:15:18: No exception value declared for 'taylor_3D' in pxd file. 2025-09-08T08:04:59,693 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:04:59,693 Suggest adding an explicit exception value. 2025-09-08T08:04:59,694 performance hint: wlsqm/fitter/polyeval.pxd:16:19: No exception value declared for 'general_3D' in pxd file. 2025-09-08T08:04:59,694 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:04:59,694 Suggest adding an explicit exception value. 2025-09-08T08:04:59,694 performance hint: wlsqm/fitter/polyeval.pxd:18:18: No exception value declared for 'taylor_2D' in pxd file. 2025-09-08T08:04:59,694 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:04:59,694 Suggest adding an explicit exception value. 2025-09-08T08:04:59,695 performance hint: wlsqm/fitter/polyeval.pxd:19:19: No exception value declared for 'general_2D' in pxd file. 2025-09-08T08:04:59,695 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:04:59,695 Suggest adding an explicit exception value. 2025-09-08T08:04:59,695 performance hint: wlsqm/fitter/polyeval.pxd:21:18: No exception value declared for 'taylor_1D' in pxd file. 2025-09-08T08:04:59,695 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:04:59,696 Suggest adding an explicit exception value. 2025-09-08T08:04:59,696 performance hint: wlsqm/fitter/polyeval.pxd:22:19: No exception value declared for 'general_1D' in pxd file. 2025-09-08T08:04:59,696 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:04:59,696 Suggest adding an explicit exception value. 2025-09-08T08:05:01,094 warning: wlsqm/fitter/simple.pxd:31:181: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:01,096 warning: wlsqm/fitter/simple.pxd:34:199: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:01,098 warning: wlsqm/fitter/simple.pxd:45:174: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:01,100 warning: wlsqm/fitter/simple.pxd:51:192: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:01,103 warning: wlsqm/fitter/simple.pxd:61:195: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:01,106 warning: wlsqm/fitter/simple.pxd:67:213: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:01,582 warning: wlsqm/fitter/simple.pyx:611:181: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:01,587 warning: wlsqm/fitter/simple.pyx:660:199: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:01,593 warning: wlsqm/fitter/simple.pyx:727:174: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:01,605 warning: wlsqm/fitter/simple.pyx:848:192: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:01,618 warning: wlsqm/fitter/simple.pyx:954:195: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:01,630 warning: wlsqm/fitter/simple.pyx:1067:213: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:01,902 warning: wlsqm/fitter/infra.pxd:36:90: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:01,906 warning: wlsqm/fitter/infra.pxd:104:134: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:01,906 warning: wlsqm/fitter/infra.pxd:105:73: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:01,907 warning: wlsqm/fitter/infra.pxd:106:64: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:01,910 warning: wlsqm/fitter/infra.pxd:185:212: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:03,781 performance hint: wlsqm/fitter/simple.pyx:633:18: Exception check after calling 'make_c_nD' will always require the GIL to be acquired. 2025-09-08T08:05:03,781 Possible solutions: 2025-09-08T08:05:03,782 1. Declare 'make_c_nD' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,782 2. Use an 'int' return type on 'make_c_nD' to allow an error code to be returned. 2025-09-08T08:05:03,782 performance hint: wlsqm/fitter/simple.pyx:636:15: Exception check after calling 'make_A' will always require the GIL to be acquired. 2025-09-08T08:05:03,782 Possible solutions: 2025-09-08T08:05:03,782 1. Declare 'make_A' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,782 2. Use an 'int' return type on 'make_A' to allow an error code to be returned. 2025-09-08T08:05:03,782 performance hint: wlsqm/fitter/simple.pyx:639:21: Exception check after calling 'preprocess_A' will always require the GIL to be acquired. 2025-09-08T08:05:03,782 Possible solutions: 2025-09-08T08:05:03,782 1. Declare 'preprocess_A' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,783 2. Use an 'int' return type on 'preprocess_A' to allow an error code to be returned. 2025-09-08T08:05:03,783 performance hint: wlsqm/fitter/simple.pyx:643:21: Exception check after calling 'Case_set_fi' will always require the GIL to be acquired. 2025-09-08T08:05:03,783 Possible solutions: 2025-09-08T08:05:03,783 1. Declare 'Case_set_fi' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,783 2. Use an 'int' return type on 'Case_set_fi' to allow an error code to be returned. 2025-09-08T08:05:03,783 performance hint: wlsqm/fitter/simple.pyx:644:14: Exception check after calling 'solve' will always require the GIL to be acquired. 2025-09-08T08:05:03,783 Possible solutions: 2025-09-08T08:05:03,783 1. Declare 'solve' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,783 2. Use an 'int' return type on 'solve' to allow an error code to be returned. 2025-09-08T08:05:03,783 performance hint: wlsqm/fitter/simple.pyx:645:21: Exception check after calling 'Case_get_fi' will always require the GIL to be acquired. 2025-09-08T08:05:03,784 Possible solutions: 2025-09-08T08:05:03,784 1. Declare 'Case_get_fi' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,784 2. Use an 'int' return type on 'Case_get_fi' to allow an error code to be returned. 2025-09-08T08:05:03,784 performance hint: wlsqm/fitter/simple.pyx:649:18: Exception check after calling 'Case_del' will always require the GIL to be acquired. 2025-09-08T08:05:03,784 Possible solutions: 2025-09-08T08:05:03,784 1. Declare 'Case_del' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,784 2. Use an 'int' return type on 'Case_del' to allow an error code to be returned. 2025-09-08T08:05:03,786 performance hint: wlsqm/fitter/simple.pyx:677:18: Exception check after calling 'make_c_nD' will always require the GIL to be acquired. 2025-09-08T08:05:03,786 Possible solutions: 2025-09-08T08:05:03,786 1. Declare 'make_c_nD' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,786 2. Use an 'int' return type on 'make_c_nD' to allow an error code to be returned. 2025-09-08T08:05:03,787 performance hint: wlsqm/fitter/simple.pyx:678:15: Exception check after calling 'make_A' will always require the GIL to be acquired. 2025-09-08T08:05:03,787 Possible solutions: 2025-09-08T08:05:03,787 1. Declare 'make_A' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,787 2. Use an 'int' return type on 'make_A' to allow an error code to be returned. 2025-09-08T08:05:03,787 performance hint: wlsqm/fitter/simple.pyx:679:21: Exception check after calling 'preprocess_A' will always require the GIL to be acquired. 2025-09-08T08:05:03,787 Possible solutions: 2025-09-08T08:05:03,787 1. Declare 'preprocess_A' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,787 2. Use an 'int' return type on 'preprocess_A' to allow an error code to be returned. 2025-09-08T08:05:03,787 performance hint: wlsqm/fitter/simple.pyx:682:21: Exception check after calling 'Case_set_fi' will always require the GIL to be acquired. 2025-09-08T08:05:03,787 Possible solutions: 2025-09-08T08:05:03,787 1. Declare 'Case_set_fi' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,788 2. Use an 'int' return type on 'Case_set_fi' to allow an error code to be returned. 2025-09-08T08:05:03,788 performance hint: wlsqm/fitter/simple.pyx:683:52: Exception check after calling 'solve_iterative' will always require the GIL to be acquired. 2025-09-08T08:05:03,788 Possible solutions: 2025-09-08T08:05:03,788 1. Declare 'solve_iterative' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,788 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:05:03,788 performance hint: wlsqm/fitter/simple.pyx:684:21: Exception check after calling 'Case_get_fi' will always require the GIL to be acquired. 2025-09-08T08:05:03,788 Possible solutions: 2025-09-08T08:05:03,788 1. Declare 'Case_get_fi' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,788 2. Use an 'int' return type on 'Case_get_fi' to allow an error code to be returned. 2025-09-08T08:05:03,788 performance hint: wlsqm/fitter/simple.pyx:686:18: Exception check after calling 'Case_del' will always require the GIL to be acquired. 2025-09-08T08:05:03,789 Possible solutions: 2025-09-08T08:05:03,789 1. Declare 'Case_del' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,789 2. Use an 'int' return type on 'Case_del' to allow an error code to be returned. 2025-09-08T08:05:03,797 performance hint: wlsqm/fitter/simple.pyx:769:26: Exception check after calling 'make_c_nD' will always require the GIL to be acquired. 2025-09-08T08:05:03,797 Possible solutions: 2025-09-08T08:05:03,797 1. Declare 'make_c_nD' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,797 2. Use an 'int' return type on 'make_c_nD' to allow an error code to be returned. 2025-09-08T08:05:03,798 performance hint: wlsqm/fitter/simple.pyx:770:23: Exception check after calling 'make_A' will always require the GIL to be acquired. 2025-09-08T08:05:03,798 Possible solutions: 2025-09-08T08:05:03,798 1. Declare 'make_A' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,798 2. Use an 'int' return type on 'make_A' to allow an error code to be returned. 2025-09-08T08:05:03,798 performance hint: wlsqm/fitter/simple.pyx:771:29: Exception check after calling 'preprocess_A' will always require the GIL to be acquired. 2025-09-08T08:05:03,798 Possible solutions: 2025-09-08T08:05:03,798 1. Declare 'preprocess_A' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,798 2. Use an 'int' return type on 'preprocess_A' to allow an error code to be returned. 2025-09-08T08:05:03,798 performance hint: wlsqm/fitter/simple.pyx:772:29: Exception check after calling 'Case_set_fi' will always require the GIL to be acquired. 2025-09-08T08:05:03,798 Possible solutions: 2025-09-08T08:05:03,799 1. Declare 'Case_set_fi' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,799 2. Use an 'int' return type on 'Case_set_fi' to allow an error code to be returned. 2025-09-08T08:05:03,801 performance hint: wlsqm/fitter/simple.pyx:774:26: Exception check after calling 'solve' will always require the GIL to be acquired. 2025-09-08T08:05:03,801 Possible solutions: 2025-09-08T08:05:03,801 1. Declare 'solve' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,801 2. Use an 'int' return type on 'solve' to allow an error code to be returned. 2025-09-08T08:05:03,806 performance hint: wlsqm/fitter/simple.pyx:776:26: Exception check after calling 'solve' will always require the GIL to be acquired. 2025-09-08T08:05:03,806 Possible solutions: 2025-09-08T08:05:03,806 1. Declare 'solve' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,806 2. Use an 'int' return type on 'solve' to allow an error code to be returned. 2025-09-08T08:05:03,807 performance hint: wlsqm/fitter/simple.pyx:787:29: Exception check after calling 'Case_get_fi' will always require the GIL to be acquired. 2025-09-08T08:05:03,807 Possible solutions: 2025-09-08T08:05:03,807 1. Declare 'Case_get_fi' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,807 2. Use an 'int' return type on 'Case_get_fi' to allow an error code to be returned. 2025-09-08T08:05:03,812 performance hint: wlsqm/fitter/simple.pyx:803:26: Exception check after calling 'make_c_nD' will always require the GIL to be acquired. 2025-09-08T08:05:03,812 Possible solutions: 2025-09-08T08:05:03,812 1. Declare 'make_c_nD' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,812 2. Use an 'int' return type on 'make_c_nD' to allow an error code to be returned. 2025-09-08T08:05:03,812 performance hint: wlsqm/fitter/simple.pyx:804:23: Exception check after calling 'make_A' will always require the GIL to be acquired. 2025-09-08T08:05:03,813 Possible solutions: 2025-09-08T08:05:03,813 1. Declare 'make_A' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,813 2. Use an 'int' return type on 'make_A' to allow an error code to be returned. 2025-09-08T08:05:03,813 performance hint: wlsqm/fitter/simple.pyx:805:29: Exception check after calling 'preprocess_A' will always require the GIL to be acquired. 2025-09-08T08:05:03,813 Possible solutions: 2025-09-08T08:05:03,813 1. Declare 'preprocess_A' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,813 2. Use an 'int' return type on 'preprocess_A' to allow an error code to be returned. 2025-09-08T08:05:03,813 performance hint: wlsqm/fitter/simple.pyx:806:29: Exception check after calling 'Case_set_fi' will always require the GIL to be acquired. 2025-09-08T08:05:03,813 Possible solutions: 2025-09-08T08:05:03,813 1. Declare 'Case_set_fi' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,814 2. Use an 'int' return type on 'Case_set_fi' to allow an error code to be returned. 2025-09-08T08:05:03,816 performance hint: wlsqm/fitter/simple.pyx:808:26: Exception check after calling 'solve' will always require the GIL to be acquired. 2025-09-08T08:05:03,816 Possible solutions: 2025-09-08T08:05:03,816 1. Declare 'solve' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,816 2. Use an 'int' return type on 'solve' to allow an error code to be returned. 2025-09-08T08:05:03,821 performance hint: wlsqm/fitter/simple.pyx:810:26: Exception check after calling 'solve' will always require the GIL to be acquired. 2025-09-08T08:05:03,821 Possible solutions: 2025-09-08T08:05:03,821 1. Declare 'solve' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,821 2. Use an 'int' return type on 'solve' to allow an error code to be returned. 2025-09-08T08:05:03,822 performance hint: wlsqm/fitter/simple.pyx:821:29: Exception check after calling 'Case_get_fi' will always require the GIL to be acquired. 2025-09-08T08:05:03,822 Possible solutions: 2025-09-08T08:05:03,822 1. Declare 'Case_get_fi' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,822 2. Use an 'int' return type on 'Case_get_fi' to allow an error code to be returned. 2025-09-08T08:05:03,822 performance hint: wlsqm/fitter/simple.pyx:823:25: Exception check after calling 'CaseManager_del' will always require the GIL to be acquired. 2025-09-08T08:05:03,822 Possible solutions: 2025-09-08T08:05:03,822 1. Declare 'CaseManager_del' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,823 2. Use an 'int' return type on 'CaseManager_del' to allow an error code to be returned. 2025-09-08T08:05:03,832 performance hint: wlsqm/fitter/simple.pyx:891:26: Exception check after calling 'make_c_nD' will always require the GIL to be acquired. 2025-09-08T08:05:03,832 Possible solutions: 2025-09-08T08:05:03,832 1. Declare 'make_c_nD' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,833 2. Use an 'int' return type on 'make_c_nD' to allow an error code to be returned. 2025-09-08T08:05:03,833 performance hint: wlsqm/fitter/simple.pyx:892:23: Exception check after calling 'make_A' will always require the GIL to be acquired. 2025-09-08T08:05:03,833 Possible solutions: 2025-09-08T08:05:03,833 1. Declare 'make_A' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,833 2. Use an 'int' return type on 'make_A' to allow an error code to be returned. 2025-09-08T08:05:03,833 performance hint: wlsqm/fitter/simple.pyx:893:29: Exception check after calling 'preprocess_A' will always require the GIL to be acquired. 2025-09-08T08:05:03,833 Possible solutions: 2025-09-08T08:05:03,833 1. Declare 'preprocess_A' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,833 2. Use an 'int' return type on 'preprocess_A' to allow an error code to be returned. 2025-09-08T08:05:03,833 performance hint: wlsqm/fitter/simple.pyx:894:29: Exception check after calling 'Case_set_fi' will always require the GIL to be acquired. 2025-09-08T08:05:03,834 Possible solutions: 2025-09-08T08:05:03,834 1. Declare 'Case_set_fi' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,834 2. Use an 'int' return type on 'Case_set_fi' to allow an error code to be returned. 2025-09-08T08:05:03,839 performance hint: wlsqm/fitter/simple.pyx:896:55: Exception check after calling 'solve_iterative' will always require the GIL to be acquired. 2025-09-08T08:05:03,839 Possible solutions: 2025-09-08T08:05:03,839 1. Declare 'solve_iterative' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,839 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:05:03,847 performance hint: wlsqm/fitter/simple.pyx:898:55: Exception check after calling 'solve_iterative' will always require the GIL to be acquired. 2025-09-08T08:05:03,847 Possible solutions: 2025-09-08T08:05:03,847 1. Declare 'solve_iterative' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,847 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:05:03,848 performance hint: wlsqm/fitter/simple.pyx:905:29: Exception check after calling 'Case_get_fi' will always require the GIL to be acquired. 2025-09-08T08:05:03,848 Possible solutions: 2025-09-08T08:05:03,848 1. Declare 'Case_get_fi' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,848 2. Use an 'int' return type on 'Case_get_fi' to allow an error code to be returned. 2025-09-08T08:05:03,853 performance hint: wlsqm/fitter/simple.pyx:921:26: Exception check after calling 'make_c_nD' will always require the GIL to be acquired. 2025-09-08T08:05:03,853 Possible solutions: 2025-09-08T08:05:03,853 1. Declare 'make_c_nD' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,853 2. Use an 'int' return type on 'make_c_nD' to allow an error code to be returned. 2025-09-08T08:05:03,853 performance hint: wlsqm/fitter/simple.pyx:922:23: Exception check after calling 'make_A' will always require the GIL to be acquired. 2025-09-08T08:05:03,854 Possible solutions: 2025-09-08T08:05:03,854 1. Declare 'make_A' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,854 2. Use an 'int' return type on 'make_A' to allow an error code to be returned. 2025-09-08T08:05:03,854 performance hint: wlsqm/fitter/simple.pyx:923:29: Exception check after calling 'preprocess_A' will always require the GIL to be acquired. 2025-09-08T08:05:03,854 Possible solutions: 2025-09-08T08:05:03,854 1. Declare 'preprocess_A' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,854 2. Use an 'int' return type on 'preprocess_A' to allow an error code to be returned. 2025-09-08T08:05:03,854 performance hint: wlsqm/fitter/simple.pyx:924:29: Exception check after calling 'Case_set_fi' will always require the GIL to be acquired. 2025-09-08T08:05:03,854 Possible solutions: 2025-09-08T08:05:03,854 1. Declare 'Case_set_fi' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,854 2. Use an 'int' return type on 'Case_set_fi' to allow an error code to be returned. 2025-09-08T08:05:03,859 performance hint: wlsqm/fitter/simple.pyx:926:55: Exception check after calling 'solve_iterative' will always require the GIL to be acquired. 2025-09-08T08:05:03,859 Possible solutions: 2025-09-08T08:05:03,859 1. Declare 'solve_iterative' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,859 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:05:03,866 performance hint: wlsqm/fitter/simple.pyx:928:55: Exception check after calling 'solve_iterative' will always require the GIL to be acquired. 2025-09-08T08:05:03,867 Possible solutions: 2025-09-08T08:05:03,867 1. Declare 'solve_iterative' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,867 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:05:03,868 performance hint: wlsqm/fitter/simple.pyx:935:29: Exception check after calling 'Case_get_fi' will always require the GIL to be acquired. 2025-09-08T08:05:03,868 Possible solutions: 2025-09-08T08:05:03,868 1. Declare 'Case_get_fi' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,868 2. Use an 'int' return type on 'Case_get_fi' to allow an error code to be returned. 2025-09-08T08:05:03,868 performance hint: wlsqm/fitter/simple.pyx:937:25: Exception check after calling 'CaseManager_del' will always require the GIL to be acquired. 2025-09-08T08:05:03,868 Possible solutions: 2025-09-08T08:05:03,868 1. Declare 'CaseManager_del' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,868 2. Use an 'int' return type on 'CaseManager_del' to allow an error code to be returned. 2025-09-08T08:05:03,878 performance hint: wlsqm/fitter/simple.pyx:999:26: Exception check after calling 'make_c_nD' will always require the GIL to be acquired. 2025-09-08T08:05:03,878 Possible solutions: 2025-09-08T08:05:03,878 1. Declare 'make_c_nD' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,878 2. Use an 'int' return type on 'make_c_nD' to allow an error code to be returned. 2025-09-08T08:05:03,879 performance hint: wlsqm/fitter/simple.pyx:1000:23: Exception check after calling 'make_A' will always require the GIL to be acquired. 2025-09-08T08:05:03,879 Possible solutions: 2025-09-08T08:05:03,879 1. Declare 'make_A' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,879 2. Use an 'int' return type on 'make_A' to allow an error code to be returned. 2025-09-08T08:05:03,879 performance hint: wlsqm/fitter/simple.pyx:1001:29: Exception check after calling 'preprocess_A' will always require the GIL to be acquired. 2025-09-08T08:05:03,879 Possible solutions: 2025-09-08T08:05:03,879 1. Declare 'preprocess_A' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,879 2. Use an 'int' return type on 'preprocess_A' to allow an error code to be returned. 2025-09-08T08:05:03,879 performance hint: wlsqm/fitter/simple.pyx:1002:29: Exception check after calling 'Case_set_fi' will always require the GIL to be acquired. 2025-09-08T08:05:03,879 Possible solutions: 2025-09-08T08:05:03,880 1. Declare 'Case_set_fi' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,880 2. Use an 'int' return type on 'Case_set_fi' to allow an error code to be returned. 2025-09-08T08:05:03,882 performance hint: wlsqm/fitter/simple.pyx:1004:26: Exception check after calling 'solve' will always require the GIL to be acquired. 2025-09-08T08:05:03,882 Possible solutions: 2025-09-08T08:05:03,882 1. Declare 'solve' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,882 2. Use an 'int' return type on 'solve' to allow an error code to be returned. 2025-09-08T08:05:03,887 performance hint: wlsqm/fitter/simple.pyx:1006:26: Exception check after calling 'solve' will always require the GIL to be acquired. 2025-09-08T08:05:03,887 Possible solutions: 2025-09-08T08:05:03,887 1. Declare 'solve' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,887 2. Use an 'int' return type on 'solve' to allow an error code to be returned. 2025-09-08T08:05:03,889 performance hint: wlsqm/fitter/simple.pyx:1017:29: Exception check after calling 'Case_get_fi' will always require the GIL to be acquired. 2025-09-08T08:05:03,890 Possible solutions: 2025-09-08T08:05:03,890 1. Declare 'Case_get_fi' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,890 2. Use an 'int' return type on 'Case_get_fi' to allow an error code to be returned. 2025-09-08T08:05:03,896 performance hint: wlsqm/fitter/simple.pyx:1034:26: Exception check after calling 'make_c_nD' will always require the GIL to be acquired. 2025-09-08T08:05:03,896 Possible solutions: 2025-09-08T08:05:03,896 1. Declare 'make_c_nD' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,896 2. Use an 'int' return type on 'make_c_nD' to allow an error code to be returned. 2025-09-08T08:05:03,896 performance hint: wlsqm/fitter/simple.pyx:1035:23: Exception check after calling 'make_A' will always require the GIL to be acquired. 2025-09-08T08:05:03,897 Possible solutions: 2025-09-08T08:05:03,897 1. Declare 'make_A' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,897 2. Use an 'int' return type on 'make_A' to allow an error code to be returned. 2025-09-08T08:05:03,897 performance hint: wlsqm/fitter/simple.pyx:1036:29: Exception check after calling 'preprocess_A' will always require the GIL to be acquired. 2025-09-08T08:05:03,897 Possible solutions: 2025-09-08T08:05:03,897 1. Declare 'preprocess_A' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,897 2. Use an 'int' return type on 'preprocess_A' to allow an error code to be returned. 2025-09-08T08:05:03,897 performance hint: wlsqm/fitter/simple.pyx:1037:29: Exception check after calling 'Case_set_fi' will always require the GIL to be acquired. 2025-09-08T08:05:03,897 Possible solutions: 2025-09-08T08:05:03,897 1. Declare 'Case_set_fi' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,898 2. Use an 'int' return type on 'Case_set_fi' to allow an error code to be returned. 2025-09-08T08:05:03,900 performance hint: wlsqm/fitter/simple.pyx:1039:26: Exception check after calling 'solve' will always require the GIL to be acquired. 2025-09-08T08:05:03,900 Possible solutions: 2025-09-08T08:05:03,900 1. Declare 'solve' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,900 2. Use an 'int' return type on 'solve' to allow an error code to be returned. 2025-09-08T08:05:03,905 performance hint: wlsqm/fitter/simple.pyx:1041:26: Exception check after calling 'solve' will always require the GIL to be acquired. 2025-09-08T08:05:03,905 Possible solutions: 2025-09-08T08:05:03,905 1. Declare 'solve' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,905 2. Use an 'int' return type on 'solve' to allow an error code to be returned. 2025-09-08T08:05:03,907 performance hint: wlsqm/fitter/simple.pyx:1052:29: Exception check after calling 'Case_get_fi' will always require the GIL to be acquired. 2025-09-08T08:05:03,907 Possible solutions: 2025-09-08T08:05:03,908 1. Declare 'Case_get_fi' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,908 2. Use an 'int' return type on 'Case_get_fi' to allow an error code to be returned. 2025-09-08T08:05:03,909 performance hint: wlsqm/fitter/simple.pyx:1054:25: Exception check after calling 'CaseManager_del' will always require the GIL to be acquired. 2025-09-08T08:05:03,909 Possible solutions: 2025-09-08T08:05:03,909 1. Declare 'CaseManager_del' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,909 2. Use an 'int' return type on 'CaseManager_del' to allow an error code to be returned. 2025-09-08T08:05:03,920 performance hint: wlsqm/fitter/simple.pyx:1113:26: Exception check after calling 'make_c_nD' will always require the GIL to be acquired. 2025-09-08T08:05:03,920 Possible solutions: 2025-09-08T08:05:03,920 1. Declare 'make_c_nD' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,920 2. Use an 'int' return type on 'make_c_nD' to allow an error code to be returned. 2025-09-08T08:05:03,920 performance hint: wlsqm/fitter/simple.pyx:1114:23: Exception check after calling 'make_A' will always require the GIL to be acquired. 2025-09-08T08:05:03,920 Possible solutions: 2025-09-08T08:05:03,921 1. Declare 'make_A' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,921 2. Use an 'int' return type on 'make_A' to allow an error code to be returned. 2025-09-08T08:05:03,921 performance hint: wlsqm/fitter/simple.pyx:1115:29: Exception check after calling 'preprocess_A' will always require the GIL to be acquired. 2025-09-08T08:05:03,921 Possible solutions: 2025-09-08T08:05:03,921 1. Declare 'preprocess_A' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,921 2. Use an 'int' return type on 'preprocess_A' to allow an error code to be returned. 2025-09-08T08:05:03,921 performance hint: wlsqm/fitter/simple.pyx:1116:29: Exception check after calling 'Case_set_fi' will always require the GIL to be acquired. 2025-09-08T08:05:03,921 Possible solutions: 2025-09-08T08:05:03,921 1. Declare 'Case_set_fi' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,921 2. Use an 'int' return type on 'Case_set_fi' to allow an error code to be returned. 2025-09-08T08:05:03,926 performance hint: wlsqm/fitter/simple.pyx:1118:55: Exception check after calling 'solve_iterative' will always require the GIL to be acquired. 2025-09-08T08:05:03,927 Possible solutions: 2025-09-08T08:05:03,927 1. Declare 'solve_iterative' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,927 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:05:03,935 performance hint: wlsqm/fitter/simple.pyx:1120:55: Exception check after calling 'solve_iterative' will always require the GIL to be acquired. 2025-09-08T08:05:03,935 Possible solutions: 2025-09-08T08:05:03,935 1. Declare 'solve_iterative' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,935 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:05:03,937 performance hint: wlsqm/fitter/simple.pyx:1127:29: Exception check after calling 'Case_get_fi' will always require the GIL to be acquired. 2025-09-08T08:05:03,937 Possible solutions: 2025-09-08T08:05:03,938 1. Declare 'Case_get_fi' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,938 2. Use an 'int' return type on 'Case_get_fi' to allow an error code to be returned. 2025-09-08T08:05:03,944 performance hint: wlsqm/fitter/simple.pyx:1144:26: Exception check after calling 'make_c_nD' will always require the GIL to be acquired. 2025-09-08T08:05:03,944 Possible solutions: 2025-09-08T08:05:03,944 1. Declare 'make_c_nD' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,944 2. Use an 'int' return type on 'make_c_nD' to allow an error code to be returned. 2025-09-08T08:05:03,944 performance hint: wlsqm/fitter/simple.pyx:1145:23: Exception check after calling 'make_A' will always require the GIL to be acquired. 2025-09-08T08:05:03,944 Possible solutions: 2025-09-08T08:05:03,944 1. Declare 'make_A' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,945 2. Use an 'int' return type on 'make_A' to allow an error code to be returned. 2025-09-08T08:05:03,945 performance hint: wlsqm/fitter/simple.pyx:1146:29: Exception check after calling 'preprocess_A' will always require the GIL to be acquired. 2025-09-08T08:05:03,945 Possible solutions: 2025-09-08T08:05:03,945 1. Declare 'preprocess_A' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,945 2. Use an 'int' return type on 'preprocess_A' to allow an error code to be returned. 2025-09-08T08:05:03,945 performance hint: wlsqm/fitter/simple.pyx:1147:29: Exception check after calling 'Case_set_fi' will always require the GIL to be acquired. 2025-09-08T08:05:03,945 Possible solutions: 2025-09-08T08:05:03,945 1. Declare 'Case_set_fi' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,945 2. Use an 'int' return type on 'Case_set_fi' to allow an error code to be returned. 2025-09-08T08:05:03,950 performance hint: wlsqm/fitter/simple.pyx:1149:55: Exception check after calling 'solve_iterative' will always require the GIL to be acquired. 2025-09-08T08:05:03,950 Possible solutions: 2025-09-08T08:05:03,950 1. Declare 'solve_iterative' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,950 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:05:03,957 performance hint: wlsqm/fitter/simple.pyx:1151:55: Exception check after calling 'solve_iterative' will always require the GIL to be acquired. 2025-09-08T08:05:03,957 Possible solutions: 2025-09-08T08:05:03,957 1. Declare 'solve_iterative' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,958 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:05:03,960 performance hint: wlsqm/fitter/simple.pyx:1158:29: Exception check after calling 'Case_get_fi' will always require the GIL to be acquired. 2025-09-08T08:05:03,960 Possible solutions: 2025-09-08T08:05:03,960 1. Declare 'Case_get_fi' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,960 2. Use an 'int' return type on 'Case_get_fi' to allow an error code to be returned. 2025-09-08T08:05:03,961 performance hint: wlsqm/fitter/simple.pyx:1160:25: Exception check after calling 'CaseManager_del' will always require the GIL to be acquired. 2025-09-08T08:05:03,961 Possible solutions: 2025-09-08T08:05:03,962 1. Declare 'CaseManager_del' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:03,962 2. Use an 'int' return type on 'CaseManager_del' to allow an error code to be returned. 2025-09-08T08:05:04,313 warning: wlsqm/utils/lapackdrivers.pxd:82:95: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,313 warning: wlsqm/utils/lapackdrivers.pxd:88:63: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,314 warning: wlsqm/utils/lapackdrivers.pxd:90:67: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,314 warning: wlsqm/utils/lapackdrivers.pxd:91:73: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,315 warning: wlsqm/utils/lapackdrivers.pxd:92:86: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,315 warning: wlsqm/utils/lapackdrivers.pxd:94:78: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,316 warning: wlsqm/utils/lapackdrivers.pxd:95:91: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,316 warning: wlsqm/utils/lapackdrivers.pxd:97:78: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,316 warning: wlsqm/utils/lapackdrivers.pxd:98:91: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,317 warning: wlsqm/utils/lapackdrivers.pxd:100:84: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,317 warning: wlsqm/utils/lapackdrivers.pxd:101:97: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,318 warning: wlsqm/utils/lapackdrivers.pxd:102:97: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,318 warning: wlsqm/utils/lapackdrivers.pxd:103:110: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,319 warning: wlsqm/utils/lapackdrivers.pxd:109:61: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,319 warning: wlsqm/utils/lapackdrivers.pxd:111:65: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,320 warning: wlsqm/utils/lapackdrivers.pxd:112:71: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,320 warning: wlsqm/utils/lapackdrivers.pxd:113:84: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,320 warning: wlsqm/utils/lapackdrivers.pxd:115:76: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,321 warning: wlsqm/utils/lapackdrivers.pxd:116:89: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,321 warning: wlsqm/utils/lapackdrivers.pxd:118:76: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,322 warning: wlsqm/utils/lapackdrivers.pxd:119:89: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,323 warning: wlsqm/utils/lapackdrivers.pxd:121:82: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,323 warning: wlsqm/utils/lapackdrivers.pxd:122:95: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,324 warning: wlsqm/utils/lapackdrivers.pxd:123:95: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,324 warning: wlsqm/utils/lapackdrivers.pxd:124:108: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,325 warning: wlsqm/utils/lapackdrivers.pxd:130:68: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,819 warning: wlsqm/utils/lapackdrivers.pyx:824:95: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,837 warning: wlsqm/utils/lapackdrivers.pyx:870:63: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,840 warning: wlsqm/utils/lapackdrivers.pyx:909:67: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,842 warning: wlsqm/utils/lapackdrivers.pyx:931:73: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,845 warning: wlsqm/utils/lapackdrivers.pyx:963:86: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,847 warning: wlsqm/utils/lapackdrivers.pyx:986:78: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,852 warning: wlsqm/utils/lapackdrivers.pyx:1031:91: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,859 warning: wlsqm/utils/lapackdrivers.pyx:1095:78: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,864 warning: wlsqm/utils/lapackdrivers.pyx:1142:91: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,869 warning: wlsqm/utils/lapackdrivers.pyx:1185:84: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,874 warning: wlsqm/utils/lapackdrivers.pyx:1233:97: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,877 warning: wlsqm/utils/lapackdrivers.pyx:1262:97: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,883 warning: wlsqm/utils/lapackdrivers.pyx:1315:110: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,886 warning: wlsqm/utils/lapackdrivers.pyx:1345:61: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,889 warning: wlsqm/utils/lapackdrivers.pyx:1381:65: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,891 warning: wlsqm/utils/lapackdrivers.pyx:1403:71: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,894 warning: wlsqm/utils/lapackdrivers.pyx:1431:84: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,896 warning: wlsqm/utils/lapackdrivers.pyx:1454:76: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,899 warning: wlsqm/utils/lapackdrivers.pyx:1490:89: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,904 warning: wlsqm/utils/lapackdrivers.pyx:1539:76: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,908 warning: wlsqm/utils/lapackdrivers.pyx:1570:89: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,912 warning: wlsqm/utils/lapackdrivers.pyx:1598:82: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,915 warning: wlsqm/utils/lapackdrivers.pyx:1627:95: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,918 warning: wlsqm/utils/lapackdrivers.pyx:1655:95: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,922 warning: wlsqm/utils/lapackdrivers.pyx:1685:108: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:04,926 warning: wlsqm/utils/lapackdrivers.pyx:1726:68: The keyword 'nogil' should appear at the end of the function signature line. Placing it before 'except' or 'noexcept' will be disallowed in a future version of Cython. 2025-09-08T08:05:08,392 performance hint: wlsqm/utils/lapackdrivers.pyx:110:0: Exception check on 'distribute_items_c' will always require the GIL to be acquired. 2025-09-08T08:05:08,392 Possible solutions: 2025-09-08T08:05:08,392 1. Declare 'distribute_items_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:08,392 2. Use an 'int' return type on 'distribute_items_c' to allow an error code to be returned. 2025-09-08T08:05:08,393 performance hint: wlsqm/utils/lapackdrivers.pyx:142:0: Exception check on 'copygeneral_c' will always require the GIL to be acquired. 2025-09-08T08:05:08,393 Possible solutions: 2025-09-08T08:05:08,393 1. Declare 'copygeneral_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:08,393 2. Use an 'int' return type on 'copygeneral_c' to allow an error code to be returned. 2025-09-08T08:05:08,394 performance hint: wlsqm/utils/lapackdrivers.pyx:162:0: Exception check on 'copysymmu_c' will always require the GIL to be acquired. 2025-09-08T08:05:08,394 Possible solutions: 2025-09-08T08:05:08,394 1. Declare 'copysymmu_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:08,394 2. Use an 'int' return type on 'copysymmu_c' to allow an error code to be returned. 2025-09-08T08:05:08,394 performance hint: wlsqm/utils/lapackdrivers.pyx:184:0: Exception check on 'symmetrize_c' will always require the GIL to be acquired. 2025-09-08T08:05:08,394 Possible solutions: 2025-09-08T08:05:08,394 1. Declare 'symmetrize_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:08,395 2. Use an 'int' return type on 'symmetrize_c' to allow an error code to be returned. 2025-09-08T08:05:08,395 performance hint: wlsqm/utils/lapackdrivers.pyx:211:0: Exception check on 'msymmetrize_c' will always require the GIL to be acquired. 2025-09-08T08:05:08,395 Possible solutions: 2025-09-08T08:05:08,395 1. Declare 'msymmetrize_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:08,395 2. Use an 'int' return type on 'msymmetrize_c' to allow an error code to be returned. 2025-09-08T08:05:08,396 performance hint: wlsqm/utils/lapackdrivers.pyx:237:0: Exception check on 'msymmetrizep_c' will always require the GIL to be acquired. 2025-09-08T08:05:08,396 Possible solutions: 2025-09-08T08:05:08,396 1. Declare 'msymmetrizep_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:08,396 2. Use an 'int' return type on 'msymmetrizep_c' to allow an error code to be returned. 2025-09-08T08:05:08,396 performance hint: wlsqm/utils/lapackdrivers.pyx:277:0: Exception check on 'init_scaling_c' will always require the GIL to be acquired. 2025-09-08T08:05:08,396 Possible solutions: 2025-09-08T08:05:08,396 1. Declare 'init_scaling_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:08,396 2. Use an 'int' return type on 'init_scaling_c' to allow an error code to be returned. 2025-09-08T08:05:08,396 performance hint: wlsqm/utils/lapackdrivers.pyx:285:0: Exception check on 'apply_scaling_c' will always require the GIL to be acquired. 2025-09-08T08:05:08,397 Possible solutions: 2025-09-08T08:05:08,397 1. Declare 'apply_scaling_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:08,397 2. Use an 'int' return type on 'apply_scaling_c' to allow an error code to be returned. 2025-09-08T08:05:08,398 performance hint: wlsqm/utils/lapackdrivers.pxd:69:26: No exception value declared for 'rescale_columns_c' in pxd file. 2025-09-08T08:05:08,398 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:05:08,399 Suggest adding an explicit exception value. 2025-09-08T08:05:08,399 performance hint: wlsqm/utils/lapackdrivers.pxd:70:23: No exception value declared for 'rescale_rows_c' in pxd file. 2025-09-08T08:05:08,399 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:05:08,399 Suggest adding an explicit exception value. 2025-09-08T08:05:08,400 performance hint: wlsqm/utils/lapackdrivers.pxd:71:26: No exception value declared for 'rescale_twopass_c' in pxd file. 2025-09-08T08:05:08,400 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:05:08,400 Suggest adding an explicit exception value. 2025-09-08T08:05:08,401 performance hint: wlsqm/utils/lapackdrivers.pxd:72:25: No exception value declared for 'rescale_dgeequ_c' in pxd file. 2025-09-08T08:05:08,401 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:05:08,401 Suggest adding an explicit exception value. 2025-09-08T08:05:08,402 performance hint: wlsqm/utils/lapackdrivers.pxd:75:27: No exception value declared for 'rescale_ruiz2001_c' in pxd file. 2025-09-08T08:05:08,402 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:05:08,402 Suggest adding an explicit exception value. 2025-09-08T08:05:08,402 performance hint: wlsqm/utils/lapackdrivers.pyx:615:0: Exception check on 'basic_scale_up_rows' will always require the GIL to be acquired. 2025-09-08T08:05:08,403 Possible solutions: 2025-09-08T08:05:08,403 1. Declare 'basic_scale_up_rows' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:08,403 2. Use an 'int' return type on 'basic_scale_up_rows' to allow an error code to be returned. 2025-09-08T08:05:08,403 performance hint: wlsqm/utils/lapackdrivers.pyx:640:0: Exception check on 'basic_scale_up_cols' will always require the GIL to be acquired. 2025-09-08T08:05:08,403 Possible solutions: 2025-09-08T08:05:08,403 1. Declare 'basic_scale_up_cols' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:08,403 2. Use an 'int' return type on 'basic_scale_up_cols' to allow an error code to be returned. 2025-09-08T08:05:08,404 performance hint: wlsqm/utils/lapackdrivers.pyx:665:0: Exception check on 'basic_scale_down_rows' will always require the GIL to be acquired. 2025-09-08T08:05:08,404 Possible solutions: 2025-09-08T08:05:08,404 1. Declare 'basic_scale_down_rows' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:08,404 2. Use an 'int' return type on 'basic_scale_down_rows' to allow an error code to be returned. 2025-09-08T08:05:08,404 performance hint: wlsqm/utils/lapackdrivers.pyx:690:0: Exception check on 'basic_scale_down_cols' will always require the GIL to be acquired. 2025-09-08T08:05:08,404 Possible solutions: 2025-09-08T08:05:08,404 1. Declare 'basic_scale_down_cols' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:08,404 2. Use an 'int' return type on 'basic_scale_down_cols' to allow an error code to be returned. 2025-09-08T08:05:08,404 performance hint: wlsqm/utils/lapackdrivers.pxd:76:25: No exception value declared for 'rescale_scalgm_c' in pxd file. 2025-09-08T08:05:08,405 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:05:08,405 Suggest adding an explicit exception value. 2025-09-08T08:05:09,990 performance hint: wlsqm/utils/lapackdrivers.pyx:140:21: Exception check after calling 'copygeneral_c' will always require the GIL to be acquired. 2025-09-08T08:05:09,991 Possible solutions: 2025-09-08T08:05:09,991 1. Declare 'copygeneral_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:09,991 2. Use an 'int' return type on 'copygeneral_c' to allow an error code to be returned. 2025-09-08T08:05:09,994 performance hint: wlsqm/utils/lapackdrivers.pyx:160:19: Exception check after calling 'copysymmu_c' will always require the GIL to be acquired. 2025-09-08T08:05:09,995 Possible solutions: 2025-09-08T08:05:09,995 1. Declare 'copysymmu_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:09,995 2. Use an 'int' return type on 'copysymmu_c' to allow an error code to be returned. 2025-09-08T08:05:09,999 performance hint: wlsqm/utils/lapackdrivers.pyx:182:20: Exception check after calling 'symmetrize_c' will always require the GIL to be acquired. 2025-09-08T08:05:09,999 Possible solutions: 2025-09-08T08:05:09,999 1. Declare 'symmetrize_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:09,999 2. Use an 'int' return type on 'symmetrize_c' to allow an error code to be returned. 2025-09-08T08:05:10,003 performance hint: wlsqm/utils/lapackdrivers.pyx:209:21: Exception check after calling 'msymmetrize_c' will always require the GIL to be acquired. 2025-09-08T08:05:10,003 Possible solutions: 2025-09-08T08:05:10,003 1. Declare 'msymmetrize_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:10,003 2. Use an 'int' return type on 'msymmetrize_c' to allow an error code to be returned. 2025-09-08T08:05:10,008 performance hint: wlsqm/utils/lapackdrivers.pyx:235:22: Exception check after calling 'msymmetrizep_c' will always require the GIL to be acquired. 2025-09-08T08:05:10,008 Possible solutions: 2025-09-08T08:05:10,008 1. Declare 'msymmetrizep_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:10,008 2. Use an 'int' return type on 'msymmetrizep_c' to allow an error code to be returned. 2025-09-08T08:05:10,023 performance hint: wlsqm/utils/lapackdrivers.pyx:360:14: Exception check after calling 'scaler' will always require the GIL to be acquired. Declare 'scaler' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:10,024 performance hint: wlsqm/utils/lapackdrivers.pyx:361:23: Exception check after calling 'apply_scaling_c' will always require the GIL to be acquired. 2025-09-08T08:05:10,024 Possible solutions: 2025-09-08T08:05:10,024 1. Declare 'apply_scaling_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:10,024 2. Use an 'int' return type on 'apply_scaling_c' to allow an error code to be returned. 2025-09-08T08:05:10,028 performance hint: wlsqm/utils/lapackdrivers.pyx:390:18: Exception check after calling 'init_scaling_c' will always require the GIL to be acquired. 2025-09-08T08:05:10,028 Possible solutions: 2025-09-08T08:05:10,028 1. Declare 'init_scaling_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:10,028 2. Use an 'int' return type on 'init_scaling_c' to allow an error code to be returned. 2025-09-08T08:05:10,032 performance hint: wlsqm/utils/lapackdrivers.pyx:422:18: Exception check after calling 'init_scaling_c' will always require the GIL to be acquired. 2025-09-08T08:05:10,032 Possible solutions: 2025-09-08T08:05:10,033 1. Declare 'init_scaling_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:10,033 2. Use an 'int' return type on 'init_scaling_c' to allow an error code to be returned. 2025-09-08T08:05:10,037 performance hint: wlsqm/utils/lapackdrivers.pyx:458:18: Exception check after calling 'init_scaling_c' will always require the GIL to be acquired. 2025-09-08T08:05:10,037 Possible solutions: 2025-09-08T08:05:10,037 1. Declare 'init_scaling_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:10,037 2. Use an 'int' return type on 'init_scaling_c' to allow an error code to be returned. 2025-09-08T08:05:10,046 performance hint: wlsqm/utils/lapackdrivers.pyx:530:18: Exception check after calling 'init_scaling_c' will always require the GIL to be acquired. 2025-09-08T08:05:10,046 Possible solutions: 2025-09-08T08:05:10,046 1. Declare 'init_scaling_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:10,046 2. Use an 'int' return type on 'init_scaling_c' to allow an error code to be returned. 2025-09-08T08:05:10,047 performance hint: wlsqm/utils/lapackdrivers.pyx:531:18: Exception check after calling 'init_scaling_c' will always require the GIL to be acquired. 2025-09-08T08:05:10,047 Possible solutions: 2025-09-08T08:05:10,047 1. Declare 'init_scaling_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:10,047 2. Use an 'int' return type on 'init_scaling_c' to allow an error code to be returned. 2025-09-08T08:05:10,047 performance hint: wlsqm/utils/lapackdrivers.pyx:532:18: Exception check after calling 'init_scaling_c' will always require the GIL to be acquired. 2025-09-08T08:05:10,047 Possible solutions: 2025-09-08T08:05:10,047 1. Declare 'init_scaling_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:10,047 2. Use an 'int' return type on 'init_scaling_c' to allow an error code to be returned. 2025-09-08T08:05:10,071 performance hint: wlsqm/utils/lapackdrivers.pyx:722:18: Exception check after calling 'init_scaling_c' will always require the GIL to be acquired. 2025-09-08T08:05:10,071 Possible solutions: 2025-09-08T08:05:10,071 1. Declare 'init_scaling_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:10,071 2. Use an 'int' return type on 'init_scaling_c' to allow an error code to be returned. 2025-09-08T08:05:10,071 performance hint: wlsqm/utils/lapackdrivers.pyx:723:18: Exception check after calling 'init_scaling_c' will always require the GIL to be acquired. 2025-09-08T08:05:10,072 Possible solutions: 2025-09-08T08:05:10,072 1. Declare 'init_scaling_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:10,072 2. Use an 'int' return type on 'init_scaling_c' to allow an error code to be returned. 2025-09-08T08:05:10,072 performance hint: wlsqm/utils/lapackdrivers.pyx:724:18: Exception check after calling 'init_scaling_c' will always require the GIL to be acquired. 2025-09-08T08:05:10,072 Possible solutions: 2025-09-08T08:05:10,072 1. Declare 'init_scaling_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:10,072 2. Use an 'int' return type on 'init_scaling_c' to allow an error code to be returned. 2025-09-08T08:05:10,072 performance hint: wlsqm/utils/lapackdrivers.pyx:737:31: Exception check after calling 'basic_scale_up_rows' will always require the GIL to be acquired. 2025-09-08T08:05:10,072 Possible solutions: 2025-09-08T08:05:10,072 1. Declare 'basic_scale_up_rows' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:10,073 2. Use an 'int' return type on 'basic_scale_up_rows' to allow an error code to be returned. 2025-09-08T08:05:10,073 performance hint: wlsqm/utils/lapackdrivers.pyx:738:31: Exception check after calling 'basic_scale_up_cols' will always require the GIL to be acquired. 2025-09-08T08:05:10,073 Possible solutions: 2025-09-08T08:05:10,073 1. Declare 'basic_scale_up_cols' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:10,073 2. Use an 'int' return type on 'basic_scale_up_cols' to allow an error code to be returned. 2025-09-08T08:05:10,073 performance hint: wlsqm/utils/lapackdrivers.pyx:742:31: Exception check after calling 'basic_scale_up_cols' will always require the GIL to be acquired. 2025-09-08T08:05:10,073 Possible solutions: 2025-09-08T08:05:10,073 1. Declare 'basic_scale_up_cols' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:10,073 2. Use an 'int' return type on 'basic_scale_up_cols' to allow an error code to be returned. 2025-09-08T08:05:10,073 performance hint: wlsqm/utils/lapackdrivers.pyx:743:31: Exception check after calling 'basic_scale_up_rows' will always require the GIL to be acquired. 2025-09-08T08:05:10,074 Possible solutions: 2025-09-08T08:05:10,074 1. Declare 'basic_scale_up_rows' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:10,074 2. Use an 'int' return type on 'basic_scale_up_rows' to allow an error code to be returned. 2025-09-08T08:05:10,075 performance hint: wlsqm/utils/lapackdrivers.pyx:758:29: Exception check after calling 'basic_scale_down_rows' will always require the GIL to be acquired. 2025-09-08T08:05:10,075 Possible solutions: 2025-09-08T08:05:10,075 1. Declare 'basic_scale_down_rows' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:10,075 2. Use an 'int' return type on 'basic_scale_down_rows' to allow an error code to be returned. 2025-09-08T08:05:10,075 performance hint: wlsqm/utils/lapackdrivers.pyx:759:29: Exception check after calling 'basic_scale_down_cols' will always require the GIL to be acquired. 2025-09-08T08:05:10,075 Possible solutions: 2025-09-08T08:05:10,075 1. Declare 'basic_scale_down_cols' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:10,075 2. Use an 'int' return type on 'basic_scale_down_cols' to allow an error code to be returned. 2025-09-08T08:05:10,075 performance hint: wlsqm/utils/lapackdrivers.pyx:763:29: Exception check after calling 'basic_scale_down_cols' will always require the GIL to be acquired. 2025-09-08T08:05:10,076 Possible solutions: 2025-09-08T08:05:10,076 1. Declare 'basic_scale_down_cols' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:10,076 2. Use an 'int' return type on 'basic_scale_down_cols' to allow an error code to be returned. 2025-09-08T08:05:10,076 performance hint: wlsqm/utils/lapackdrivers.pyx:764:29: Exception check after calling 'basic_scale_down_rows' will always require the GIL to be acquired. 2025-09-08T08:05:10,076 Possible solutions: 2025-09-08T08:05:10,076 1. Declare 'basic_scale_down_rows' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:10,076 2. Use an 'int' return type on 'basic_scale_down_rows' to allow an error code to be returned. 2025-09-08T08:05:10,110 performance hint: wlsqm/utils/lapackdrivers.pyx:1039:22: Exception check after calling 'distribute_items_c' will always require the GIL to be acquired. 2025-09-08T08:05:10,110 Possible solutions: 2025-09-08T08:05:10,110 1. Declare 'distribute_items_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:10,111 2. Use an 'int' return type on 'distribute_items_c' to allow an error code to be returned. 2025-09-08T08:05:10,112 performance hint: wlsqm/utils/lapackdrivers.pyx:1060:19: Exception check after calling 'copysymmu_c' will always require the GIL to be acquired. 2025-09-08T08:05:10,112 Possible solutions: 2025-09-08T08:05:10,112 1. Declare 'copysymmu_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:10,112 2. Use an 'int' return type on 'copysymmu_c' to allow an error code to be returned. 2025-09-08T08:05:10,174 performance hint: wlsqm/utils/lapackdrivers.pyx:1497:22: Exception check after calling 'distribute_items_c' will always require the GIL to be acquired. 2025-09-08T08:05:10,174 Possible solutions: 2025-09-08T08:05:10,174 1. Declare 'distribute_items_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:10,174 2. Use an 'int' return type on 'distribute_items_c' to allow an error code to be returned. 2025-09-08T08:05:10,175 performance hint: wlsqm/utils/lapackdrivers.pyx:1506:21: Exception check after calling 'copygeneral_c' will always require the GIL to be acquired. 2025-09-08T08:05:10,175 Possible solutions: 2025-09-08T08:05:10,175 1. Declare 'copygeneral_c' as 'noexcept' if you control the definition and you're sure you don't want the function to raise exceptions. 2025-09-08T08:05:10,175 2. Use an 'int' return type on 'copygeneral_c' to allow an error code to be returned. 2025-09-08T08:05:10,828 build configuration selected: optimized 2025-09-08T08:05:10,828 Compiling wlsqm/utils/lapackdrivers.pyx because it changed. 2025-09-08T08:05:10,828 Compiling wlsqm/utils/ptrwrap.pyx because it changed. 2025-09-08T08:05:10,828 Compiling wlsqm/fitter/defs.pyx because it changed. 2025-09-08T08:05:10,828 Compiling wlsqm/fitter/infra.pyx because it changed. 2025-09-08T08:05:10,828 Compiling wlsqm/fitter/impl.pyx because it changed. 2025-09-08T08:05:10,828 Compiling wlsqm/fitter/polyeval.pyx because it changed. 2025-09-08T08:05:10,828 Compiling wlsqm/fitter/interp.pyx because it changed. 2025-09-08T08:05:10,829 Compiling wlsqm/fitter/simple.pyx because it changed. 2025-09-08T08:05:10,829 Compiling wlsqm/fitter/expert.pyx because it changed. 2025-09-08T08:05:10,829 [1/9] Cythonizing wlsqm/fitter/defs.pyx 2025-09-08T08:05:10,829 [2/9] Cythonizing wlsqm/fitter/expert.pyx 2025-09-08T08:05:10,829 [3/9] Cythonizing wlsqm/fitter/impl.pyx 2025-09-08T08:05:10,829 [4/9] Cythonizing wlsqm/fitter/infra.pyx 2025-09-08T08:05:10,829 [5/9] Cythonizing wlsqm/fitter/interp.pyx 2025-09-08T08:05:10,829 [6/9] Cythonizing wlsqm/fitter/polyeval.pyx 2025-09-08T08:05:10,829 [7/9] Cythonizing wlsqm/fitter/simple.pyx 2025-09-08T08:05:10,829 [8/9] Cythonizing wlsqm/utils/lapackdrivers.pyx 2025-09-08T08:05:10,830 [9/9] Cythonizing wlsqm/utils/ptrwrap.pyx 2025-09-08T08:05:10,947 /usr/local/lib/python3.13/dist-packages/setuptools/__init__.py:92: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated. 2025-09-08T08:05:10,947 !! 2025-09-08T08:05:10,948 ******************************************************************************** 2025-09-08T08:05:10,948 Requirements should be satisfied by a PEP 517 installer. 2025-09-08T08:05:10,948 If you are using pip, you can try `pip install --use-pep517`. 2025-09-08T08:05:10,948 By 2025-Oct-31, you need to update your project and remove deprecated calls 2025-09-08T08:05:10,948 or your builds will no longer be supported. 2025-09-08T08:05:10,948 ******************************************************************************** 2025-09-08T08:05:10,948 !! 2025-09-08T08:05:10,948 dist.fetch_build_eggs(dist.setup_requires) 2025-09-08T08:05:11,388 /usr/local/lib/python3.13/dist-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated. 2025-09-08T08:05:11,388 !! 2025-09-08T08:05:11,388 ******************************************************************************** 2025-09-08T08:05:11,388 Please consider removing the following classifiers in favor of a SPDX license expression: 2025-09-08T08:05:11,388 License :: OSI Approved :: BSD License 2025-09-08T08:05:11,389 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. 2025-09-08T08:05:11,389 ******************************************************************************** 2025-09-08T08:05:11,389 !! 2025-09-08T08:05:11,389 self._finalize_license_expression() 2025-09-08T08:05:11,467 running egg_info 2025-09-08T08:05:11,546 creating /tmp/pip-pip-egg-info-eqlq8q5_/wlsqm.egg-info 2025-09-08T08:05:11,546 writing /tmp/pip-pip-egg-info-eqlq8q5_/wlsqm.egg-info/PKG-INFO 2025-09-08T08:05:11,548 writing dependency_links to /tmp/pip-pip-egg-info-eqlq8q5_/wlsqm.egg-info/dependency_links.txt 2025-09-08T08:05:11,548 writing requirements to /tmp/pip-pip-egg-info-eqlq8q5_/wlsqm.egg-info/requires.txt 2025-09-08T08:05:11,549 writing top-level names to /tmp/pip-pip-egg-info-eqlq8q5_/wlsqm.egg-info/top_level.txt 2025-09-08T08:05:11,549 writing manifest file '/tmp/pip-pip-egg-info-eqlq8q5_/wlsqm.egg-info/SOURCES.txt' 2025-09-08T08:05:11,864 reading manifest file '/tmp/pip-pip-egg-info-eqlq8q5_/wlsqm.egg-info/SOURCES.txt' 2025-09-08T08:05:11,865 adding license file 'LICENSE.md' 2025-09-08T08:05:11,868 writing manifest file '/tmp/pip-pip-egg-info-eqlq8q5_/wlsqm.egg-info/SOURCES.txt' 2025-09-08T08:05:12,760 Preparing metadata (setup.py): finished with status 'done' 2025-09-08T08:05:12,765 Source in /tmp/pip-wheel-h8pokkub/wlsqm_1e9dfb9debf34ee197e1e383223af1af has version 0.1.6, which satisfies requirement wlsqm==0.1.6 from https://files.pythonhosted.org/packages/bf/87/a4e1adc45e69f5032971b0b47251c0b87d1cd70b277b1548e3197f9af479/wlsqm-0.1.6.tar.gz 2025-09-08T08:05:12,766 Removed wlsqm==0.1.6 from https://files.pythonhosted.org/packages/bf/87/a4e1adc45e69f5032971b0b47251c0b87d1cd70b277b1548e3197f9af479/wlsqm-0.1.6.tar.gz from build tracker '/tmp/pip-build-tracker-1ycv8e62' 2025-09-08T08:05:12,769 Created temporary directory: /tmp/pip-unpack-u486lmgk 2025-09-08T08:05:12,770 Created temporary directory: /tmp/pip-unpack-czmpzj7s 2025-09-08T08:05:12,770 Building wheels for collected packages: wlsqm 2025-09-08T08:05:12,771 Created temporary directory: /tmp/pip-wheel-_m2b8joz 2025-09-08T08:05:12,771 DEPRECATION: Building 'wlsqm' using the legacy setup.py bdist_wheel mechanism, which will be removed in a future version. pip 25.3 will enforce this behaviour change. A possible replacement is to use the standardized build interface by setting the `--use-pep517` option, (possibly combined with `--no-build-isolation`), or adding a `pyproject.toml` file to the source tree of 'wlsqm'. Discussion can be found at https://github.com/pypa/pip/issues/6334 2025-09-08T08:05:12,773 Building wheel for wlsqm (setup.py): started 2025-09-08T08:05:12,773 Destination directory: /tmp/pip-wheel-_m2b8joz 2025-09-08T08:05:12,773 Running command python setup.py bdist_wheel 2025-09-08T08:05:13,484 build configuration selected: optimized 2025-09-08T08:05:13,485 /tmp/pip-wheel-h8pokkub/wlsqm_1e9dfb9debf34ee197e1e383223af1af/setup.py:149: DeprecationWarning: Attribute s is deprecated and will be removed in Python 3.14; use value instead 2025-09-08T08:05:13,485 version = ast.parse(line).body[0].value.s 2025-09-08T08:05:14,280 /usr/local/lib/python3.13/dist-packages/setuptools/__init__.py:92: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated. 2025-09-08T08:05:14,280 !! 2025-09-08T08:05:14,280 ******************************************************************************** 2025-09-08T08:05:14,280 Requirements should be satisfied by a PEP 517 installer. 2025-09-08T08:05:14,280 If you are using pip, you can try `pip install --use-pep517`. 2025-09-08T08:05:14,280 By 2025-Oct-31, you need to update your project and remove deprecated calls 2025-09-08T08:05:14,281 or your builds will no longer be supported. 2025-09-08T08:05:14,281 ******************************************************************************** 2025-09-08T08:05:14,281 !! 2025-09-08T08:05:14,281 dist.fetch_build_eggs(dist.setup_requires) 2025-09-08T08:05:14,707 /usr/local/lib/python3.13/dist-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated. 2025-09-08T08:05:14,707 !! 2025-09-08T08:05:14,708 ******************************************************************************** 2025-09-08T08:05:14,708 Please consider removing the following classifiers in favor of a SPDX license expression: 2025-09-08T08:05:14,708 License :: OSI Approved :: BSD License 2025-09-08T08:05:14,708 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. 2025-09-08T08:05:14,708 ******************************************************************************** 2025-09-08T08:05:14,708 !! 2025-09-08T08:05:14,708 self._finalize_license_expression() 2025-09-08T08:05:14,709 running bdist_wheel 2025-09-08T08:05:15,084 running build 2025-09-08T08:05:15,084 running build_py 2025-09-08T08:05:15,163 creating build/lib.linux-armv7l-cpython-313/wlsqm 2025-09-08T08:05:15,163 copying wlsqm/__init__.py -> build/lib.linux-armv7l-cpython-313/wlsqm 2025-09-08T08:05:15,164 creating build/lib.linux-armv7l-cpython-313/wlsqm/utils 2025-09-08T08:05:15,164 copying wlsqm/utils/__init__.py -> build/lib.linux-armv7l-cpython-313/wlsqm/utils 2025-09-08T08:05:15,165 creating build/lib.linux-armv7l-cpython-313/wlsqm/fitter 2025-09-08T08:05:15,165 copying wlsqm/fitter/__init__.py -> build/lib.linux-armv7l-cpython-313/wlsqm/fitter 2025-09-08T08:05:15,169 copying wlsqm/utils/ptrwrap.pxd -> build/lib.linux-armv7l-cpython-313/wlsqm/utils 2025-09-08T08:05:15,169 copying wlsqm/utils/lapackdrivers.pxd -> build/lib.linux-armv7l-cpython-313/wlsqm/utils 2025-09-08T08:05:15,170 copying wlsqm/utils/lapackdrivers.pyx -> build/lib.linux-armv7l-cpython-313/wlsqm/utils 2025-09-08T08:05:15,171 copying wlsqm/utils/ptrwrap.pyx -> build/lib.linux-armv7l-cpython-313/wlsqm/utils 2025-09-08T08:05:15,171 copying wlsqm/fitter/interp.pxd -> build/lib.linux-armv7l-cpython-313/wlsqm/fitter 2025-09-08T08:05:15,172 copying wlsqm/fitter/simple.pxd -> build/lib.linux-armv7l-cpython-313/wlsqm/fitter 2025-09-08T08:05:15,172 copying wlsqm/fitter/defs.pxd -> build/lib.linux-armv7l-cpython-313/wlsqm/fitter 2025-09-08T08:05:15,173 copying wlsqm/fitter/infra.pxd -> build/lib.linux-armv7l-cpython-313/wlsqm/fitter 2025-09-08T08:05:15,174 copying wlsqm/fitter/impl.pxd -> build/lib.linux-armv7l-cpython-313/wlsqm/fitter 2025-09-08T08:05:15,174 copying wlsqm/fitter/polyeval.pxd -> build/lib.linux-armv7l-cpython-313/wlsqm/fitter 2025-09-08T08:05:15,175 copying wlsqm/fitter/expert.pyx -> build/lib.linux-armv7l-cpython-313/wlsqm/fitter 2025-09-08T08:05:15,175 copying wlsqm/fitter/infra.pyx -> build/lib.linux-armv7l-cpython-313/wlsqm/fitter 2025-09-08T08:05:15,176 copying wlsqm/fitter/interp.pyx -> build/lib.linux-armv7l-cpython-313/wlsqm/fitter 2025-09-08T08:05:15,177 copying wlsqm/fitter/impl.pyx -> build/lib.linux-armv7l-cpython-313/wlsqm/fitter 2025-09-08T08:05:15,177 copying wlsqm/fitter/simple.pyx -> build/lib.linux-armv7l-cpython-313/wlsqm/fitter 2025-09-08T08:05:15,178 copying wlsqm/fitter/defs.pyx -> build/lib.linux-armv7l-cpython-313/wlsqm/fitter 2025-09-08T08:05:15,179 copying wlsqm/fitter/polyeval.pyx -> build/lib.linux-armv7l-cpython-313/wlsqm/fitter 2025-09-08T08:05:15,180 running build_ext 2025-09-08T08:05:15,188 building 'wlsqm.utils.lapackdrivers' extension 2025-09-08T08:05:15,188 creating build/temp.linux-armv7l-cpython-313/wlsqm/utils 2025-09-08T08:05:15,189 arm-linux-gnueabihf-gcc -fno-strict-overflow -Wsign-compare -DNDEBUG -g -O2 -Wall -fPIC -I/usr/include/python3.13 -c wlsqm/utils/lapackdrivers.c -o build/temp.linux-armv7l-cpython-313/wlsqm/utils/lapackdrivers.o -fopenmp -march=native -O2 -msse -msse2 -mfma -mfpmath=sse 2025-09-08T08:05:15,200 arm-linux-gnueabihf-gcc: error: unrecognized command-line option ‘-msse’ 2025-09-08T08:05:15,201 arm-linux-gnueabihf-gcc: error: unrecognized command-line option ‘-msse2’ 2025-09-08T08:05:15,202 arm-linux-gnueabihf-gcc: error: unrecognized command-line option ‘-mfma’ 2025-09-08T08:05:15,218 arm-linux-gnueabihf-gcc: error: unrecognized command-line option ‘-mfpmath=sse’ 2025-09-08T08:05:15,220 error: command '/usr/bin/arm-linux-gnueabihf-gcc' failed with exit code 1 2025-09-08T08:05:15,370 ERROR: python setup.py bdist_wheel exited with 1 2025-09-08T08:05:15,381 [bold magenta]full command[/]: [blue]/usr/bin/python3 -u -c ' 2025-09-08T08:05:15,381 exec(compile('"'"''"'"''"'"' 2025-09-08T08:05:15,381 # This is -- a caller that pip uses to run setup.py 2025-09-08T08:05:15,381 # 2025-09-08T08:05:15,381 # - It imports setuptools before invoking setup.py, to enable projects that directly 2025-09-08T08:05:15,381 # import from `distutils.core` to work with newer packaging standards. 2025-09-08T08:05:15,381 # - It provides a clear error message when setuptools is not installed. 2025-09-08T08:05:15,381 # - It sets `sys.argv[0]` to the underlying `setup.py`, when invoking `setup.py` so 2025-09-08T08:05:15,381 # setuptools doesn'"'"'t think the script is `-c`. This avoids the following warning: 2025-09-08T08:05:15,381 # manifest_maker: standard file '"'"'-c'"'"' not found". 2025-09-08T08:05:15,381 # - It generates a shim setup.py, for handling setup.cfg-only projects. 2025-09-08T08:05:15,381 import os, sys, tokenize, traceback 2025-09-08T08:05:15,381 2025-09-08T08:05:15,381 try: 2025-09-08T08:05:15,381 import setuptools 2025-09-08T08:05:15,381 except ImportError: 2025-09-08T08:05:15,381 print( 2025-09-08T08:05:15,381 "ERROR: Can not execute `setup.py` since setuptools failed to import in " 2025-09-08T08:05:15,381 "the build environment with exception:", 2025-09-08T08:05:15,381 file=sys.stderr, 2025-09-08T08:05:15,381 ) 2025-09-08T08:05:15,381 traceback.print_exc() 2025-09-08T08:05:15,381 sys.exit(1) 2025-09-08T08:05:15,381 2025-09-08T08:05:15,381 __file__ = %r 2025-09-08T08:05:15,381 sys.argv[0] = __file__ 2025-09-08T08:05:15,381 2025-09-08T08:05:15,381 if os.path.exists(__file__): 2025-09-08T08:05:15,381 filename = __file__ 2025-09-08T08:05:15,381 with tokenize.open(__file__) as f: 2025-09-08T08:05:15,381 setup_py_code = f.read() 2025-09-08T08:05:15,381 else: 2025-09-08T08:05:15,381 filename = "" 2025-09-08T08:05:15,381 setup_py_code = "from setuptools import setup; setup()" 2025-09-08T08:05:15,381 2025-09-08T08:05:15,381 exec(compile(setup_py_code, filename, "exec")) 2025-09-08T08:05:15,381 '"'"''"'"''"'"' % ('"'"'/tmp/pip-wheel-h8pokkub/wlsqm_1e9dfb9debf34ee197e1e383223af1af/setup.py'"'"',), "", "exec"))' bdist_wheel -d /tmp/pip-wheel-_m2b8joz[/] 2025-09-08T08:05:15,381 [bold magenta]cwd[/]: /tmp/pip-wheel-h8pokkub/wlsqm_1e9dfb9debf34ee197e1e383223af1af/ 2025-09-08T08:05:15,382 Building wheel for wlsqm (setup.py): finished with status 'error' 2025-09-08T08:05:15,382 ERROR: Failed building wheel for wlsqm 2025-09-08T08:05:15,383 Running setup.py clean for wlsqm 2025-09-08T08:05:15,384 Running command python setup.py clean 2025-09-08T08:05:16,093 build configuration selected: optimized 2025-09-08T08:05:16,094 /tmp/pip-wheel-h8pokkub/wlsqm_1e9dfb9debf34ee197e1e383223af1af/setup.py:149: DeprecationWarning: Attribute s is deprecated and will be removed in Python 3.14; use value instead 2025-09-08T08:05:16,094 version = ast.parse(line).body[0].value.s 2025-09-08T08:05:16,883 /usr/local/lib/python3.13/dist-packages/setuptools/__init__.py:92: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated. 2025-09-08T08:05:16,883 !! 2025-09-08T08:05:16,883 ******************************************************************************** 2025-09-08T08:05:16,883 Requirements should be satisfied by a PEP 517 installer. 2025-09-08T08:05:16,883 If you are using pip, you can try `pip install --use-pep517`. 2025-09-08T08:05:16,884 By 2025-Oct-31, you need to update your project and remove deprecated calls 2025-09-08T08:05:16,884 or your builds will no longer be supported. 2025-09-08T08:05:16,884 ******************************************************************************** 2025-09-08T08:05:16,884 !! 2025-09-08T08:05:16,884 dist.fetch_build_eggs(dist.setup_requires) 2025-09-08T08:05:17,307 /usr/local/lib/python3.13/dist-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated. 2025-09-08T08:05:17,307 !! 2025-09-08T08:05:17,308 ******************************************************************************** 2025-09-08T08:05:17,308 Please consider removing the following classifiers in favor of a SPDX license expression: 2025-09-08T08:05:17,308 License :: OSI Approved :: BSD License 2025-09-08T08:05:17,308 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. 2025-09-08T08:05:17,308 ******************************************************************************** 2025-09-08T08:05:17,308 !! 2025-09-08T08:05:17,309 self._finalize_license_expression() 2025-09-08T08:05:17,384 running clean 2025-09-08T08:05:17,531 removing 'build/temp.linux-armv7l-cpython-313' (and everything under it) 2025-09-08T08:05:17,532 removing 'build/lib.linux-armv7l-cpython-313' (and everything under it) 2025-09-08T08:05:17,533 'build/bdist.linux-armv7l' does not exist -- can't clean it 2025-09-08T08:05:17,533 'build/scripts-3.13' does not exist -- can't clean it 2025-09-08T08:05:17,533 removing 'build' 2025-09-08T08:05:17,679 Failed to build wlsqm 2025-09-08T08:05:17,680 ERROR: Failed to build one or more wheels 2025-09-08T08:05:17,681 Exception information: 2025-09-08T08:05:17,681 Traceback (most recent call last): 2025-09-08T08:05:17,681 File "/usr/lib/python3/dist-packages/pip/_internal/cli/base_command.py", line 105, in _run_wrapper 2025-09-08T08:05:17,681 status = _inner_run() 2025-09-08T08:05:17,681 File "/usr/lib/python3/dist-packages/pip/_internal/cli/base_command.py", line 96, in _inner_run 2025-09-08T08:05:17,681 return self.run(options, args) 2025-09-08T08:05:17,681 ~~~~~~~~^^^^^^^^^^^^^^^ 2025-09-08T08:05:17,681 File "/usr/lib/python3/dist-packages/pip/_internal/cli/req_command.py", line 68, in wrapper 2025-09-08T08:05:17,681 return func(self, options, args) 2025-09-08T08:05:17,681 File "/usr/lib/python3/dist-packages/pip/_internal/commands/wheel.py", line 180, in run 2025-09-08T08:05:17,681 raise CommandError("Failed to build one or more wheels") 2025-09-08T08:05:17,681 pip._internal.exceptions.CommandError: Failed to build one or more wheels 2025-09-08T08:05:17,685 Removed build tracker: '/tmp/pip-build-tracker-1ycv8e62'