Re: svn commit: r1869856 - /subversion/site/staging/docs/release-notes/1.14.html

On Fri, Nov 15, 2019 at 6:40 PM Daniel Shahaf <d.s_at_daniel.shahaf.name>
wrote:

> > +<p>Subversion does <strong>not</strong> 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.
>

You're right. Scripts coded in Python can exec calls to the svn
binaries... We don't care what version of Python they're using for that.

Regarding your suggestion, I'm not sure I understand correctly. Are you
suggesting to re-order the paragraphs, like so:

[[[

Subversion does *not* require Python for its basic operation. Python
is only required for building Subversion and for using Subversion's
SWIG Python bindings. If you do not do either of these things, then
this change does not affect you.

The Python bindings are used by:

* Third-party programs (e.g., ViewVC)
* Scripts distributed with Subversion itself in the tools/
  subdirectory.
* Any in-house scripts you may have.

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

]]]

Thanks,
Nathan
Received on 2019-11-17 06:16:10 CET