Nathan Hartman wrote on Fri, Nov 15, 2019 at 00:40:08 -0500: > [[[ > Python is optional. > > Subversion does not require Python for its basic operation. In general, if > you are not using Subversion's SWIG Python bindings, hook scripts coded in > Python, or other tools that require Python, then this change does not > affect you. > > You may need Python if you are building Subversion from source. Python is > not strictly required when building from a distribution tarball, but is > required to: > * build from a source checkout > * run Subversion's automated test suite > * run other maintainer-oriented scripts > ]]]
I'd like to avoid language such as "not strictly required" and "other maintainer-oriented scripts" because it's bound to leave the reader puzzled, wondering whether _their_ installation would be affected. How about just spelling out the list of known-good and known-bad cases? For example: [[[ Python is optional. Subversion does not require Python for its basic operation. Python is only required for building Subversion and for using Subversion's SWIG Python bindings or hook scripts coded in Python. If you do not do either of these things, then this change does not affect you. In more detail, Python is required for doing any of the following: * Build Subversion on Windows * Build Subversion from a tarball on Unix-like systems and run the test suite * Build Subversion from a working copy checked out from Subversion's own repository * Use the SWIG Python bindings * Use the ctypes Python bindings The bindings are used by third-party programs (e.g., ViewVC), as well as by scripts distributed with Subversion itself in the <a href="…">tools/ subdirectory</a>. They may also be used by any in-house scripts you [= the reader] may have. Python is *not* required for doing any of the following: * Build Subversion from a tarball on Unix-like systems without running the test suite * Use the core command-line binaries (svn, svnadmin, svnsync, …) * Use the C libraries * Use any other language bindings ]]] Cheers, Daniel
