Re: svn commit: r1869856 - /subversion/site/staging/docs/release-notes/1.14.html
hartmannat...@apache.org wrote on Fri, Nov 15, 2019 at 14:52:50 -:
> Author: hartmannathan
> Date: Fri Nov 15 14:52:50 2019
> New Revision: 1869856
>
> URL: http://svn.apache.org/viewvc?rev=1869856=rev
> Log:
> In 'staging': 1.14 release notes: Explain when/how Python is required
>
> * docs/release-notes/1.14.html:
> ("Python is Optional" note box):
> Explain in detail when Subversion requires Python, and also when
> it does not, replacing short and vague paragraph.
Thanks for HTMLifying and committing that. More below.
> +++ subversion/site/staging/docs/release-notes/1.14.html Fri Nov 15 14:52:50
> 2019
> @@ -272,10 +272,49 @@ Welcome below.
>
> Python is Optional.
>
> -Note that Subversion does not require Python for its basic
> -operation. If you are not using Subversion's SWIG Python bindings,
> -Subversion's test suite, or other Python-coded tools that ship with
> -Subversion, this change does not affect you.
> +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.
This sentence is inaccurate: hook scripts written in Python that don't require
the bindings will not be an issue. Suggestion: say "for building Subversion
and for using the SWIG Python bindings", then move the "The Python bindings are
used by:" bit to after this paragraph.
> 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:
> +
> +
⋮
> +
> +
> +The Python bindings are used by:
> +
> +
> +Third-party programs (e.g.,
> +https://github.com/viewvc/viewvc/;>ViewVC)
> +Scripts distributed with Subversion itself in the tools/
> +subdirectory.
> +Any in-house scripts you may have.
> +
Cheers,
Daniel
svn commit: r1869856 - /subversion/site/staging/docs/release-notes/1.14.html
Author: hartmannathan
Date: Fri Nov 15 14:52:50 2019
New Revision: 1869856
URL: http://svn.apache.org/viewvc?rev=1869856=rev
Log:
In 'staging': 1.14 release notes: Explain when/how Python is required
* docs/release-notes/1.14.html:
("Python is Optional" note box):
Explain in detail when Subversion requires Python, and also when
it does not, replacing short and vague paragraph.
Suggested by: danielsh
Modified:
subversion/site/staging/docs/release-notes/1.14.html
Modified: subversion/site/staging/docs/release-notes/1.14.html
URL:
http://svn.apache.org/viewvc/subversion/site/staging/docs/release-notes/1.14.html?rev=1869856=1869855=1869856=diff
==
--- subversion/site/staging/docs/release-notes/1.14.html (original)
+++ subversion/site/staging/docs/release-notes/1.14.html Fri Nov 15 14:52:50
2019
@@ -272,10 +272,49 @@ Welcome below.
Python is Optional.
-Note that Subversion does not require Python for its basic
-operation. If you are not using Subversion's SWIG Python bindings,
-Subversion's test suite, or other Python-coded tools that ship with
-Subversion, this change does not affect you.
+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:
+
+
+Use the SWIG Python bindings
+Use the ctypes Python bindings
+Build Subversion on Windows
+Build Subversion from a tarball on Unix-like systems and run
+Subversion's test suite
+Build Subversion from a working copy checked out from Subversion's
+own repository
+Build the SWIG Python bindings
+Build the ctypes Python bindings
+
+
+The Python bindings are used by:
+
+
+Third-party programs (e.g.,
+https://github.com/viewvc/viewvc/;>ViewVC)
+Scripts distributed with Subversion itself in the tools/
+subdirectory.
+Any in-house scripts you may have.
+
+
+Python is not required for doing any of the
+following:
+
+
+Use the core command-line binaries (svn, svnadmin, svnsync,
+)
+Use Subversion's C libraries
+Use any of Subversion's other language bindings
+Build Subversion from a tarball on Unix-like systems without
+running Subversion's test suite
+
+
