2025-09-08T08:03:16,360 Created temporary directory: /tmp/pip-build-tracker-68yma6z2 2025-09-08T08:03:16,361 Initialized build tracking at /tmp/pip-build-tracker-68yma6z2 2025-09-08T08:03:16,361 Created build tracker: /tmp/pip-build-tracker-68yma6z2 2025-09-08T08:03:16,361 Entered build tracker: /tmp/pip-build-tracker-68yma6z2 2025-09-08T08:03:16,361 Created temporary directory: /tmp/pip-wheel-sazcx695 2025-09-08T08:03:16,365 Created temporary directory: /tmp/pip-ephem-wheel-cache-5lmdm5zt 2025-09-08T08:03:16,424 Looking in indexes: https://pypi.org/simple, https://www.piwheels.org/simple 2025-09-08T08:03:16,426 2 location(s) to search for versions of wlsqm: 2025-09-08T08:03:16,426 * https://pypi.org/simple/wlsqm/ 2025-09-08T08:03:16,426 * https://www.piwheels.org/simple/wlsqm/ 2025-09-08T08:03:16,427 Fetching project page and analyzing links: https://pypi.org/simple/wlsqm/ 2025-09-08T08:03:16,427 Getting page https://pypi.org/simple/wlsqm/ 2025-09-08T08:03:16,428 Found index url https://pypi.org/simple/ 2025-09-08T08:03:16,499 Fetched page https://pypi.org/simple/wlsqm/ as application/vnd.pypi.simple.v1+json 2025-09-08T08:03:16,500 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:03:16,500 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:03:16,501 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:03:16,501 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:03:16,501 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:03:16,501 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:03:16,502 Fetching project page and analyzing links: https://www.piwheels.org/simple/wlsqm/ 2025-09-08T08:03:16,502 Getting page https://www.piwheels.org/simple/wlsqm/ 2025-09-08T08:03:16,503 Found index url https://www.piwheels.org/simple/ 2025-09-08T08:03:16,584 Fetched page https://www.piwheels.org/simple/wlsqm/ as text/html 2025-09-08T08:03:16,585 Skipping link: not a file: https://www.piwheels.org/simple/wlsqm/ 2025-09-08T08:03:16,585 Skipping link: not a file: https://pypi.org/simple/wlsqm/ 2025-09-08T08:03:16,611 Given no hashes to check 1 links for project 'wlsqm': discarding no candidates 2025-09-08T08:03:16,612 Collecting wlsqm==0.1.5 2025-09-08T08:03:16,614 Created temporary directory: /tmp/pip-unpack-lyko3z26 2025-09-08T08:03:17,043 Downloading wlsqm-0.1.5.tar.gz (934 kB) 2025-09-08T08:03:17,275 Added wlsqm==0.1.5 from https://files.pythonhosted.org/packages/0f/37/d6e09c5fa4d2437dd239681b483a1a2c28f52673a2e6c80c0865420cf907/wlsqm-0.1.5.tar.gz to build tracker '/tmp/pip-build-tracker-68yma6z2' 2025-09-08T08:03:17,277 Running setup.py (path:/tmp/pip-wheel-sazcx695/wlsqm_f40c948c21cb4ca198e92d7d432711ce/setup.py) egg_info for package wlsqm 2025-09-08T08:03:17,277 Created temporary directory: /tmp/pip-pip-egg-info-f79rn4g9 2025-09-08T08:03:17,277 Preparing metadata (setup.py): started 2025-09-08T08:03:17,278 Running command python setup.py egg_info 2025-09-08T08:03:17,998 /tmp/pip-wheel-sazcx695/wlsqm_f40c948c21cb4ca198e92d7d432711ce/setup.py:148: DeprecationWarning: Attribute s is deprecated and will be removed in Python 3.14; use value instead 2025-09-08T08:03:17,998 version = ast.parse(line).body[0].value.s 2025-09-08T08:03:20,694 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:03:20,698 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:03:20,698 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:03:20,699 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:03:20,703 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:03:20,764 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:03:20,765 Possible solutions: 2025-09-08T08:03:20,765 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:03:20,765 2. Use an 'int' return type on 'expert_prepare_one_3D' to allow an error code to be returned. 2025-09-08T08:03:20,765 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:03:20,765 Possible solutions: 2025-09-08T08:03:20,765 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:03:20,765 2. Use an 'int' return type on 'expert_prepare_one_2D' to allow an error code to be returned. 2025-09-08T08:03:20,766 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:03:20,766 Possible solutions: 2025-09-08T08:03:20,766 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:03:20,766 2. Use an 'int' return type on 'expert_prepare_one_1D' to allow an error code to be returned. 2025-09-08T08:03:20,778 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:03:20,778 Possible solutions: 2025-09-08T08:03:20,778 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:03:20,778 2. Use an 'int' return type on 'expert_solve_one_basic' to allow an error code to be returned. 2025-09-08T08:03:22,171 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:03:22,171 Possible solutions: 2025-09-08T08:03:22,172 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:03:22,172 2. Use an 'int' return type on 'CaseManager_del' to allow an error code to be returned. 2025-09-08T08:03:22,199 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:03:22,200 Possible solutions: 2025-09-08T08:03:22,200 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:03:22,200 2. Use an 'int' return type on 'expert_prepare_one_3D' to allow an error code to be returned. 2025-09-08T08:03:22,204 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:03:22,204 Possible solutions: 2025-09-08T08:03:22,205 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:03:22,205 2. Use an 'int' return type on 'expert_prepare_one_3D' to allow an error code to be returned. 2025-09-08T08:03:22,209 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:03:22,210 Possible solutions: 2025-09-08T08:03:22,210 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:03:22,210 2. Use an 'int' return type on 'expert_prepare_one_2D' to allow an error code to be returned. 2025-09-08T08:03:22,214 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:03:22,214 Possible solutions: 2025-09-08T08:03:22,214 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:03:22,214 2. Use an 'int' return type on 'expert_prepare_one_2D' to allow an error code to be returned. 2025-09-08T08:03:22,218 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:03:22,219 Possible solutions: 2025-09-08T08:03:22,219 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:03:22,219 2. Use an 'int' return type on 'expert_prepare_one_1D' to allow an error code to be returned. 2025-09-08T08:03:22,222 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:03:22,223 Possible solutions: 2025-09-08T08:03:22,223 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:03:22,223 2. Use an 'int' return type on 'expert_prepare_one_1D' to allow an error code to be returned. 2025-09-08T08:03:22,244 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:03:22,244 Possible solutions: 2025-09-08T08:03:22,244 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:03:22,244 2. Use an 'int' return type on 'expert_solve_one_basic' to allow an error code to be returned. 2025-09-08T08:03:22,248 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:03:22,249 Possible solutions: 2025-09-08T08:03:22,249 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:03:22,249 2. Use an 'int' return type on 'expert_solve_one_basic' to allow an error code to be returned. 2025-09-08T08:03:22,250 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:03:22,250 Possible solutions: 2025-09-08T08:03:22,251 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:03:22,251 2. Use an 'int' return type on 'Case_get_fi' to allow an error code to be returned. 2025-09-08T08:03:22,257 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:03:22,257 Possible solutions: 2025-09-08T08:03:22,257 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:03:22,257 2. Use an 'int' return type on 'expert_solve_one_basic' to allow an error code to be returned. 2025-09-08T08:03:22,260 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:03:22,261 Possible solutions: 2025-09-08T08:03:22,261 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:03:22,261 2. Use an 'int' return type on 'expert_solve_one_basic' to allow an error code to be returned. 2025-09-08T08:03:22,261 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:03:22,262 Possible solutions: 2025-09-08T08:03:22,262 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:03:22,262 2. Use an 'int' return type on 'Case_get_fi' to allow an error code to be returned. 2025-09-08T08:03:22,298 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:03:22,298 Possible solutions: 2025-09-08T08:03:22,298 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:03:22,298 2. Use an 'int' return type on 'Case_get_fi' to allow an error code to be returned. 2025-09-08T08:03:22,330 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:03:22,330 Possible solutions: 2025-09-08T08:03:22,330 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:03:22,330 2. Use an 'int' return type on 'Case_get_fi' to allow an error code to be returned. 2025-09-08T08:03:22,349 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:03:22,349 Possible solutions: 2025-09-08T08:03:22,349 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:03:22,349 2. Use an 'int' return type on 'make_c_3D' to allow an error code to be returned. 2025-09-08T08:03:22,349 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:03:22,349 Possible solutions: 2025-09-08T08:03:22,349 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:03:22,349 2. Use an 'int' return type on 'make_A' to allow an error code to be returned. 2025-09-08T08:03:22,349 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:03:22,349 Possible solutions: 2025-09-08T08:03:22,350 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:03:22,350 2. Use an 'int' return type on 'preprocess_A' to allow an error code to be returned. 2025-09-08T08:03:22,350 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:03:22,350 Possible solutions: 2025-09-08T08:03:22,350 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:03:22,350 2. Use an 'int' return type on 'make_c_2D' to allow an error code to be returned. 2025-09-08T08:03:22,350 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:03:22,350 Possible solutions: 2025-09-08T08:03:22,351 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:03:22,351 2. Use an 'int' return type on 'make_A' to allow an error code to be returned. 2025-09-08T08:03:22,351 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:03:22,351 Possible solutions: 2025-09-08T08:03:22,351 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:03:22,351 2. Use an 'int' return type on 'preprocess_A' to allow an error code to be returned. 2025-09-08T08:03:22,351 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:03:22,351 Possible solutions: 2025-09-08T08:03:22,351 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:03:22,352 2. Use an 'int' return type on 'make_c_1D' to allow an error code to be returned. 2025-09-08T08:03:22,352 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:03:22,352 Possible solutions: 2025-09-08T08:03:22,352 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:03:22,352 2. Use an 'int' return type on 'make_A' to allow an error code to be returned. 2025-09-08T08:03:22,352 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:03:22,352 Possible solutions: 2025-09-08T08:03:22,352 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:03:22,352 2. Use an 'int' return type on 'preprocess_A' to allow an error code to be returned. 2025-09-08T08:03:22,352 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:03:22,353 Possible solutions: 2025-09-08T08:03:22,353 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:03:22,353 2. Use an 'int' return type on 'Case_set_fi' to allow an error code to be returned. 2025-09-08T08:03:22,353 performance hint: wlsqm/fitter/expert.pyx:808:14: Exception check after calling 'solve' will always require the GIL to be acquired. 2025-09-08T08:03:22,353 Possible solutions: 2025-09-08T08:03:22,353 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:03:22,353 2. Use an 'int' return type on 'solve' to allow an error code to be returned. 2025-09-08T08:03:22,354 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:03:22,354 Possible solutions: 2025-09-08T08:03:22,354 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:03:22,354 2. Use an 'int' return type on 'Case_set_fi' to allow an error code to be returned. 2025-09-08T08:03:22,354 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:03:22,354 Possible solutions: 2025-09-08T08:03:22,354 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:03:22,354 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:22,364 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:03:22,364 Possible solutions: 2025-09-08T08:03:22,364 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:03:22,364 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:22,367 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:03:22,368 Possible solutions: 2025-09-08T08:03:22,368 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:03:22,368 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:22,371 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:03:22,371 Possible solutions: 2025-09-08T08:03:22,371 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:03:22,371 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:22,375 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:03:22,375 Possible solutions: 2025-09-08T08:03:22,375 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:03:22,375 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:22,378 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:03:22,378 Possible solutions: 2025-09-08T08:03:22,378 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:03:22,378 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:22,381 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:03:22,381 Possible solutions: 2025-09-08T08:03:22,381 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:03:22,381 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:23,168 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:03:23,172 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:03:23,172 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:03:23,172 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:03:23,176 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:03:23,511 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:03:23,512 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:03:23,512 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:03:23,513 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:03:23,513 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:03:23,514 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:03:23,514 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:03:23,514 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:03:23,515 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:03:23,515 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:03:23,516 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:03:23,516 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:03:23,517 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:03:23,518 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:03:23,519 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:03:23,519 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:03:23,520 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:03:23,520 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:03:23,521 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:03:23,521 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:03:23,521 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:03:23,522 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:03:23,522 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:03:23,523 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:03:23,523 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:03:23,524 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:03:23,583 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:03:23,583 Possible solutions: 2025-09-08T08:03:23,583 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:03:23,584 2. Use an 'int' return type on 'make_c_nD' to allow an error code to be returned. 2025-09-08T08:03:23,584 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:03:23,584 Possible solutions: 2025-09-08T08:03:23,584 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:03:23,584 2. Use an 'int' return type on 'make_c_3D' to allow an error code to be returned. 2025-09-08T08:03:23,584 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:03:23,584 Possible solutions: 2025-09-08T08:03:23,584 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:03:23,584 2. Use an 'int' return type on 'make_c_2D' to allow an error code to be returned. 2025-09-08T08:03:23,585 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:03:23,585 Possible solutions: 2025-09-08T08:03:23,585 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:03:23,585 2. Use an 'int' return type on 'make_c_1D' to allow an error code to be returned. 2025-09-08T08:03:23,585 performance hint: wlsqm/fitter/impl.pyx:568:0: Exception check on 'make_A' will always require the GIL to be acquired. 2025-09-08T08:03:23,585 Possible solutions: 2025-09-08T08:03:23,585 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:03:23,585 2. Use an 'int' return type on 'make_A' to allow an error code to be returned. 2025-09-08T08:03:23,585 performance hint: wlsqm/fitter/impl.pyx:622:0: Exception check on 'preprocess_A' will always require the GIL to be acquired. 2025-09-08T08:03:23,585 Possible solutions: 2025-09-08T08:03:23,585 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:03:23,586 2. Use an 'int' return type on 'preprocess_A' to allow an error code to be returned. 2025-09-08T08:03:23,586 performance hint: wlsqm/fitter/impl.pyx:734:0: Exception check on 'solve' will always require the GIL to be acquired. 2025-09-08T08:03:23,586 Possible solutions: 2025-09-08T08:03:23,586 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:03:23,586 2. Use an 'int' return type on 'solve' to allow an error code to be returned. 2025-09-08T08:03:23,586 performance hint: wlsqm/fitter/impl.pyx:863:0: Exception check on 'solve_contig' will always require the GIL to be acquired. 2025-09-08T08:03:23,586 Possible solutions: 2025-09-08T08:03:23,587 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:03:23,587 2. Use an 'int' return type on 'solve_contig' to allow an error code to be returned. 2025-09-08T08:03:23,587 performance hint: wlsqm/fitter/impl.pxd:47:24: No exception value declared for 'solve_iterative' in pxd file. 2025-09-08T08:03:23,587 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:03:23,588 Suggest adding an explicit exception value. 2025-09-08T08:03:24,881 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:03:24,881 Possible solutions: 2025-09-08T08:03:24,881 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:03:24,881 2. Use an 'int' return type on 'make_c_3D' to allow an error code to be returned. 2025-09-08T08:03:24,881 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:03:24,882 Possible solutions: 2025-09-08T08:03:24,882 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:03:24,882 2. Use an 'int' return type on 'make_c_2D' to allow an error code to be returned. 2025-09-08T08:03:24,882 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:03:24,882 Possible solutions: 2025-09-08T08:03:24,882 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:03:24,882 2. Use an 'int' return type on 'make_c_1D' to allow an error code to be returned. 2025-09-08T08:03:24,902 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:03:24,903 Possible solutions: 2025-09-08T08:03:24,903 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:03:24,903 2. Use an 'int' return type on 'Case_make_weights' to allow an error code to be returned. 2025-09-08T08:03:24,927 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:03:24,927 Possible solutions: 2025-09-08T08:03:24,927 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:03:24,927 2. Use an 'int' return type on 'Case_make_weights' to allow an error code to be returned. 2025-09-08T08:03:24,935 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:03:24,935 Possible solutions: 2025-09-08T08:03:24,935 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:03:24,935 2. Use an 'int' return type on 'Case_make_weights' to allow an error code to be returned. 2025-09-08T08:03:24,941 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:03:24,942 Possible solutions: 2025-09-08T08:03:24,942 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:03:24,942 2. Use an 'int' return type on 'copygeneral_c' to allow an error code to be returned. 2025-09-08T08:03:24,942 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:03:24,942 Possible solutions: 2025-09-08T08:03:24,942 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:03:24,942 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:24,942 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:03:24,942 Possible solutions: 2025-09-08T08:03:24,942 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:03:24,943 2. Use an 'int' return type on 'apply_scaling_c' to allow an error code to be returned. 2025-09-08T08:03:24,943 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:03:24,943 Possible solutions: 2025-09-08T08:03:24,943 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:03:24,943 2. Use an 'int' return type on 'copygeneral_c' to allow an error code to be returned. 2025-09-08T08:03:24,947 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:03:24,947 Possible solutions: 2025-09-08T08:03:24,948 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:03:24,948 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:24,957 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:03:24,957 Possible solutions: 2025-09-08T08:03:24,957 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:03:24,958 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:24,965 performance hint: wlsqm/fitter/impl.pyx:995:9: Exception check after calling 'solve' will always require the GIL to be acquired. 2025-09-08T08:03:24,965 Possible solutions: 2025-09-08T08:03:24,966 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:03:24,966 2. Use an 'int' return type on 'solve' to allow an error code to be returned. 2025-09-08T08:03:24,966 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:03:24,966 Possible solutions: 2025-09-08T08:03:24,966 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:03:24,966 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:24,966 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:03:24,966 Possible solutions: 2025-09-08T08:03:24,966 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:03:24,966 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:24,968 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:03:24,968 Possible solutions: 2025-09-08T08:03:24,968 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:03:24,968 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:24,970 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:03:24,970 Possible solutions: 2025-09-08T08:03:24,970 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:03:24,971 2. Use an 'int' return type on 'solve_contig' to allow an error code to be returned. 2025-09-08T08:03:25,036 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:03:25,040 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:03:25,041 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:03:25,041 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:03:25,045 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:03:25,074 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:03:25,080 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:03:25,085 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:03:25,088 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:03:25,089 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:03:25,101 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:03:25,120 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:03:25,339 performance hint: wlsqm/fitter/infra.pxd:18:23: No exception value declared for 'number_of_dofs' in pxd file. 2025-09-08T08:03:25,340 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:03:25,340 Suggest adding an explicit exception value. 2025-09-08T08:03:25,340 performance hint: wlsqm/fitter/infra.pxd:19:31: No exception value declared for 'number_of_reduced_dofs' in pxd file. 2025-09-08T08:03:25,340 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:03:25,340 Suggest adding an explicit exception value. 2025-09-08T08:03:25,340 performance hint: wlsqm/fitter/infra.pxd:20:14: No exception value declared for 'remap' in pxd file. 2025-09-08T08:03:25,340 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:03:25,340 Suggest adding an explicit exception value. 2025-09-08T08:03:25,341 performance hint: wlsqm/fitter/infra.pyx:276:0: Exception check on 'Allocator_free' will always require the GIL to be acquired. 2025-09-08T08:03:25,341 Possible solutions: 2025-09-08T08:03:25,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:03:25,341 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:03:25,342 performance hint: wlsqm/fitter/infra.pxd:39:33: No exception value declared for 'Allocator_size_remaining' in pxd file. 2025-09-08T08:03:25,342 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:03:25,342 Suggest adding an explicit exception value. 2025-09-08T08:03:25,342 performance hint: wlsqm/fitter/infra.pyx:285:0: Exception check on 'Allocator_del' will always require the GIL to be acquired. 2025-09-08T08:03:25,342 Possible solutions: 2025-09-08T08:03:25,342 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:03:25,342 2. Use an 'int' return type on 'Allocator_del' to allow an error code to be returned. 2025-09-08T08:03:25,343 performance hint: wlsqm/fitter/infra.pyx:467:0: Exception check on 'CaseManager_deallocate' will always require the GIL to be acquired. 2025-09-08T08:03:25,343 Possible solutions: 2025-09-08T08:03:25,343 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:03:25,343 2. Use an 'int' return type on 'CaseManager_deallocate' to allow an error code to be returned. 2025-09-08T08:03:25,343 performance hint: wlsqm/fitter/infra.pyx:489:0: Exception check on 'CaseManager_del' will always require the GIL to be acquired. 2025-09-08T08:03:25,343 Possible solutions: 2025-09-08T08:03:25,344 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:03:25,344 2. Use an 'int' return type on 'CaseManager_del' to allow an error code to be returned. 2025-09-08T08:03:25,345 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:03:25,345 Possible solutions: 2025-09-08T08:03:25,345 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:03:25,345 2. Use an 'int' return type on 'Case_make_weights' to allow an error code to be returned. 2025-09-08T08:03:25,345 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:03:25,345 Possible solutions: 2025-09-08T08:03:25,345 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:03:25,345 2. Use an 'int' return type on 'Case_determine_sizes' to allow an error code to be returned. 2025-09-08T08:03:25,346 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:03:25,346 Possible solutions: 2025-09-08T08:03:25,346 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:03:25,346 2. Use an 'int' return type on 'Case_set_fi' to allow an error code to be returned. 2025-09-08T08:03:25,346 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:03:25,346 Possible solutions: 2025-09-08T08:03:25,346 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:03:25,346 2. Use an 'int' return type on 'Case_get_fi' to allow an error code to be returned. 2025-09-08T08:03:25,346 performance hint: wlsqm/fitter/infra.pyx:868:0: Exception check on 'Case_deallocate' will always require the GIL to be acquired. 2025-09-08T08:03:25,346 Possible solutions: 2025-09-08T08:03:25,347 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:03:25,347 2. Use an 'int' return type on 'Case_deallocate' to allow an error code to be returned. 2025-09-08T08:03:25,347 performance hint: wlsqm/fitter/infra.pyx:917:0: Exception check on 'Case_del' will always require the GIL to be acquired. 2025-09-08T08:03:25,347 Possible solutions: 2025-09-08T08:03:25,347 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:03:25,347 2. Use an 'int' return type on 'Case_del' to allow an error code to be returned. 2025-09-08T08:03:25,606 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:03:25,606 Possible solutions: 2025-09-08T08:03:25,606 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:03:25,606 2. Use an 'int' return type on 'Case_deallocate' to allow an error code to be returned. 2025-09-08T08:03:25,606 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:03:25,607 Possible solutions: 2025-09-08T08:03:25,607 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:03:25,607 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:03:25,607 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:03:25,607 Possible solutions: 2025-09-08T08:03:25,607 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:03:25,607 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:03:25,607 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:03:25,607 Possible solutions: 2025-09-08T08:03:25,607 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:03:25,608 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:03:25,608 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:03:25,608 Possible solutions: 2025-09-08T08:03:25,608 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:03:25,608 2. Use an 'int' return type on 'Allocator_del' to allow an error code to be returned. 2025-09-08T08:03:25,609 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:03:25,609 Possible solutions: 2025-09-08T08:03:25,609 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:03:25,609 2. Use an 'int' return type on 'CaseManager_deallocate' to allow an error code to be returned. 2025-09-08T08:03:25,609 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:03:25,610 Possible solutions: 2025-09-08T08:03:25,610 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:03:25,610 2. Use an 'int' return type on 'Case_del' to allow an error code to be returned. 2025-09-08T08:03:25,630 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:03:25,630 Possible solutions: 2025-09-08T08:03:25,630 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:03:25,631 2. Use an 'int' return type on 'Case_determine_sizes' to allow an error code to be returned. 2025-09-08T08:03:25,639 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:03:25,639 Possible solutions: 2025-09-08T08:03:25,639 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:03:25,639 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:03:25,639 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:03:25,640 Possible solutions: 2025-09-08T08:03:25,640 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:03:25,640 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:03:25,640 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:03:25,640 Possible solutions: 2025-09-08T08:03:25,640 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:03:25,640 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:03:25,640 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:03:25,640 Possible solutions: 2025-09-08T08:03:25,640 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:03:25,641 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:03:25,641 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:03:25,641 Possible solutions: 2025-09-08T08:03:25,641 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:03:25,641 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:03:25,641 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:03:25,641 Possible solutions: 2025-09-08T08:03:25,641 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:03:25,641 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:03:25,641 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:03:25,642 Possible solutions: 2025-09-08T08:03:25,642 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:03:25,642 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:03:25,642 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:03:25,642 Possible solutions: 2025-09-08T08:03:25,642 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:03:25,642 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:03:25,642 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:03:25,642 Possible solutions: 2025-09-08T08:03:25,642 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:03:25,643 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:03:25,643 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:03:25,643 Possible solutions: 2025-09-08T08:03:25,643 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:03:25,643 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:03:25,643 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:03:25,643 Possible solutions: 2025-09-08T08:03:25,643 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:03:25,643 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:03:25,643 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:03:25,643 Possible solutions: 2025-09-08T08:03:25,644 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:03:25,644 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:03:25,644 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:03:25,644 Possible solutions: 2025-09-08T08:03:25,644 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:03:25,644 2. Use an 'int' return type on 'Allocator_free' to allow an error code to be returned. 2025-09-08T08:03:25,645 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:03:25,645 Possible solutions: 2025-09-08T08:03:25,645 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:03:25,645 2. Use an 'int' return type on 'Case_deallocate' to allow an error code to be returned. 2025-09-08T08:03:25,645 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:03:25,645 Possible solutions: 2025-09-08T08:03:25,645 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:03:25,645 2. Use an 'int' return type on 'Allocator_del' to allow an error code to be returned. 2025-09-08T08:03:26,090 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:03:26,094 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:03:26,095 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:03:26,095 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:03:26,099 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:03:26,402 performance hint: wlsqm/fitter/interp.pxd:17:23: No exception value declared for 'interpolate_nD' in pxd file. 2025-09-08T08:03:26,402 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:03:26,402 Suggest adding an explicit exception value. 2025-09-08T08:03:26,403 performance hint: wlsqm/fitter/interp.pxd:19:23: No exception value declared for 'interpolate_3D' in pxd file. 2025-09-08T08:03:26,403 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:03:26,403 Suggest adding an explicit exception value. 2025-09-08T08:03:26,403 performance hint: wlsqm/fitter/interp.pxd:20:23: No exception value declared for 'interpolate_2D' in pxd file. 2025-09-08T08:03:26,404 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:03:26,404 Suggest adding an explicit exception value. 2025-09-08T08:03:26,404 performance hint: wlsqm/fitter/interp.pxd:21:23: No exception value declared for 'interpolate_1D' in pxd file. 2025-09-08T08:03:26,404 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:03:26,404 Suggest adding an explicit exception value. 2025-09-08T08:03:28,208 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:03:28,208 Possible solutions: 2025-09-08T08:03:28,208 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:03:28,208 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,213 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:03:28,213 Possible solutions: 2025-09-08T08:03:28,213 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:03:28,213 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,217 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:03:28,217 Possible solutions: 2025-09-08T08:03:28,217 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:03:28,217 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,220 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:03:28,221 Possible solutions: 2025-09-08T08:03:28,221 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:03:28,221 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,223 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:03:28,223 Possible solutions: 2025-09-08T08:03:28,223 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:03:28,223 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,225 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:03:28,226 Possible solutions: 2025-09-08T08:03:28,226 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:03:28,226 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,228 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:03:28,228 Possible solutions: 2025-09-08T08:03:28,228 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:03:28,228 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,230 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:03:28,231 Possible solutions: 2025-09-08T08:03:28,231 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:03:28,231 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,233 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:03:28,233 Possible solutions: 2025-09-08T08:03:28,233 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:03:28,233 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,235 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:03:28,236 Possible solutions: 2025-09-08T08:03:28,236 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:03:28,236 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,237 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:03:28,237 Possible solutions: 2025-09-08T08:03:28,237 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:03:28,237 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,238 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:03:28,239 Possible solutions: 2025-09-08T08:03:28,239 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:03:28,239 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,240 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:03:28,240 Possible solutions: 2025-09-08T08:03:28,240 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:03:28,240 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,242 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:03:28,242 Possible solutions: 2025-09-08T08:03:28,242 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:03:28,242 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,244 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:03:28,244 Possible solutions: 2025-09-08T08:03:28,244 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:03:28,244 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,245 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:03:28,245 Possible solutions: 2025-09-08T08:03:28,245 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:03:28,245 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,247 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:03:28,247 Possible solutions: 2025-09-08T08:03:28,247 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:03:28,247 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,248 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:03:28,248 Possible solutions: 2025-09-08T08:03:28,248 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:03:28,248 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,250 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:03:28,250 Possible solutions: 2025-09-08T08:03:28,250 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:03:28,250 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,251 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:03:28,251 Possible solutions: 2025-09-08T08:03:28,251 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:03:28,251 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,252 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:03:28,252 Possible solutions: 2025-09-08T08:03:28,252 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:03:28,252 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,253 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:03:28,253 Possible solutions: 2025-09-08T08:03:28,253 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:03:28,253 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,253 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:03:28,254 Possible solutions: 2025-09-08T08:03:28,254 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:03:28,254 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,254 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:03:28,254 Possible solutions: 2025-09-08T08:03:28,254 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:03:28,255 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,255 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:03:28,255 Possible solutions: 2025-09-08T08:03:28,255 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:03:28,255 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,256 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:03:28,256 Possible solutions: 2025-09-08T08:03:28,256 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:03:28,256 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,257 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:03:28,257 Possible solutions: 2025-09-08T08:03:28,257 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:03:28,257 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,258 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:03:28,258 Possible solutions: 2025-09-08T08:03:28,258 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:03:28,258 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,258 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:03:28,258 Possible solutions: 2025-09-08T08:03:28,259 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:03:28,259 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,259 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:03:28,259 Possible solutions: 2025-09-08T08:03:28,259 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:03:28,259 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,260 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:03:28,260 Possible solutions: 2025-09-08T08:03:28,260 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:03:28,260 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,261 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:03:28,261 Possible solutions: 2025-09-08T08:03:28,261 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:03:28,261 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,262 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:03:28,262 Possible solutions: 2025-09-08T08:03:28,262 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:03:28,262 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,262 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:03:28,262 Possible solutions: 2025-09-08T08:03:28,263 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:03:28,263 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,263 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:03:28,263 Possible solutions: 2025-09-08T08:03:28,263 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:03:28,263 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,265 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:03:28,265 Possible solutions: 2025-09-08T08:03:28,265 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:03:28,265 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,268 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:03:28,268 Possible solutions: 2025-09-08T08:03:28,268 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:03:28,269 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,271 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:03:28,271 Possible solutions: 2025-09-08T08:03:28,271 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:03:28,271 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,273 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:03:28,273 Possible solutions: 2025-09-08T08:03:28,273 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:03:28,273 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,274 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:03:28,275 Possible solutions: 2025-09-08T08:03:28,275 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:03:28,275 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,276 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:03:28,276 Possible solutions: 2025-09-08T08:03:28,277 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:03:28,277 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,278 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:03:28,278 Possible solutions: 2025-09-08T08:03:28,278 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:03:28,278 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,279 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:03:28,279 Possible solutions: 2025-09-08T08:03:28,279 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:03:28,279 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,280 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:03:28,280 Possible solutions: 2025-09-08T08:03:28,280 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:03:28,281 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,282 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:03:28,282 Possible solutions: 2025-09-08T08:03:28,282 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:03:28,282 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,282 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:03:28,282 Possible solutions: 2025-09-08T08:03:28,283 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:03:28,283 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,283 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:03:28,283 Possible solutions: 2025-09-08T08:03:28,283 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:03:28,283 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,284 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:03:28,284 Possible solutions: 2025-09-08T08:03:28,284 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:03:28,284 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,285 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:03:28,285 Possible solutions: 2025-09-08T08:03:28,285 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:03:28,285 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,286 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:03:28,286 Possible solutions: 2025-09-08T08:03:28,286 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:03:28,286 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,287 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:03:28,287 Possible solutions: 2025-09-08T08:03:28,287 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:03:28,287 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,290 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:03:28,290 Possible solutions: 2025-09-08T08:03:28,290 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:03:28,290 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,291 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:03:28,291 Possible solutions: 2025-09-08T08:03:28,291 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:03:28,291 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,292 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:03:28,292 Possible solutions: 2025-09-08T08:03:28,292 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:03:28,292 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,293 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:03:28,293 Possible solutions: 2025-09-08T08:03:28,293 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:03:28,293 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:28,962 performance hint: wlsqm/fitter/polyeval.pxd:15:18: No exception value declared for 'taylor_3D' in pxd file. 2025-09-08T08:03:28,962 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:03:28,962 Suggest adding an explicit exception value. 2025-09-08T08:03:28,962 performance hint: wlsqm/fitter/polyeval.pxd:16:19: No exception value declared for 'general_3D' in pxd file. 2025-09-08T08:03:28,962 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:03:28,963 Suggest adding an explicit exception value. 2025-09-08T08:03:28,963 performance hint: wlsqm/fitter/polyeval.pxd:18:18: No exception value declared for 'taylor_2D' in pxd file. 2025-09-08T08:03:28,963 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:03:28,963 Suggest adding an explicit exception value. 2025-09-08T08:03:28,964 performance hint: wlsqm/fitter/polyeval.pxd:19:19: No exception value declared for 'general_2D' in pxd file. 2025-09-08T08:03:28,964 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:03:28,964 Suggest adding an explicit exception value. 2025-09-08T08:03:28,964 performance hint: wlsqm/fitter/polyeval.pxd:21:18: No exception value declared for 'taylor_1D' in pxd file. 2025-09-08T08:03:28,964 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:03:28,964 Suggest adding an explicit exception value. 2025-09-08T08:03:28,965 performance hint: wlsqm/fitter/polyeval.pxd:22:19: No exception value declared for 'general_1D' in pxd file. 2025-09-08T08:03:28,965 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:03:28,965 Suggest adding an explicit exception value. 2025-09-08T08:03:30,355 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:03:30,356 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:03:30,358 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:03:30,360 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:03:30,364 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:03:30,366 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:03:30,841 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:03:30,845 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:03:30,852 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:03:30,864 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:03:30,876 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:03:30,889 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:03:31,162 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:03:31,166 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:03:31,167 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:03:31,167 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:03:31,171 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:03:33,030 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:03:33,030 Possible solutions: 2025-09-08T08:03:33,030 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:03:33,030 2. Use an 'int' return type on 'make_c_nD' to allow an error code to be returned. 2025-09-08T08:03:33,031 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:03:33,031 Possible solutions: 2025-09-08T08:03:33,031 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:03:33,031 2. Use an 'int' return type on 'make_A' to allow an error code to be returned. 2025-09-08T08:03:33,031 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:03:33,031 Possible solutions: 2025-09-08T08:03:33,031 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:03:33,031 2. Use an 'int' return type on 'preprocess_A' to allow an error code to be returned. 2025-09-08T08:03:33,031 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:03:33,032 Possible solutions: 2025-09-08T08:03:33,032 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:03:33,032 2. Use an 'int' return type on 'Case_set_fi' to allow an error code to be returned. 2025-09-08T08:03:33,032 performance hint: wlsqm/fitter/simple.pyx:644:14: Exception check after calling 'solve' will always require the GIL to be acquired. 2025-09-08T08:03:33,032 Possible solutions: 2025-09-08T08:03:33,032 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:03:33,032 2. Use an 'int' return type on 'solve' to allow an error code to be returned. 2025-09-08T08:03:33,032 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:03:33,032 Possible solutions: 2025-09-08T08:03:33,032 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:03:33,032 2. Use an 'int' return type on 'Case_get_fi' to allow an error code to be returned. 2025-09-08T08:03:33,033 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:03:33,033 Possible solutions: 2025-09-08T08:03:33,033 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:03:33,033 2. Use an 'int' return type on 'Case_del' to allow an error code to be returned. 2025-09-08T08:03:33,035 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:03:33,035 Possible solutions: 2025-09-08T08:03:33,035 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:03:33,035 2. Use an 'int' return type on 'make_c_nD' to allow an error code to be returned. 2025-09-08T08:03:33,035 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:03:33,035 Possible solutions: 2025-09-08T08:03:33,035 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:03:33,036 2. Use an 'int' return type on 'make_A' to allow an error code to be returned. 2025-09-08T08:03:33,036 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:03:33,036 Possible solutions: 2025-09-08T08:03:33,036 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:03:33,036 2. Use an 'int' return type on 'preprocess_A' to allow an error code to be returned. 2025-09-08T08:03:33,036 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:03:33,036 Possible solutions: 2025-09-08T08:03:33,036 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:03:33,036 2. Use an 'int' return type on 'Case_set_fi' to allow an error code to be returned. 2025-09-08T08:03:33,036 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:03:33,037 Possible solutions: 2025-09-08T08:03:33,037 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:03:33,037 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:33,037 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:03:33,037 Possible solutions: 2025-09-08T08:03:33,037 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:03:33,037 2. Use an 'int' return type on 'Case_get_fi' to allow an error code to be returned. 2025-09-08T08:03:33,037 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:03:33,037 Possible solutions: 2025-09-08T08:03:33,037 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:03:33,037 2. Use an 'int' return type on 'Case_del' to allow an error code to be returned. 2025-09-08T08:03:33,046 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:03:33,046 Possible solutions: 2025-09-08T08:03:33,046 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:03:33,046 2. Use an 'int' return type on 'make_c_nD' to allow an error code to be returned. 2025-09-08T08:03:33,046 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:03:33,046 Possible solutions: 2025-09-08T08:03:33,047 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:03:33,047 2. Use an 'int' return type on 'make_A' to allow an error code to be returned. 2025-09-08T08:03:33,047 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:03:33,047 Possible solutions: 2025-09-08T08:03:33,047 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:03:33,047 2. Use an 'int' return type on 'preprocess_A' to allow an error code to be returned. 2025-09-08T08:03:33,047 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:03:33,047 Possible solutions: 2025-09-08T08:03:33,047 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:03:33,047 2. Use an 'int' return type on 'Case_set_fi' to allow an error code to be returned. 2025-09-08T08:03:33,050 performance hint: wlsqm/fitter/simple.pyx:774:26: Exception check after calling 'solve' will always require the GIL to be acquired. 2025-09-08T08:03:33,050 Possible solutions: 2025-09-08T08:03:33,050 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:03:33,050 2. Use an 'int' return type on 'solve' to allow an error code to be returned. 2025-09-08T08:03:33,055 performance hint: wlsqm/fitter/simple.pyx:776:26: Exception check after calling 'solve' will always require the GIL to be acquired. 2025-09-08T08:03:33,055 Possible solutions: 2025-09-08T08:03:33,055 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:03:33,055 2. Use an 'int' return type on 'solve' to allow an error code to be returned. 2025-09-08T08:03:33,056 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:03:33,056 Possible solutions: 2025-09-08T08:03:33,056 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:03:33,056 2. Use an 'int' return type on 'Case_get_fi' to allow an error code to be returned. 2025-09-08T08:03:33,061 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:03:33,061 Possible solutions: 2025-09-08T08:03:33,061 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:03:33,061 2. Use an 'int' return type on 'make_c_nD' to allow an error code to be returned. 2025-09-08T08:03:33,061 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:03:33,061 Possible solutions: 2025-09-08T08:03:33,061 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:03:33,062 2. Use an 'int' return type on 'make_A' to allow an error code to be returned. 2025-09-08T08:03:33,062 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:03:33,062 Possible solutions: 2025-09-08T08:03:33,062 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:03:33,062 2. Use an 'int' return type on 'preprocess_A' to allow an error code to be returned. 2025-09-08T08:03:33,062 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:03:33,062 Possible solutions: 2025-09-08T08:03:33,062 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:03:33,062 2. Use an 'int' return type on 'Case_set_fi' to allow an error code to be returned. 2025-09-08T08:03:33,064 performance hint: wlsqm/fitter/simple.pyx:808:26: Exception check after calling 'solve' will always require the GIL to be acquired. 2025-09-08T08:03:33,065 Possible solutions: 2025-09-08T08:03:33,065 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:03:33,065 2. Use an 'int' return type on 'solve' to allow an error code to be returned. 2025-09-08T08:03:33,070 performance hint: wlsqm/fitter/simple.pyx:810:26: Exception check after calling 'solve' will always require the GIL to be acquired. 2025-09-08T08:03:33,070 Possible solutions: 2025-09-08T08:03:33,070 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:03:33,070 2. Use an 'int' return type on 'solve' to allow an error code to be returned. 2025-09-08T08:03:33,071 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:03:33,071 Possible solutions: 2025-09-08T08:03:33,071 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:03:33,071 2. Use an 'int' return type on 'Case_get_fi' to allow an error code to be returned. 2025-09-08T08:03:33,071 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:03:33,071 Possible solutions: 2025-09-08T08:03:33,071 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:03:33,071 2. Use an 'int' return type on 'CaseManager_del' to allow an error code to be returned. 2025-09-08T08:03:33,081 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:03:33,081 Possible solutions: 2025-09-08T08:03:33,081 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:03:33,081 2. Use an 'int' return type on 'make_c_nD' to allow an error code to be returned. 2025-09-08T08:03:33,082 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:03:33,082 Possible solutions: 2025-09-08T08:03:33,082 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:03:33,082 2. Use an 'int' return type on 'make_A' to allow an error code to be returned. 2025-09-08T08:03:33,082 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:03:33,082 Possible solutions: 2025-09-08T08:03:33,082 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:03:33,082 2. Use an 'int' return type on 'preprocess_A' to allow an error code to be returned. 2025-09-08T08:03:33,082 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:03:33,082 Possible solutions: 2025-09-08T08:03:33,082 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:03:33,083 2. Use an 'int' return type on 'Case_set_fi' to allow an error code to be returned. 2025-09-08T08:03:33,087 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:03:33,088 Possible solutions: 2025-09-08T08:03:33,088 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:03:33,088 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:33,096 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:03:33,096 Possible solutions: 2025-09-08T08:03:33,096 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:03:33,096 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:33,097 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:03:33,097 Possible solutions: 2025-09-08T08:03:33,097 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:03:33,097 2. Use an 'int' return type on 'Case_get_fi' to allow an error code to be returned. 2025-09-08T08:03:33,102 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:03:33,102 Possible solutions: 2025-09-08T08:03:33,102 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:03:33,102 2. Use an 'int' return type on 'make_c_nD' to allow an error code to be returned. 2025-09-08T08:03:33,102 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:03:33,103 Possible solutions: 2025-09-08T08:03:33,103 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:03:33,103 2. Use an 'int' return type on 'make_A' to allow an error code to be returned. 2025-09-08T08:03:33,103 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:03:33,103 Possible solutions: 2025-09-08T08:03:33,103 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:03:33,103 2. Use an 'int' return type on 'preprocess_A' to allow an error code to be returned. 2025-09-08T08:03:33,103 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:03:33,103 Possible solutions: 2025-09-08T08:03:33,103 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:03:33,103 2. Use an 'int' return type on 'Case_set_fi' to allow an error code to be returned. 2025-09-08T08:03:33,108 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:03:33,108 Possible solutions: 2025-09-08T08:03:33,108 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:03:33,108 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:33,115 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:03:33,116 Possible solutions: 2025-09-08T08:03:33,116 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:03:33,116 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:33,117 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:03:33,117 Possible solutions: 2025-09-08T08:03:33,117 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:03:33,117 2. Use an 'int' return type on 'Case_get_fi' to allow an error code to be returned. 2025-09-08T08:03:33,117 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:03:33,117 Possible solutions: 2025-09-08T08:03:33,117 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:03:33,117 2. Use an 'int' return type on 'CaseManager_del' to allow an error code to be returned. 2025-09-08T08:03:33,127 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:03:33,127 Possible solutions: 2025-09-08T08:03:33,127 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:03:33,127 2. Use an 'int' return type on 'make_c_nD' to allow an error code to be returned. 2025-09-08T08:03:33,127 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:03:33,128 Possible solutions: 2025-09-08T08:03:33,128 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:03:33,128 2. Use an 'int' return type on 'make_A' to allow an error code to be returned. 2025-09-08T08:03:33,128 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:03:33,128 Possible solutions: 2025-09-08T08:03:33,128 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:03:33,128 2. Use an 'int' return type on 'preprocess_A' to allow an error code to be returned. 2025-09-08T08:03:33,128 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:03:33,128 Possible solutions: 2025-09-08T08:03:33,128 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:03:33,128 2. Use an 'int' return type on 'Case_set_fi' to allow an error code to be returned. 2025-09-08T08:03:33,131 performance hint: wlsqm/fitter/simple.pyx:1004:26: Exception check after calling 'solve' will always require the GIL to be acquired. 2025-09-08T08:03:33,131 Possible solutions: 2025-09-08T08:03:33,131 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:03:33,131 2. Use an 'int' return type on 'solve' to allow an error code to be returned. 2025-09-08T08:03:33,136 performance hint: wlsqm/fitter/simple.pyx:1006:26: Exception check after calling 'solve' will always require the GIL to be acquired. 2025-09-08T08:03:33,136 Possible solutions: 2025-09-08T08:03:33,136 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:03:33,136 2. Use an 'int' return type on 'solve' to allow an error code to be returned. 2025-09-08T08:03:33,138 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:03:33,138 Possible solutions: 2025-09-08T08:03:33,139 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:03:33,139 2. Use an 'int' return type on 'Case_get_fi' to allow an error code to be returned. 2025-09-08T08:03:33,145 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:03:33,145 Possible solutions: 2025-09-08T08:03:33,145 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:03:33,145 2. Use an 'int' return type on 'make_c_nD' to allow an error code to be returned. 2025-09-08T08:03:33,145 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:03:33,145 Possible solutions: 2025-09-08T08:03:33,145 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:03:33,146 2. Use an 'int' return type on 'make_A' to allow an error code to be returned. 2025-09-08T08:03:33,146 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:03:33,146 Possible solutions: 2025-09-08T08:03:33,146 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:03:33,146 2. Use an 'int' return type on 'preprocess_A' to allow an error code to be returned. 2025-09-08T08:03:33,146 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:03:33,146 Possible solutions: 2025-09-08T08:03:33,146 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:03:33,146 2. Use an 'int' return type on 'Case_set_fi' to allow an error code to be returned. 2025-09-08T08:03:33,148 performance hint: wlsqm/fitter/simple.pyx:1039:26: Exception check after calling 'solve' will always require the GIL to be acquired. 2025-09-08T08:03:33,149 Possible solutions: 2025-09-08T08:03:33,149 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:03:33,149 2. Use an 'int' return type on 'solve' to allow an error code to be returned. 2025-09-08T08:03:33,154 performance hint: wlsqm/fitter/simple.pyx:1041:26: Exception check after calling 'solve' will always require the GIL to be acquired. 2025-09-08T08:03:33,154 Possible solutions: 2025-09-08T08:03:33,154 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:03:33,154 2. Use an 'int' return type on 'solve' to allow an error code to be returned. 2025-09-08T08:03:33,156 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:03:33,156 Possible solutions: 2025-09-08T08:03:33,156 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:03:33,156 2. Use an 'int' return type on 'Case_get_fi' to allow an error code to be returned. 2025-09-08T08:03:33,157 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:03:33,158 Possible solutions: 2025-09-08T08:03:33,158 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:03:33,158 2. Use an 'int' return type on 'CaseManager_del' to allow an error code to be returned. 2025-09-08T08:03:33,169 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:03:33,169 Possible solutions: 2025-09-08T08:03:33,169 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:03:33,169 2. Use an 'int' return type on 'make_c_nD' to allow an error code to be returned. 2025-09-08T08:03:33,169 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:03:33,169 Possible solutions: 2025-09-08T08:03:33,169 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:03:33,169 2. Use an 'int' return type on 'make_A' to allow an error code to be returned. 2025-09-08T08:03:33,169 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:03:33,169 Possible solutions: 2025-09-08T08:03:33,170 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:03:33,170 2. Use an 'int' return type on 'preprocess_A' to allow an error code to be returned. 2025-09-08T08:03:33,170 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:03:33,170 Possible solutions: 2025-09-08T08:03:33,170 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:03:33,170 2. Use an 'int' return type on 'Case_set_fi' to allow an error code to be returned. 2025-09-08T08:03:33,175 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:03:33,175 Possible solutions: 2025-09-08T08:03:33,175 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:03:33,175 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:33,183 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:03:33,183 Possible solutions: 2025-09-08T08:03:33,183 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:03:33,183 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:33,186 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:03:33,186 Possible solutions: 2025-09-08T08:03:33,186 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:03:33,186 2. Use an 'int' return type on 'Case_get_fi' to allow an error code to be returned. 2025-09-08T08:03:33,192 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:03:33,192 Possible solutions: 2025-09-08T08:03:33,193 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:03:33,193 2. Use an 'int' return type on 'make_c_nD' to allow an error code to be returned. 2025-09-08T08:03:33,193 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:03:33,193 Possible solutions: 2025-09-08T08:03:33,193 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:03:33,193 2. Use an 'int' return type on 'make_A' to allow an error code to be returned. 2025-09-08T08:03:33,193 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:03:33,193 Possible solutions: 2025-09-08T08:03:33,193 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:03:33,193 2. Use an 'int' return type on 'preprocess_A' to allow an error code to be returned. 2025-09-08T08:03:33,193 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:03:33,194 Possible solutions: 2025-09-08T08:03:33,194 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:03:33,194 2. Use an 'int' return type on 'Case_set_fi' to allow an error code to be returned. 2025-09-08T08:03:33,198 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:03:33,198 Possible solutions: 2025-09-08T08:03:33,198 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:03:33,198 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:33,206 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:03:33,206 Possible solutions: 2025-09-08T08:03:33,206 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:03:33,206 2. Declare any exception value explicitly for functions in pxd files. 2025-09-08T08:03:33,208 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:03:33,209 Possible solutions: 2025-09-08T08:03:33,209 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:03:33,209 2. Use an 'int' return type on 'Case_get_fi' to allow an error code to be returned. 2025-09-08T08:03:33,210 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:03:33,210 Possible solutions: 2025-09-08T08:03:33,210 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:03:33,210 2. Use an 'int' return type on 'CaseManager_del' to allow an error code to be returned. 2025-09-08T08:03:33,563 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:03:33,564 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:03:33,564 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:03:33,565 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:03:33,565 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:03:33,565 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:03:33,566 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:03:33,566 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:03:33,567 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:03:33,567 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:03:33,568 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:03:33,568 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:03:33,569 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:03:33,569 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:03:33,569 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:03:33,570 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:03:33,570 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:03:33,571 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:03:33,571 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:03:33,572 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:03:33,573 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:03:33,573 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:03:33,574 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:03:33,574 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:03:33,574 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:03:33,575 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:03:34,066 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:03:34,083 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:03:34,087 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:03:34,089 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:03:34,091 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:03:34,093 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:03:34,098 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:03:34,105 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:03:34,110 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:03:34,116 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:03:34,120 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:03:34,124 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:03:34,129 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:03:34,132 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:03:34,135 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:03:34,137 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:03:34,140 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:03:34,142 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:03:34,145 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:03:34,150 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:03:34,154 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:03:34,158 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:03:34,161 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:03:34,164 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:03:34,168 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:03:34,172 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:03:37,605 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:03:37,605 Possible solutions: 2025-09-08T08:03:37,605 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:03:37,605 2. Use an 'int' return type on 'distribute_items_c' to allow an error code to be returned. 2025-09-08T08:03:37,606 performance hint: wlsqm/utils/lapackdrivers.pyx:142:0: Exception check on 'copygeneral_c' will always require the GIL to be acquired. 2025-09-08T08:03:37,606 Possible solutions: 2025-09-08T08:03:37,606 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:03:37,606 2. Use an 'int' return type on 'copygeneral_c' to allow an error code to be returned. 2025-09-08T08:03:37,607 performance hint: wlsqm/utils/lapackdrivers.pyx:162:0: Exception check on 'copysymmu_c' will always require the GIL to be acquired. 2025-09-08T08:03:37,607 Possible solutions: 2025-09-08T08:03:37,607 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:03:37,607 2. Use an 'int' return type on 'copysymmu_c' to allow an error code to be returned. 2025-09-08T08:03:37,607 performance hint: wlsqm/utils/lapackdrivers.pyx:184:0: Exception check on 'symmetrize_c' will always require the GIL to be acquired. 2025-09-08T08:03:37,607 Possible solutions: 2025-09-08T08:03:37,608 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:03:37,608 2. Use an 'int' return type on 'symmetrize_c' to allow an error code to be returned. 2025-09-08T08:03:37,608 performance hint: wlsqm/utils/lapackdrivers.pyx:211:0: Exception check on 'msymmetrize_c' will always require the GIL to be acquired. 2025-09-08T08:03:37,608 Possible solutions: 2025-09-08T08:03:37,608 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:03:37,608 2. Use an 'int' return type on 'msymmetrize_c' to allow an error code to be returned. 2025-09-08T08:03:37,609 performance hint: wlsqm/utils/lapackdrivers.pyx:237:0: Exception check on 'msymmetrizep_c' will always require the GIL to be acquired. 2025-09-08T08:03:37,609 Possible solutions: 2025-09-08T08:03:37,609 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:03:37,609 2. Use an 'int' return type on 'msymmetrizep_c' to allow an error code to be returned. 2025-09-08T08:03:37,609 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:03:37,609 Possible solutions: 2025-09-08T08:03:37,609 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:03:37,609 2. Use an 'int' return type on 'init_scaling_c' to allow an error code to be returned. 2025-09-08T08:03:37,610 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:03:37,610 Possible solutions: 2025-09-08T08:03:37,610 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:03:37,610 2. Use an 'int' return type on 'apply_scaling_c' to allow an error code to be returned. 2025-09-08T08:03:37,611 performance hint: wlsqm/utils/lapackdrivers.pxd:69:26: No exception value declared for 'rescale_columns_c' in pxd file. 2025-09-08T08:03:37,612 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:03:37,612 Suggest adding an explicit exception value. 2025-09-08T08:03:37,612 performance hint: wlsqm/utils/lapackdrivers.pxd:70:23: No exception value declared for 'rescale_rows_c' in pxd file. 2025-09-08T08:03:37,612 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:03:37,613 Suggest adding an explicit exception value. 2025-09-08T08:03:37,613 performance hint: wlsqm/utils/lapackdrivers.pxd:71:26: No exception value declared for 'rescale_twopass_c' in pxd file. 2025-09-08T08:03:37,613 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:03:37,613 Suggest adding an explicit exception value. 2025-09-08T08:03:37,614 performance hint: wlsqm/utils/lapackdrivers.pxd:72:25: No exception value declared for 'rescale_dgeequ_c' in pxd file. 2025-09-08T08:03:37,614 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:03:37,614 Suggest adding an explicit exception value. 2025-09-08T08:03:37,615 performance hint: wlsqm/utils/lapackdrivers.pxd:75:27: No exception value declared for 'rescale_ruiz2001_c' in pxd file. 2025-09-08T08:03:37,615 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:03:37,615 Suggest adding an explicit exception value. 2025-09-08T08:03:37,616 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:03:37,616 Possible solutions: 2025-09-08T08:03:37,616 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:03:37,616 2. Use an 'int' return type on 'basic_scale_up_rows' to allow an error code to be returned. 2025-09-08T08:03:37,616 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:03:37,616 Possible solutions: 2025-09-08T08:03:37,616 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:03:37,616 2. Use an 'int' return type on 'basic_scale_up_cols' to allow an error code to be returned. 2025-09-08T08:03:37,617 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:03:37,617 Possible solutions: 2025-09-08T08:03:37,617 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:03:37,617 2. Use an 'int' return type on 'basic_scale_down_rows' to allow an error code to be returned. 2025-09-08T08:03:37,617 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:03:37,617 Possible solutions: 2025-09-08T08:03:37,617 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:03:37,617 2. Use an 'int' return type on 'basic_scale_down_cols' to allow an error code to be returned. 2025-09-08T08:03:37,618 performance hint: wlsqm/utils/lapackdrivers.pxd:76:25: No exception value declared for 'rescale_scalgm_c' in pxd file. 2025-09-08T08:03:37,618 Users cimporting this function and calling it without the gil will always require an exception check. 2025-09-08T08:03:37,618 Suggest adding an explicit exception value. 2025-09-08T08:03:39,193 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:03:39,193 Possible solutions: 2025-09-08T08:03:39,193 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:03:39,193 2. Use an 'int' return type on 'copygeneral_c' to allow an error code to be returned. 2025-09-08T08:03:39,197 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:03:39,197 Possible solutions: 2025-09-08T08:03:39,197 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:03:39,197 2. Use an 'int' return type on 'copysymmu_c' to allow an error code to be returned. 2025-09-08T08:03:39,201 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:03:39,201 Possible solutions: 2025-09-08T08:03:39,201 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:03:39,202 2. Use an 'int' return type on 'symmetrize_c' to allow an error code to be returned. 2025-09-08T08:03:39,205 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:03:39,206 Possible solutions: 2025-09-08T08:03:39,206 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:03:39,206 2. Use an 'int' return type on 'msymmetrize_c' to allow an error code to be returned. 2025-09-08T08:03:39,210 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:03:39,211 Possible solutions: 2025-09-08T08:03:39,211 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:03:39,211 2. Use an 'int' return type on 'msymmetrizep_c' to allow an error code to be returned. 2025-09-08T08:03:39,225 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:03:39,226 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:03:39,226 Possible solutions: 2025-09-08T08:03:39,226 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:03:39,226 2. Use an 'int' return type on 'apply_scaling_c' to allow an error code to be returned. 2025-09-08T08:03:39,230 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:03:39,230 Possible solutions: 2025-09-08T08:03:39,230 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:03:39,230 2. Use an 'int' return type on 'init_scaling_c' to allow an error code to be returned. 2025-09-08T08:03:39,234 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:03:39,235 Possible solutions: 2025-09-08T08:03:39,235 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:03:39,235 2. Use an 'int' return type on 'init_scaling_c' to allow an error code to be returned. 2025-09-08T08:03:39,239 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:03:39,239 Possible solutions: 2025-09-08T08:03:39,239 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:03:39,239 2. Use an 'int' return type on 'init_scaling_c' to allow an error code to be returned. 2025-09-08T08:03:39,248 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:03:39,248 Possible solutions: 2025-09-08T08:03:39,248 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:03:39,248 2. Use an 'int' return type on 'init_scaling_c' to allow an error code to be returned. 2025-09-08T08:03:39,249 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:03:39,249 Possible solutions: 2025-09-08T08:03:39,249 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:03:39,249 2. Use an 'int' return type on 'init_scaling_c' to allow an error code to be returned. 2025-09-08T08:03:39,249 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:03:39,249 Possible solutions: 2025-09-08T08:03:39,249 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:03:39,249 2. Use an 'int' return type on 'init_scaling_c' to allow an error code to be returned. 2025-09-08T08:03:39,273 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:03:39,273 Possible solutions: 2025-09-08T08:03:39,273 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:03:39,273 2. Use an 'int' return type on 'init_scaling_c' to allow an error code to be returned. 2025-09-08T08:03:39,273 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:03:39,273 Possible solutions: 2025-09-08T08:03:39,273 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:03:39,273 2. Use an 'int' return type on 'init_scaling_c' to allow an error code to be returned. 2025-09-08T08:03:39,274 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:03:39,274 Possible solutions: 2025-09-08T08:03:39,274 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:03:39,274 2. Use an 'int' return type on 'init_scaling_c' to allow an error code to be returned. 2025-09-08T08:03:39,274 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:03:39,274 Possible solutions: 2025-09-08T08:03:39,274 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:03:39,274 2. Use an 'int' return type on 'basic_scale_up_rows' to allow an error code to be returned. 2025-09-08T08:03:39,274 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:03:39,274 Possible solutions: 2025-09-08T08:03:39,275 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:03:39,275 2. Use an 'int' return type on 'basic_scale_up_cols' to allow an error code to be returned. 2025-09-08T08:03:39,275 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:03:39,275 Possible solutions: 2025-09-08T08:03:39,275 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:03:39,275 2. Use an 'int' return type on 'basic_scale_up_cols' to allow an error code to be returned. 2025-09-08T08:03:39,275 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:03:39,275 Possible solutions: 2025-09-08T08:03:39,275 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:03:39,275 2. Use an 'int' return type on 'basic_scale_up_rows' to allow an error code to be returned. 2025-09-08T08:03:39,276 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:03:39,276 Possible solutions: 2025-09-08T08:03:39,276 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:03:39,277 2. Use an 'int' return type on 'basic_scale_down_rows' to allow an error code to be returned. 2025-09-08T08:03:39,277 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:03:39,277 Possible solutions: 2025-09-08T08:03:39,277 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:03:39,277 2. Use an 'int' return type on 'basic_scale_down_cols' to allow an error code to be returned. 2025-09-08T08:03:39,277 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:03:39,277 Possible solutions: 2025-09-08T08:03:39,277 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:03:39,277 2. Use an 'int' return type on 'basic_scale_down_cols' to allow an error code to be returned. 2025-09-08T08:03:39,277 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:03:39,278 Possible solutions: 2025-09-08T08:03:39,278 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:03:39,278 2. Use an 'int' return type on 'basic_scale_down_rows' to allow an error code to be returned. 2025-09-08T08:03:39,311 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:03:39,312 Possible solutions: 2025-09-08T08:03:39,312 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:03:39,312 2. Use an 'int' return type on 'distribute_items_c' to allow an error code to be returned. 2025-09-08T08:03:39,313 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:03:39,314 Possible solutions: 2025-09-08T08:03:39,314 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:03:39,314 2. Use an 'int' return type on 'copysymmu_c' to allow an error code to be returned. 2025-09-08T08:03:39,376 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:03:39,376 Possible solutions: 2025-09-08T08:03:39,376 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:03:39,376 2. Use an 'int' return type on 'distribute_items_c' to allow an error code to be returned. 2025-09-08T08:03:39,377 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:03:39,377 Possible solutions: 2025-09-08T08:03:39,377 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:03:39,377 2. Use an 'int' return type on 'copygeneral_c' to allow an error code to be returned. 2025-09-08T08:03:40,025 build configuration selected: optimized 2025-09-08T08:03:40,026 Compiling wlsqm/utils/lapackdrivers.pyx because it changed. 2025-09-08T08:03:40,026 Compiling wlsqm/utils/ptrwrap.pyx because it changed. 2025-09-08T08:03:40,026 Compiling wlsqm/fitter/defs.pyx because it changed. 2025-09-08T08:03:40,026 Compiling wlsqm/fitter/infra.pyx because it changed. 2025-09-08T08:03:40,026 Compiling wlsqm/fitter/impl.pyx because it changed. 2025-09-08T08:03:40,026 Compiling wlsqm/fitter/polyeval.pyx because it changed. 2025-09-08T08:03:40,026 Compiling wlsqm/fitter/interp.pyx because it changed. 2025-09-08T08:03:40,026 Compiling wlsqm/fitter/simple.pyx because it changed. 2025-09-08T08:03:40,026 Compiling wlsqm/fitter/expert.pyx because it changed. 2025-09-08T08:03:40,026 [1/9] Cythonizing wlsqm/fitter/defs.pyx 2025-09-08T08:03:40,026 [2/9] Cythonizing wlsqm/fitter/expert.pyx 2025-09-08T08:03:40,027 [3/9] Cythonizing wlsqm/fitter/impl.pyx 2025-09-08T08:03:40,027 [4/9] Cythonizing wlsqm/fitter/infra.pyx 2025-09-08T08:03:40,027 [5/9] Cythonizing wlsqm/fitter/interp.pyx 2025-09-08T08:03:40,027 [6/9] Cythonizing wlsqm/fitter/polyeval.pyx 2025-09-08T08:03:40,027 [7/9] Cythonizing wlsqm/fitter/simple.pyx 2025-09-08T08:03:40,027 [8/9] Cythonizing wlsqm/utils/lapackdrivers.pyx 2025-09-08T08:03:40,027 [9/9] Cythonizing wlsqm/utils/ptrwrap.pyx 2025-09-08T08:03:40,204 /usr/local/lib/python3.13/dist-packages/setuptools/__init__.py:92: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated. 2025-09-08T08:03:40,204 !! 2025-09-08T08:03:40,204 ******************************************************************************** 2025-09-08T08:03:40,204 Requirements should be satisfied by a PEP 517 installer. 2025-09-08T08:03:40,204 If you are using pip, you can try `pip install --use-pep517`. 2025-09-08T08:03:40,205 By 2025-Oct-31, you need to update your project and remove deprecated calls 2025-09-08T08:03:40,205 or your builds will no longer be supported. 2025-09-08T08:03:40,205 ******************************************************************************** 2025-09-08T08:03:40,205 !! 2025-09-08T08:03:40,205 dist.fetch_build_eggs(dist.setup_requires) 2025-09-08T08:03:40,578 /usr/local/lib/python3.13/dist-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated. 2025-09-08T08:03:40,578 !! 2025-09-08T08:03:40,578 ******************************************************************************** 2025-09-08T08:03:40,578 Please consider removing the following classifiers in favor of a SPDX license expression: 2025-09-08T08:03:40,579 License :: OSI Approved :: BSD License 2025-09-08T08:03:40,579 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. 2025-09-08T08:03:40,579 ******************************************************************************** 2025-09-08T08:03:40,579 !! 2025-09-08T08:03:40,579 self._finalize_license_expression() 2025-09-08T08:03:40,654 running egg_info 2025-09-08T08:03:40,729 creating /tmp/pip-pip-egg-info-f79rn4g9/wlsqm.egg-info 2025-09-08T08:03:40,729 writing /tmp/pip-pip-egg-info-f79rn4g9/wlsqm.egg-info/PKG-INFO 2025-09-08T08:03:40,730 writing dependency_links to /tmp/pip-pip-egg-info-f79rn4g9/wlsqm.egg-info/dependency_links.txt 2025-09-08T08:03:40,731 writing requirements to /tmp/pip-pip-egg-info-f79rn4g9/wlsqm.egg-info/requires.txt 2025-09-08T08:03:40,731 writing top-level names to /tmp/pip-pip-egg-info-f79rn4g9/wlsqm.egg-info/top_level.txt 2025-09-08T08:03:40,732 writing manifest file '/tmp/pip-pip-egg-info-f79rn4g9/wlsqm.egg-info/SOURCES.txt' 2025-09-08T08:03:41,036 reading manifest file '/tmp/pip-pip-egg-info-f79rn4g9/wlsqm.egg-info/SOURCES.txt' 2025-09-08T08:03:41,036 adding license file 'LICENSE.md' 2025-09-08T08:03:41,040 writing manifest file '/tmp/pip-pip-egg-info-f79rn4g9/wlsqm.egg-info/SOURCES.txt' 2025-09-08T08:03:41,926 Preparing metadata (setup.py): finished with status 'done' 2025-09-08T08:03:41,931 Source in /tmp/pip-wheel-sazcx695/wlsqm_f40c948c21cb4ca198e92d7d432711ce has version 0.1.5, which satisfies requirement wlsqm==0.1.5 from https://files.pythonhosted.org/packages/0f/37/d6e09c5fa4d2437dd239681b483a1a2c28f52673a2e6c80c0865420cf907/wlsqm-0.1.5.tar.gz 2025-09-08T08:03:41,932 Removed wlsqm==0.1.5 from https://files.pythonhosted.org/packages/0f/37/d6e09c5fa4d2437dd239681b483a1a2c28f52673a2e6c80c0865420cf907/wlsqm-0.1.5.tar.gz from build tracker '/tmp/pip-build-tracker-68yma6z2' 2025-09-08T08:03:41,935 Created temporary directory: /tmp/pip-unpack-w86aqu5c 2025-09-08T08:03:41,936 Created temporary directory: /tmp/pip-unpack-hfcaj86f 2025-09-08T08:03:41,936 Building wheels for collected packages: wlsqm 2025-09-08T08:03:41,937 Created temporary directory: /tmp/pip-wheel-9nz2nhxo 2025-09-08T08:03:41,938 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:03:41,939 Building wheel for wlsqm (setup.py): started 2025-09-08T08:03:41,939 Destination directory: /tmp/pip-wheel-9nz2nhxo 2025-09-08T08:03:41,939 Running command python setup.py bdist_wheel 2025-09-08T08:03:42,651 build configuration selected: optimized 2025-09-08T08:03:42,652 /tmp/pip-wheel-sazcx695/wlsqm_f40c948c21cb4ca198e92d7d432711ce/setup.py:148: DeprecationWarning: Attribute s is deprecated and will be removed in Python 3.14; use value instead 2025-09-08T08:03:42,652 version = ast.parse(line).body[0].value.s 2025-09-08T08:03:43,469 /usr/local/lib/python3.13/dist-packages/setuptools/__init__.py:92: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated. 2025-09-08T08:03:43,469 !! 2025-09-08T08:03:43,469 ******************************************************************************** 2025-09-08T08:03:43,469 Requirements should be satisfied by a PEP 517 installer. 2025-09-08T08:03:43,469 If you are using pip, you can try `pip install --use-pep517`. 2025-09-08T08:03:43,469 By 2025-Oct-31, you need to update your project and remove deprecated calls 2025-09-08T08:03:43,469 or your builds will no longer be supported. 2025-09-08T08:03:43,470 ******************************************************************************** 2025-09-08T08:03:43,470 !! 2025-09-08T08:03:43,470 dist.fetch_build_eggs(dist.setup_requires) 2025-09-08T08:03:43,834 /usr/local/lib/python3.13/dist-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated. 2025-09-08T08:03:43,834 !! 2025-09-08T08:03:43,834 ******************************************************************************** 2025-09-08T08:03:43,835 Please consider removing the following classifiers in favor of a SPDX license expression: 2025-09-08T08:03:43,835 License :: OSI Approved :: BSD License 2025-09-08T08:03:43,835 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. 2025-09-08T08:03:43,835 ******************************************************************************** 2025-09-08T08:03:43,835 !! 2025-09-08T08:03:43,835 self._finalize_license_expression() 2025-09-08T08:03:43,836 running bdist_wheel 2025-09-08T08:03:44,203 running build 2025-09-08T08:03:44,203 running build_py 2025-09-08T08:03:44,282 creating build/lib.linux-armv7l-cpython-313/wlsqm 2025-09-08T08:03:44,282 copying wlsqm/__init__.py -> build/lib.linux-armv7l-cpython-313/wlsqm 2025-09-08T08:03:44,283 creating build/lib.linux-armv7l-cpython-313/wlsqm/utils 2025-09-08T08:03:44,283 copying wlsqm/utils/__init__.py -> build/lib.linux-armv7l-cpython-313/wlsqm/utils 2025-09-08T08:03:44,284 creating build/lib.linux-armv7l-cpython-313/wlsqm/fitter 2025-09-08T08:03:44,284 copying wlsqm/fitter/__init__.py -> build/lib.linux-armv7l-cpython-313/wlsqm/fitter 2025-09-08T08:03:44,288 copying wlsqm/utils/ptrwrap.pxd -> build/lib.linux-armv7l-cpython-313/wlsqm/utils 2025-09-08T08:03:44,288 copying wlsqm/utils/lapackdrivers.pxd -> build/lib.linux-armv7l-cpython-313/wlsqm/utils 2025-09-08T08:03:44,289 copying wlsqm/utils/lapackdrivers.pyx -> build/lib.linux-armv7l-cpython-313/wlsqm/utils 2025-09-08T08:03:44,290 copying wlsqm/utils/ptrwrap.pyx -> build/lib.linux-armv7l-cpython-313/wlsqm/utils 2025-09-08T08:03:44,290 copying wlsqm/fitter/interp.pxd -> build/lib.linux-armv7l-cpython-313/wlsqm/fitter 2025-09-08T08:03:44,291 copying wlsqm/fitter/simple.pxd -> build/lib.linux-armv7l-cpython-313/wlsqm/fitter 2025-09-08T08:03:44,291 copying wlsqm/fitter/defs.pxd -> build/lib.linux-armv7l-cpython-313/wlsqm/fitter 2025-09-08T08:03:44,292 copying wlsqm/fitter/infra.pxd -> build/lib.linux-armv7l-cpython-313/wlsqm/fitter 2025-09-08T08:03:44,293 copying wlsqm/fitter/impl.pxd -> build/lib.linux-armv7l-cpython-313/wlsqm/fitter 2025-09-08T08:03:44,293 copying wlsqm/fitter/polyeval.pxd -> build/lib.linux-armv7l-cpython-313/wlsqm/fitter 2025-09-08T08:03:44,294 copying wlsqm/fitter/expert.pyx -> build/lib.linux-armv7l-cpython-313/wlsqm/fitter 2025-09-08T08:03:44,294 copying wlsqm/fitter/infra.pyx -> build/lib.linux-armv7l-cpython-313/wlsqm/fitter 2025-09-08T08:03:44,295 copying wlsqm/fitter/interp.pyx -> build/lib.linux-armv7l-cpython-313/wlsqm/fitter 2025-09-08T08:03:44,296 copying wlsqm/fitter/impl.pyx -> build/lib.linux-armv7l-cpython-313/wlsqm/fitter 2025-09-08T08:03:44,296 copying wlsqm/fitter/simple.pyx -> build/lib.linux-armv7l-cpython-313/wlsqm/fitter 2025-09-08T08:03:44,297 copying wlsqm/fitter/defs.pyx -> build/lib.linux-armv7l-cpython-313/wlsqm/fitter 2025-09-08T08:03:44,298 copying wlsqm/fitter/polyeval.pyx -> build/lib.linux-armv7l-cpython-313/wlsqm/fitter 2025-09-08T08:03:44,299 running build_ext 2025-09-08T08:03:44,307 building 'wlsqm.utils.lapackdrivers' extension 2025-09-08T08:03:44,308 creating build/temp.linux-armv7l-cpython-313/wlsqm/utils 2025-09-08T08:03:44,308 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:03:44,318 arm-linux-gnueabihf-gcc: error: unrecognized command-line option ‘-msse’ 2025-09-08T08:03:44,320 arm-linux-gnueabihf-gcc: error: unrecognized command-line option ‘-msse2’ 2025-09-08T08:03:44,320 arm-linux-gnueabihf-gcc: error: unrecognized command-line option ‘-mfma’ 2025-09-08T08:03:44,338 arm-linux-gnueabihf-gcc: error: unrecognized command-line option ‘-mfpmath=sse’ 2025-09-08T08:03:44,340 error: command '/usr/bin/arm-linux-gnueabihf-gcc' failed with exit code 1 2025-09-08T08:03:44,490 ERROR: python setup.py bdist_wheel exited with 1 2025-09-08T08:03:44,502 [bold magenta]full command[/]: [blue]/usr/bin/python3 -u -c ' 2025-09-08T08:03:44,502 exec(compile('"'"''"'"''"'"' 2025-09-08T08:03:44,502 # This is -- a caller that pip uses to run setup.py 2025-09-08T08:03:44,502 # 2025-09-08T08:03:44,502 # - It imports setuptools before invoking setup.py, to enable projects that directly 2025-09-08T08:03:44,502 # import from `distutils.core` to work with newer packaging standards. 2025-09-08T08:03:44,502 # - It provides a clear error message when setuptools is not installed. 2025-09-08T08:03:44,502 # - It sets `sys.argv[0]` to the underlying `setup.py`, when invoking `setup.py` so 2025-09-08T08:03:44,502 # setuptools doesn'"'"'t think the script is `-c`. This avoids the following warning: 2025-09-08T08:03:44,502 # manifest_maker: standard file '"'"'-c'"'"' not found". 2025-09-08T08:03:44,502 # - It generates a shim setup.py, for handling setup.cfg-only projects. 2025-09-08T08:03:44,502 import os, sys, tokenize, traceback 2025-09-08T08:03:44,502 2025-09-08T08:03:44,502 try: 2025-09-08T08:03:44,502 import setuptools 2025-09-08T08:03:44,502 except ImportError: 2025-09-08T08:03:44,502 print( 2025-09-08T08:03:44,502 "ERROR: Can not execute `setup.py` since setuptools failed to import in " 2025-09-08T08:03:44,502 "the build environment with exception:", 2025-09-08T08:03:44,502 file=sys.stderr, 2025-09-08T08:03:44,502 ) 2025-09-08T08:03:44,502 traceback.print_exc() 2025-09-08T08:03:44,502 sys.exit(1) 2025-09-08T08:03:44,502 2025-09-08T08:03:44,502 __file__ = %r 2025-09-08T08:03:44,502 sys.argv[0] = __file__ 2025-09-08T08:03:44,502 2025-09-08T08:03:44,502 if os.path.exists(__file__): 2025-09-08T08:03:44,502 filename = __file__ 2025-09-08T08:03:44,502 with tokenize.open(__file__) as f: 2025-09-08T08:03:44,502 setup_py_code = f.read() 2025-09-08T08:03:44,502 else: 2025-09-08T08:03:44,502 filename = "" 2025-09-08T08:03:44,502 setup_py_code = "from setuptools import setup; setup()" 2025-09-08T08:03:44,502 2025-09-08T08:03:44,502 exec(compile(setup_py_code, filename, "exec")) 2025-09-08T08:03:44,502 '"'"''"'"''"'"' % ('"'"'/tmp/pip-wheel-sazcx695/wlsqm_f40c948c21cb4ca198e92d7d432711ce/setup.py'"'"',), "", "exec"))' bdist_wheel -d /tmp/pip-wheel-9nz2nhxo[/] 2025-09-08T08:03:44,502 [bold magenta]cwd[/]: /tmp/pip-wheel-sazcx695/wlsqm_f40c948c21cb4ca198e92d7d432711ce/ 2025-09-08T08:03:44,502 Building wheel for wlsqm (setup.py): finished with status 'error' 2025-09-08T08:03:44,503 ERROR: Failed building wheel for wlsqm 2025-09-08T08:03:44,503 Running setup.py clean for wlsqm 2025-09-08T08:03:44,504 Running command python setup.py clean 2025-09-08T08:03:45,194 build configuration selected: optimized 2025-09-08T08:03:45,195 /tmp/pip-wheel-sazcx695/wlsqm_f40c948c21cb4ca198e92d7d432711ce/setup.py:148: DeprecationWarning: Attribute s is deprecated and will be removed in Python 3.14; use value instead 2025-09-08T08:03:45,195 version = ast.parse(line).body[0].value.s 2025-09-08T08:03:46,018 /usr/local/lib/python3.13/dist-packages/setuptools/__init__.py:92: _DeprecatedInstaller: setuptools.installer and fetch_build_eggs are deprecated. 2025-09-08T08:03:46,018 !! 2025-09-08T08:03:46,018 ******************************************************************************** 2025-09-08T08:03:46,018 Requirements should be satisfied by a PEP 517 installer. 2025-09-08T08:03:46,018 If you are using pip, you can try `pip install --use-pep517`. 2025-09-08T08:03:46,019 By 2025-Oct-31, you need to update your project and remove deprecated calls 2025-09-08T08:03:46,019 or your builds will no longer be supported. 2025-09-08T08:03:46,019 ******************************************************************************** 2025-09-08T08:03:46,019 !! 2025-09-08T08:03:46,019 dist.fetch_build_eggs(dist.setup_requires) 2025-09-08T08:03:46,378 /usr/local/lib/python3.13/dist-packages/setuptools/dist.py:759: SetuptoolsDeprecationWarning: License classifiers are deprecated. 2025-09-08T08:03:46,379 !! 2025-09-08T08:03:46,379 ******************************************************************************** 2025-09-08T08:03:46,379 Please consider removing the following classifiers in favor of a SPDX license expression: 2025-09-08T08:03:46,379 License :: OSI Approved :: BSD License 2025-09-08T08:03:46,379 See https://packaging.python.org/en/latest/guides/writing-pyproject-toml/#license for details. 2025-09-08T08:03:46,379 ******************************************************************************** 2025-09-08T08:03:46,380 !! 2025-09-08T08:03:46,380 self._finalize_license_expression() 2025-09-08T08:03:46,453 running clean 2025-09-08T08:03:46,601 removing 'build/temp.linux-armv7l-cpython-313' (and everything under it) 2025-09-08T08:03:46,601 removing 'build/lib.linux-armv7l-cpython-313' (and everything under it) 2025-09-08T08:03:46,602 'build/bdist.linux-armv7l' does not exist -- can't clean it 2025-09-08T08:03:46,602 'build/scripts-3.13' does not exist -- can't clean it 2025-09-08T08:03:46,602 removing 'build' 2025-09-08T08:03:46,752 Failed to build wlsqm 2025-09-08T08:03:46,752 ERROR: Failed to build one or more wheels 2025-09-08T08:03:46,753 Exception information: 2025-09-08T08:03:46,753 Traceback (most recent call last): 2025-09-08T08:03:46,753 File "/usr/lib/python3/dist-packages/pip/_internal/cli/base_command.py", line 105, in _run_wrapper 2025-09-08T08:03:46,753 status = _inner_run() 2025-09-08T08:03:46,753 File "/usr/lib/python3/dist-packages/pip/_internal/cli/base_command.py", line 96, in _inner_run 2025-09-08T08:03:46,753 return self.run(options, args) 2025-09-08T08:03:46,753 ~~~~~~~~^^^^^^^^^^^^^^^ 2025-09-08T08:03:46,753 File "/usr/lib/python3/dist-packages/pip/_internal/cli/req_command.py", line 68, in wrapper 2025-09-08T08:03:46,753 return func(self, options, args) 2025-09-08T08:03:46,753 File "/usr/lib/python3/dist-packages/pip/_internal/commands/wheel.py", line 180, in run 2025-09-08T08:03:46,753 raise CommandError("Failed to build one or more wheels") 2025-09-08T08:03:46,753 pip._internal.exceptions.CommandError: Failed to build one or more wheels 2025-09-08T08:03:46,757 Removed build tracker: '/tmp/pip-build-tracker-68yma6z2'