From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from m0.truegem.net (m0.truegem.net [69.55.228.47]) by sourceware.org (Postfix) with ESMTPS id 8114E3858D28 for ; Tue, 8 Nov 2022 07:07:06 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 8114E3858D28 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=maxrnd.com Authentication-Results: sourceware.org; spf=none smtp.mailfrom=maxrnd.com Received: (from daemon@localhost) by m0.truegem.net (8.12.11/8.12.11) id 2A8772sU012849 for ; Mon, 7 Nov 2022 23:07:02 -0800 (PST) (envelope-from mark@maxrnd.com) Received: from 162-235-43-67.lightspeed.irvnca.sbcglobal.net(162.235.43.67), claiming to be "[192.168.1.100]" via SMTP by m0.truegem.net, id smtpdhErgXS; Mon Nov 7 23:07:02 2022 X-Mozilla-News-Host: news://news.gmane.org:119 To: cygwin-apps@cygwin.com From: Mark Geisert Subject: Concerning Python patch 3.6.12-socketmodule.patch Message-ID: <34544e65-985f-c3a8-3f8d-e9f2550f2fcd@maxrnd.com> Date: Mon, 7 Nov 2022 23:07:02 -0800 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Firefox/52.0 SeaMonkey/2.49.4 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,KAM_DMARC_STATUS,KAM_LAZY_DOMAIN_SECURITY,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hi Marco, Recently there's been a complaint about that patch on the Cygwin mailing list. The patch was meant to allow same-machine communication between Cygwin Python programs via an AF_UNIX socket. The patch works because both ends of the connection are Python programs that have the patch. The problem reported by the user is that when a Python program attempts to communicate with ssh-agent, the connection freezes. This is due to the above patch being applied only to the Python end (of course). Given that we need the patch for Python build tests, could you handle an environment variable setting to choose the behavior of the patch? In other words. a revised patch would consult an environment variable PYTHON_NET_DISABLE_CREDENTIALS to decide whether to do what the current patch does. I guess the pythonXX.cygport file would have to define that env var. Does that sound like a workable scheme to you? Thanks, ..mark