From 3386658575333b03f38a6e91c9a6e77e9c91e3ba Mon Sep 17 00:00:00 2001 From: Chris Burr Date: Fri, 28 Aug 2026 12:02:36 +0200 Subject: [PATCH] fix: Unpin mysqlclient and require >=2.2.0 The <2.1 constraint was added because mysqlclient 2.1 removed the module-level MySQLdb.escape_string. DIRAC stopped using it in v8.0.81, v9.0.23 and v9.1.13, so the constraint is no longer needed. Require >=2.2.0 so that cursor.mogrify is available, and because the diracgrid channel only carries 2.0.3, which would otherwise win over conda-forge on channel priority. This also removes the need to keep rebuilding 2.0.3 for each new Python version, as conda-forge only has 2.0.3 builds up to py311. Closes #190 --- construct.yaml | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/construct.yaml b/construct.yaml index 56d8bf5..1656483 100644 --- a/construct.yaml +++ b/construct.yaml @@ -53,8 +53,7 @@ specs: - elasticsearch <7.14 - elasticsearch-dsl - numpy <2 # elasticsearch<7.14 needs numpy 1.x, remove this constraint when elasticsearch is removed - # Earlier versions of mysqlclient were build with older MySQL versions - - mysqlclient >=2.0.3,<2.1 + - mysqlclient >=2.2.0 - sqlalchemy >=1.4.36 - stomp.py >8 # Middleware