Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sHThH-0080ur-BY for pgsql-hackers@arkaria.postgresql.org; Wed, 12 Jun 2024 19:31:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sHThF-005dpU-3i for pgsql-hackers@arkaria.postgresql.org; Wed, 12 Jun 2024 19:31:49 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sHThE-005dog-Pw for pgsql-hackers@lists.postgresql.org; Wed, 12 Jun 2024 19:31:49 +0000 Received: from mail-qv1-xf30.google.com ([2607:f8b0:4864:20::f30]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sHThD-0010Lj-1Z for pgsql-hackers@postgresql.org; Wed, 12 Jun 2024 19:31:48 +0000 Received: by mail-qv1-xf30.google.com with SMTP id 6a1803df08f44-6b0682d1b12so1301806d6.0 for ; Wed, 12 Jun 2024 12:31:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; t=1718220706; x=1718825506; darn=postgresql.org; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=sYjCKMQjdMy/OARvOf6RhUvH/2yYcnQmwGOPVAPe81w=; b=aVW4UKPeWUy9BynNAJxnoTC4ktiV/YGRWqyXrupu3bhiTwKdAniQjVzK5ess7ouol1 MZSnSVIukg3aR2NGINfPso8PJ1LBAOoeTmrHVZqoaYL4VMk+BqBkT/M+WXZPL0CiUkHN qi0/n6ewDaToOFpp+rs0A5hh0SSLHUCwMima93inhrMwaE7zM/dGH5qip/4kt8z/Kl8r PikbO7CreWyGhcmhvHgBur6w5qHNPDweOyZpRz9WSmqPCYnf52GiGuJ0J3/3xocgYYsB E0Wa+NMmSGNgsOIGO3UAtHociRamPDqjPARNuDT13FEIUhYaxW7HVbKKLSwEav7QiLcJ DsNw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1718220706; x=1718825506; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=sYjCKMQjdMy/OARvOf6RhUvH/2yYcnQmwGOPVAPe81w=; b=g1KyxgH8HXExUQvPbtgujg4jUjiAXABm0YUWPUSt+gq56E6pFI3qpo6TXljm3adN3D NhlIlsZvzRjc3l5D7naQo7Vb8wbU1J7R4hqy0juLKS6b6EHNTBzOY8/rvoPdCW2f4gjT qqeRQZbgGXkcrU9b7ek+XcRacf2dpb9t8GjkhlFbJwIGeyEgWA93G6drTIkASK8NuCZc CuQGuRJVLjuSTHhHU+Lh/1CW2m7tybwfV7vGh5MXQdkPxq6W2lDuf+kUX+5y5yZPAvGU r0tH04ieuDmbywQZK12bbBfn8FTgg+5xLduHLN1Gd4E8MW5iqgbmJ3VLJ7XhukiEyzaK TtAw== X-Gm-Message-State: AOJu0YxjoCLl/QysXB5IoGyQyepk069sL2yz8x2BwFV/52jPnhs8zz08 XwmdVrM695/qvZ8qc57rqNQ1PMKUfpAnT25Tzb7ao0GDpQayJ2eHROQtBsq+c+7Ydxjc7EDfMfr ATKqrm/woRqIs95l/hS6YsMGJY3ZgsA+JqtQS X-Google-Smtp-Source: AGHT+IEhhuJ5oedqWZFgJAZQRzMfPRpQW2sHTsNUeh33tPxIdw+HED8FwLfY7LI8LPyygtxpmfdyZmiaNYvxMpIp3K4= X-Received: by 2002:a05:6214:469a:b0:6b0:71ad:db7d with SMTP id 6a1803df08f44-6b1a76fcb2amr32337786d6.57.1718220706383; Wed, 12 Jun 2024 12:31:46 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Jacob Champion Date: Wed, 12 Jun 2024 12:31:35 -0700 Message-ID: Subject: Re: RFC: adding pytest as a supported test framework To: Alexander Korotkov Cc: PostgreSQL Hackers Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, Jun 12, 2024 at 4:48=E2=80=AFAM Alexander Korotkov wrote: > Generally, testgres was initially designed as Python analogue of what > we have in src/test/perl/PostgreSQL/Test. In particular its > testgres.PostgresNode is analogue of PostgreSQL::Test::Cluster. It > comes under PostgreSQL License. So, I wonder if we could revise it > and fetch most part of it into our source tree. Okay. If there's wide interest in a port of PostgreSQL::Test::Cluster, that might be something to take a look at. (Since I'm focused on testing things that the current Perl suite can't do at all, I would probably not be the first to volunteer.) --Jacob