From: "Jason R. Coombs" <jaraco@jaraco.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: distutils adoption means cygwin-specific patches will be lost
Date: Sat, 11 Dec 2021 16:19:46 +0000 [thread overview]
Message-ID: <94880E76-90FA-4B7A-B5F5-80CB3AD55BC0@jaraco.com> (raw)
The Setuptools project is adopting distutils from the Python standard library. It’s doing this to unify the implementation and allow it to evolve again.
In Setuptools 48 and Setuptools 50, Setuptools made the adopted distutils the default (causing “import distutils” to resolve to `setuptools._distutils` and thus bypass any patches that may have been applied to distutils as found in the stdlib) with an escape hatch: by setting SETUPTOOLS_USE_DISTUTILS=stdlib. Due to incompatibilities identified with this ereleases, the behavior of using the local distutils by default was rolled back.
In about a week’s time, Setuptools will make the local distutils the default again. Users can preview the behavior on existing releases by setting SETUPTOOLS_USE_DISTUTILS=local and opt out with the escape hatch.
Until recently, no one from the Cygwin project has reached out, but recently, mkoeppe did mention the concern leading to the filing of https://github.com/pypa/distutils/issues/73.
The Setuptools/distutils project would be happy to facilitate supporting Cygwin in the new environment without monkey patching, either through direct support of the platform or through hooks that allow the platform to customize the behavior (and probably a mix). Please reach out on the issue to uncover any emergent issues and to devise a design for long term support.
Regards,
Jason R. Coombs
next reply other threads:[~2021-12-11 16:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-11 16:19 Jason R. Coombs [this message]
2021-12-11 16:55 ` 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=94880E76-90FA-4B7A-B5F5-80CB3AD55BC0@jaraco.com \
--to=jaraco@jaraco.com \
--cc=cygwin@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).