From: Mark Geisert <mark@maxrnd.com>
To: Cygwin-Apps <cygwin-apps@cygwin.com>
Subject: Concerning Python patch 3.6.12-socketmodule.patch -- ping Marco
Date: Fri, 10 Feb 2023 22:41:35 -0800 [thread overview]
Message-ID: <7b6be8fa-1a85-52b8-ce23-677f243f67d0@maxrnd.com> (raw)
In-Reply-To: <34544e65-985f-c3a8-3f8d-e9f2550f2fcd@maxrnd.com>
Hi Marco,
When I said "could you handle" I meant I would author the revised patch, test it
locally, and pass it on to you to integrate into the Cygwin Python packages. Does
that sound workable to you?
Thank you,
..mark
-------- Forwarded Message --------
Subject: Concerning Python patch 3.6.12-socketmodule.patch
Date: Mon, 7 Nov 2022 23:07:02 -0800
From: Mark Geisert <mark@maxrnd.com>
To: cygwin-apps@cygwin.com
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
next prev parent reply other threads:[~2023-02-11 6:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 7:07 Concerning Python patch 3.6.12-socketmodule.patch Mark Geisert
2023-02-11 6:41 ` Mark Geisert [this message]
2023-02-14 21:25 ` Concerning Python patch 3.6.12-socketmodule.patch -- ping Marco Marco Atzeri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7b6be8fa-1a85-52b8-ce23-677f243f67d0@maxrnd.com \
--to=mark@maxrnd.com \
--cc=cygwin-apps@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).