From aad1276751fdc87c1d766c7af4a194b33b91df32 Mon Sep 17 00:00:00 2001 From: Ryan Scott Date: Tue, 9 May 2023 13:14:10 -0400 Subject: [PATCH] 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 `argo` submodule to bring in the changes from https://github.com/GaloisInc/argo/pull/197, which applies similar changes. --- cryptol-remote-api/python/pyproject.toml | 3 ++- deps/argo | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git a/cryptol-remote-api/python/pyproject.toml b/cryptol-remote-api/python/pyproject.toml index 71748b28b..bd1acd880 100644 --- a/cryptol-remote-api/python/pyproject.toml +++ b/cryptol-remote-api/python/pyproject.toml @@ -23,4 +23,5 @@ typing-extensions = "^4.1.1" 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" diff --git a/deps/argo b/deps/argo index a2a6e7f54..ef4cc2935 160000 --- a/deps/argo +++ b/deps/argo @@ -1 +1 @@ -Subproject commit a2a6e7f54551f20549dc5f48881f5b35d6f8c155 +Subproject commit ef4cc29359931789957853e79ee5c0e3a03d5844