Reword changelog for issue #5207

SQLAlchemy can remain using setuptools even when pep-517 is
the standard installation process.   We are omitting the file
for now because it leads to new pip installation issues that need
to be worked out in the greater pip community before SQLAlchemy
opts into this system.

Change-Id: I40b196100c6f16ae1291fcb7f8b5196bba14a300
(cherry picked from commit e12707263717161950e0c9817758d3240666ed83)

diff --git a/doc/build/changelog/unreleased_13/5207.rst b/doc/build/changelog/unreleased_13/5207.rst
index abc87290f2628256850dca8e028595f7e336e88e..076c51cb266cb6012e9f8b8921364cddad102404 100644 (file)
--- a/doc/build/changelog/unreleased_13/5207.rst
+++ b/doc/build/changelog/unreleased_13/5207.rst
@@ -3,9 +3,8 @@
     :tickets: 5207
 
     Ensured that the "pyproject.toml" file is not included in builds, as the
-    presence of this file is a positive direction to pip that pep-517 should be
-    used. As this mode of operation is not well supported by current tools /
-    distros, we would like to explicitly disallow this mode of operation until
-    we have an actual pep517 installation module available.
-
+    presence of this file indicates to pip that a pep-517 installation process
+    should be used.  As this mode of operation appears to be not well supported
+    by current tools / distros, these problems are avoided within the scope
+    of SQLAlchemy installation by omitting the file.