Python: Use poetry.core.masonry.api as build-backend

This is motivated by a desire to switch away from `setuptools`, which has some unfortunate interactions with static analysis tools. This also bumps the following submodules, which apply similar changes: * `argo` submodule: GaloisInc/argo#197 * `cryptol` submodule: GaloisInc/cryptol#1519
GaloisInc · May 9, 2023 · ff35274 · ff35274
1 parent 9e78344
commit ff35274
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 3 deletions.
diff --git a/deps/argo b/deps/argo
diff --git a/deps/cryptol b/deps/cryptol
diff --git a/saw-remote-api/python/pyproject.toml b/saw-remote-api/python/pyproject.toml
@@ -21,4 +21,5 @@ argo-client = "0.0.11"
 mypy = "^0.991"
 
 [build-system]
-requires = ["poetry>=1.1.4", "setuptools>=40.8.0"]
+requires = ["poetry-core>=1.0.0"]
+build-backend = "poetry.core.masonry.api"