svn commit: r1869883 - /subversion/branches/1.10.x/STATUS

2019-11-15 Thread danielsh
Author: danielsh
Date: Fri Nov 15 23:53:13 2019
New Revision: 1869883

URL: http://svn.apache.org/viewvc?rev=1869883&view=rev
Log:
* STATUS: Nominate r1868151.

Modified:
subversion/branches/1.10.x/STATUS

Modified: subversion/branches/1.10.x/STATUS
URL: 
http://svn.apache.org/viewvc/subversion/branches/1.10.x/STATUS?rev=1869883&r1=1869882&r2=1869883&view=diff
==
--- subversion/branches/1.10.x/STATUS (original)
+++ subversion/branches/1.10.x/STATUS Fri Nov 15 23:53:13 2019
@@ -32,6 +32,13 @@ Candidate changes:
Votes:
  +1: brane
 
+ * r1868151
+   Fix syntax error when $PYTHON is Python 3.
+   Justification:
+ Python 2 will reach EOL during the lifetime of this branch.
+   Votes:
+ +1: danielsh
+
 Veto-blocked changes:
 =
 




Re: svn commit: r1869870 - /subversion/trunk/INSTALL

2019-11-15 Thread Daniel Shahaf
hartmannat...@apache.org wrote on Fri, Nov 15, 2019 at 16:40:22 -:
> +++ subversion/trunk/INSTALL Fri Nov 15 16:40:22 2019
> @@ -344,17 +344,21 @@ I.INTRODUCTION
> +  7.  Berkeley DB 4.X  (DEPRECATED and OPTIONAL)
⋮
> +  The BDB back end has been deprecated in favor of FSFS, which
> +  stores the repository in a flat filesystem.  You do not need 
> +  Berkeley DB if you will only use the FSFS repository filesystem,
> +  or if you are building a Subversion client that will only speak 
> +  to remote (networked) repositories.

Could "remote (networked) repositories" be misunderstood as referring to
NFS-mounted repositories?  Suggest to append "via the svn:// or http:// URI
schemes and their variants" (svn+ssh, svn+foo, https).


Re: svn commit: r1869868 - /subversion/trunk/INSTALL

2019-11-15 Thread Daniel Shahaf
hartmannat...@apache.org wrote on Fri, Nov 15, 2019 at 16:21:00 -:
> +++ subversion/trunk/INSTALL Fri Nov 15 16:20:59 2019
> @@ -120,17 +120,17 @@ I.INTRODUCTION
>  assembler modules of OpenSSL.  As of OpenSSL 1.1.0 NASM is the
>  only supported assembler.
>  
> +  * Berkeley DB (DEPRECATED and OPTIONAL for client and server)
>  
> + When you create a repository, you have the option of
> + specifying a storage 'back-end' implementation.  Currently,
> + there are two options.  The newer and recommended one, known

There are three options: bdb, fsfs, fsx.  (This error predates your change.)

Cheers,

Daniel

> + as FSFS, does not require Berkeley DB.  FSFS stores data in a
> + flat filesystem.  The older implementation, known as BDB, has
> + been deprecated and is not recommend, but is still available.
> + BDB stores data in a Berkeley DB database.  This back-end
> + will only be available if the BDB libraries are discovered at
> + compile time.
>  
>* libsasl (OPTIONAL for client and server)
>  
> 
> 


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

2019-11-15 Thread Daniel Shahaf
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&view=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


Re: svn commit: r1869851 - in /subversion/trunk/subversion: include/svn_client.h libsvn_client/revert.c

2019-11-15 Thread Daniel Shahaf
julianf...@apache.org wrote on Fri, Nov 15, 2019 at 12:34:58 -:
> +++ subversion/trunk/subversion/include/svn_client.h Fri Nov 15 12:34:57 2019
> @@ -4479,6 +4479,9 @@ svn_client_relocate(const char *dir,
>   * removed from the working copy. Otherwise, all items are reverted and
>   * their on-disk state changed to match.
>   *
> + * Consult @a ctx to determine whether or not to revert timestamp to the
> + * time of last commit ('use-commit-times = yes').

Say «#SVN_CONFIG_OPTION_USE_COMMIT_TIMES» somewhere in there?


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

2019-11-15 Thread Daniel Shahaf
julianf...@apache.org wrote on Fri, Nov 15, 2019 at 11:46:31 -:
> +++ subversion/site/staging/docs/release-notes/1.14.html Fri Nov 15 11:46:31 
> 2019
> @@ -219,7 +219,7 @@ users.  We'll cover those in this sectio
> -Subversion's SWIG Python bindings and automated test suite now
> +Subversion's SWIG Python bindings and Subversion's test suite now
>  support Python 3.x (and newer).

That will be true in 1.13.1 too.  Would it be worthwhile to point this out?
Probably not in 1.14.html but in the "Known bugs" section of 1.13.html?

> @@ -245,9 +246,8 @@ Welcome below.
> +As of 1 January 2020, https://www.python.org/dev/peps/pep-0373/";>
> +Python 2.7 has reached end of life. All users are strongly encouraged

Please change "> Python" to ">Python" with no intervening whitespace; the
whitespace is noticeable in the rendered HTML.  (Or, at least, it _was_ 
noticeable
when I last tested this.)  Thus:

example

Cheers,

Daniel


svn commit: r1869882 - in /subversion/site/publish: ./ docs/release-notes/1.14.html index.html news.html roadmap.html

2019-11-15 Thread hartmannathan
Author: hartmannathan
Date: Fri Nov 15 20:43:50 2019
New Revision: 1869882

URL: http://svn.apache.org/viewvc?rev=1869882&view=rev
Log:
Merge 'staging' to 'publish'.

Modified:
subversion/site/publish/   (props changed)
subversion/site/publish/docs/release-notes/1.14.html
subversion/site/publish/index.html   (props changed)
subversion/site/publish/news.html   (props changed)
subversion/site/publish/roadmap.html   (props changed)

Propchange: subversion/site/publish/
--
  Merged /subversion/site/staging:r1869159-1869871

Modified: subversion/site/publish/docs/release-notes/1.14.html
URL: 
http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.14.html?rev=1869882&r1=1869881&r2=1869882&view=diff
==
--- subversion/site/publish/docs/release-notes/1.14.html (original)
+++ subversion/site/publish/docs/release-notes/1.14.html Fri Nov 15 20:43:50 
2019
@@ -39,6 +39,10 @@
   ###
   -->
+  Support for Python 3.x
+  Support for Python 2.7 is being phased out
   Many enhancements and bug fixes

 
+
+API changes, improvements and language bindings
+(client and server)
+  ¶
+
+
+
+Support for Python 3.x
+  ¶
+
+
+Some optional features of Subversion utilize the Python scripting
+language.
+
+Subversion's SWIG Python bindings and Subversion's test suite now
+support Python 3.x (and newer).
+
+
+TODO: Describe which minor releases of Python 3.x we
+plan to support through the four-year LTS period of Subversion 1.14.
+Per recent discussions on the dev@ mailing list, that might be some
+form of "rolling" support: In each 1.14.x patch release, we would make
+an effort to support the oldest through newest minor lines of Python
+3.x that Python upstream supports at the time of our release. However,
+we could drop support for the oldest one if we have a compelling
+reason to do so.
+
+Of course, we welcome contributions that extend Subversion's Python
+support to include other versions, subject to the project's other needs.
+See the section
+Enthusiastic Contributors
+Welcome below.
+
+  
+
+
+Support for Python 2.7 is being phased out
+  ¶
+
+
+As of 1 January 2020, https://www.python.org/dev/peps/pep-0373/";>
+Python 2.7 has reached end of life. All users are strongly encouraged
+to move to Python 3.
+
+As Subversion 1.14 is a Long Term Support (LTS) release with
+planned support into 2024, well beyond end-of-life for Python 2.7, the
+core Subversion developers cannot commit to supporting and testing
+with Python 2.7, or to fixing bugs that affect Python 2.7 only, for
+the duration of this support period.
+
+This means that although Subversion 1.14.0 still technically works
+with Python 2.7, any later 1.14.x point release may drop this support
+if it becomes too difficult to maintain.
+
+If you must continue using Python 2.7, our previous Long Term Support
+release, Subversion 1.10, is supported until 2022. Python 2.7 support
+will not be removed from Subversion 1.10.
+
+Of course, we welcome contributions that extend Subversion's Python
+2.7 support, subject to the project's other needs. See the section
+Enthusiastic Contributors
+Welcome below.
+
+  
+
+
+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:
+
+
+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
+
+
+ 
+
+  
+
   
 
 
@@ -245,6 +367,46 @@ if they occur.
 
   
 
+
+Enthusiastic Contributors Welcome!
+  ¶
+
+
+You can contribute to Subversion!
+
+As Subversion is an open source project developed and supported by
+volunteers, we are always happy to welcome enthusiastic participants
+to the community.
+
+Whether you'd like to see support for additional versions of Python
+or have ideas for some big new features, if you're willing to invest
+the e

svn commit: r1869871 - /subversion/trunk/INSTALL

2019-11-15 Thread hartmannathan
Author: hartmannathan
Date: Fri Nov 15 17:42:51 2019
New Revision: 1869871

URL: http://svn.apache.org/viewvc?rev=1869871&view=rev
Log:
INSTALL: Unify Python-related dependency info from 1.14 release notes

* INSTALL:
  (Section I.C. "Dependencies in Detail" -- Python)  Bring in the far
more detailed Python dependency info that was added to the 1.14
release notes in r1869856, but with some editing to better fit the
context of INSTALL.  In particular, the new text explains when the
optional dependency of Python is needed and when it is not.  Also,
bump the Python version to 3.x, but with a paragraph explaining
that although 2.7 support is being phased out, it technically
still works.

Suggested by: julianfoad

Modified:
subversion/trunk/INSTALL

Modified: subversion/trunk/INSTALL
URL: 
http://svn.apache.org/viewvc/subversion/trunk/INSTALL?rev=1869871&r1=1869870&r2=1869871&view=diff
==
--- subversion/trunk/INSTALL (original)
+++ subversion/trunk/INSTALL Fri Nov 15 17:42:51 2019
@@ -415,13 +415,53 @@ I.INTRODUCTION
   is done: See section III for details.
 
 
-  10.  Python 2.7 or newer (https://www.python.org/)  (OPTIONAL)
+  10.  Python 3.x or newer (https://www.python.org/)  (OPTIONAL)
+
+  Subversion does not require Python for its basic operation.
+  However, Python is required for building and testing Subversion
+  and for using Subversion's SWIG Python bindings or hook scripts
+  coded in Python.
+
+  The majority of Subversion's test suite is written in Python, as
+  is part of Subversion's build system.
+
+  In more detail, Python is required to do any of the following:
+
+  * Use the SWIG Python bindings.
+  * Use the ctypes Python bindings.
+  * Use hook scripts coded in Python.
+  * Build Subversion from a tarball on Unix-like systems and run
+Subversion's test suite as described in section II.B.
+  * Build Subversion on Windows as described in section II.E.
+  * Build Subversion from a working copy checked out from
+Subversion's own repository (whether or not running the test
+suite).
+  * Build the SWIG Python bindings.
+  * Build the ctypes Python bindings.
+  * Testing as described in section III.D.
+
+  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.
+
+  Python is NOT required to do any of the following:
+
+  * Use the core command-line binaries (svn, svnadmin, svnsync,
+etc.)
+  * 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
+
+  Although this section calls for Python 3.x, Subversion still
+  technically works with Python 2.7.  However, Support for Python
+  2.7 is being phased out.  As of 1 January 2020, Python 2.7 has
+  reached end of life.  All users are strongly encouraged to move
+  to Python 3.
 
-  If you want to run "make check" or build from the latest source
-  under Unix/Windows as described in section II.B, II.E and III.D,
-  install Python 2.7 or higher on your system. The majority of the
-  test suite is written in Python, as is part of Subversion's build
-  system.
 
   11. Perl 5.8 or newer (Windows only)  (OPTIONAL)
 




svn commit: r1869870 - /subversion/trunk/INSTALL

2019-11-15 Thread hartmannathan
Author: hartmannathan
Date: Fri Nov 15 16:40:22 2019
New Revision: 1869870

URL: http://svn.apache.org/viewvc?rev=1869870&view=rev
Log:
INSTALL: Improve another section regarding Berkeley DB dependency.

* INSTALL:
  ("Dependencies in Detail" -- "Berkeley DB") Similar to the change to
"Dependencies Overview" in r1869868, explain that BDB is
deprecated at the beginning of the section to make it more clear
that BDB is not needed if only using FSFS.

Modified:
subversion/trunk/INSTALL

Modified: subversion/trunk/INSTALL
URL: 
http://svn.apache.org/viewvc/subversion/trunk/INSTALL?rev=1869870&r1=1869869&r2=1869870&view=diff
==
--- subversion/trunk/INSTALL (original)
+++ subversion/trunk/INSTALL Fri Nov 15 16:40:22 2019
@@ -344,17 +344,21 @@ I.INTRODUCTION
   https://www.openssl.org/
 
 
-  7.  Berkeley DB 4.X  (OPTIONAL)
+  7.  Berkeley DB 4.X  (DEPRECATED and OPTIONAL)
 
   Berkeley DB is needed to build a Subversion server that supports
   the BDB repository filesystem, or to access a BDB repository on
-  local disk.  If you will only use the FSFS repository filesystem,
-  or if you are building a Subversion client that will only speak
-  to remote (networked) repositories, you don't need it.
-
-  The current recommended version is 4.4.20 or newer, which brings
-  auto-recovery functionality to the Berkeley DB database
-  environment.
+  local disk.
+
+  The BDB back end has been deprecated in favor of FSFS, which
+  stores the repository in a flat filesystem.  You do not need 
+  Berkeley DB if you will only use the FSFS repository filesystem,
+  or if you are building a Subversion client that will only speak 
+  to remote (networked) repositories.
+
+  The current recommended version of Berkeley DB is 4.4.20 or
+  newer, which brings auto-recovery functionality to the Berkeley
+  DB database environment.
 
   If you must use an older version of Berkeley DB, we *strongly*
   recommend using 4.3 or 4.2 over the 4.1 or 4.0 versions.  Not




svn commit: r1869868 - /subversion/trunk/INSTALL

2019-11-15 Thread hartmannathan
Author: hartmannathan
Date: Fri Nov 15 16:20:59 2019
New Revision: 1869868

URL: http://svn.apache.org/viewvc?rev=1869868&view=rev
Log:
INSTALL: Rewrite section about Berkeley DB dependency.

* INSTALL:
  ("Dependencies in Detail" -- "Berkeley DB") Add "DEPRECATED" to the
title of the bullet point.  Rewrite the paragraph to (hopefully)
make it more clear.  Rationale: Avoid having to read a long
paragraph only to find out at the end that BDB is deprecated.

Modified:
subversion/trunk/INSTALL

Modified: subversion/trunk/INSTALL
URL: 
http://svn.apache.org/viewvc/subversion/trunk/INSTALL?rev=1869868&r1=1869867&r2=1869868&view=diff
==
--- subversion/trunk/INSTALL (original)
+++ subversion/trunk/INSTALL Fri Nov 15 16:20:59 2019
@@ -120,17 +120,17 @@ I.INTRODUCTION
 assembler modules of OpenSSL.  As of OpenSSL 1.1.0 NASM is the
 only supported assembler.
 
-  * Berkeley DB (OPTIONAL for client and server)
+  * Berkeley DB (DEPRECATED and OPTIONAL for client and server)
 
- There are two different repository 'back-end'
- implementations.  One implementation stores data in a flat
- filesystem (known as FSFS); the other implementation stores
- data in a Berkeley DB database (known as BDB).  When you
- create a repository, you have the option of specifying a
- storage back-end.  The Berkeley DB back-end will only be
- available if the BDB libraries are discovered at compile
- time.  The Berkeley DB back-end has been deprecated and
- is not recommend.
+ When you create a repository, you have the option of
+ specifying a storage 'back-end' implementation.  Currently,
+ there are two options.  The newer and recommended one, known
+ as FSFS, does not require Berkeley DB.  FSFS stores data in a
+ flat filesystem.  The older implementation, known as BDB, has
+ been deprecated and is not recommend, but is still available.
+ BDB stores data in a Berkeley DB database.  This back-end
+ will only be available if the BDB libraries are discovered at
+ compile time.
 
   * libsasl (OPTIONAL for client and server)
 




svn commit: r1869866 - /subversion/trunk/INSTALL

2019-11-15 Thread hartmannathan
Author: hartmannathan
Date: Fri Nov 15 16:07:41 2019
New Revision: 1869866

URL: http://svn.apache.org/viewvc?rev=1869866&view=rev
Log:
* INSTALL: Fix grammar error regarding optional NASM dependency.

Modified:
subversion/trunk/INSTALL

Modified: subversion/trunk/INSTALL
URL: 
http://svn.apache.org/viewvc/subversion/trunk/INSTALL?rev=1869866&r1=1869865&r2=1869866&view=diff
==
--- subversion/trunk/INSTALL (original)
+++ subversion/trunk/INSTALL Fri Nov 15 16:07:41 2019
@@ -116,7 +116,7 @@ I.INTRODUCTION
 
   * Netwide Assembler (OPTIONAL for client and server)
 
-The Netwide Assembler (NASM) is used to build the (optionally)
+The Netwide Assembler (NASM) is used to build the (optional)
 assembler modules of OpenSSL.  As of OpenSSL 1.1.0 NASM is the
 only supported assembler.
 




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

2019-11-15 Thread hartmannathan
Author: hartmannathan
Date: Fri Nov 15 14:52:50 2019
New Revision: 1869856

URL: http://svn.apache.org/viewvc?rev=1869856&view=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&r1=1869855&r2=1869856&view=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
+
+
  
 
   




svn commit: r1869853 - in /subversion/trunk: build/ac-macros/swig.m4 subversion/bindings/swig/INSTALL subversion/bindings/swig/include/proxy.py subversion/bindings/swig/include/proxy.swg

2019-11-15 Thread hartmannathan
Author: hartmannathan
Date: Fri Nov 15 14:09:09 2019
New Revision: 1869853

URL: http://svn.apache.org/viewvc?rev=1869853&view=rev
Log:
Support building with SWIG 4 on Python 3.x

* build/ac-macros/swig.m4
  (SVN_FIND_SWIG): Allow building with SWIG 4+, and add -modern option
when Python 3 and SWIG 3.x are detected.

* subversion/bindings/swig/include/proxy.py
Use _get_instance_attr and _set_instance_attr.

* subversion/bindings/swig/include/proxy.swg
  (_get_instance_attr): New function to get an instance attribute
without metadata for new-style and old-style classes.
  (_set_instance_attr): New function to set an instance attribute for
new-style and old-style classes.

* subversion/bindings/swig/INSTALL
  (BUILDING SWIG BINDINGS FOR SVN ON UNIX, Step 1): Update supported
SWIG versions for Python 3 bindings (remove the note that SWIG 4+
is not supported).

Patch by: Jun Omae 

Review by: brane
   futatuki
   julianfoad

Modified:
subversion/trunk/build/ac-macros/swig.m4
subversion/trunk/subversion/bindings/swig/INSTALL
subversion/trunk/subversion/bindings/swig/include/proxy.py
subversion/trunk/subversion/bindings/swig/include/proxy.swg

Modified: subversion/trunk/build/ac-macros/swig.m4
URL: 
http://svn.apache.org/viewvc/subversion/trunk/build/ac-macros/swig.m4?rev=1869853&r1=1869852&r2=1869853&view=diff
==
--- subversion/trunk/build/ac-macros/swig.m4 (original)
+++ subversion/trunk/build/ac-macros/swig.m4 Fri Nov 15 14:09:09 2019
@@ -158,14 +158,17 @@ AC_DEFUN(SVN_FIND_SWIG,
   ])
 
   if test "$ac_cv_python_is_py3" = "yes"; then
-if test "$SWIG_VERSION" -ge "300010" -a "$SWIG_VERSION" -lt 
"40"; then
-  SWIG_PY_OPTS="-python -py3"
+if test "$SWIG_VERSION" -ge "300010"; then
   dnl SWIG Python bindings successfully configured, clear the 
error message dnl
   SWIG_PY_ERRMSG=""
 else
-  SWIG_PY_OPTS="-python -py3 -nofastunpack"
   SWIG_PY_ERRMSG="SWIG version is not suitable"
-  AC_MSG_WARN([Subversion Python bindings for Python 3 require 
3.0.10 <= SWIG < 4.0.0])
+  AC_MSG_WARN([Subversion Python bindings for Python 3 require 
SWIG 3.0.10 or newer])
+fi
+if test "$SWIG_VERSION" -lt "40"; then
+  SWIG_PY_OPTS="-python -py3 -nofastunpack -modern"
+else
+  SWIG_PY_OPTS="-python -py3 -nofastunpack"
 fi
   else
 if test "$SWIG_VERSION" -lt "40"; then

Modified: subversion/trunk/subversion/bindings/swig/INSTALL
URL: 
http://svn.apache.org/viewvc/subversion/trunk/subversion/bindings/swig/INSTALL?rev=1869853&r1=1869852&r2=1869853&view=diff
==
--- subversion/trunk/subversion/bindings/swig/INSTALL (original)
+++ subversion/trunk/subversion/bindings/swig/INSTALL Fri Nov 15 14:09:09 2019
@@ -78,8 +78,7 @@ Step 1: [Optional] Install a suitable ve
   - SWIG 1.3.24 and later 1.3.x may work, but we do not test these
 versions on our latest source code.
   - For Python 2 bindings, SWIG 4.0.0 or later is not supported.
-  - For Python 3 bindings, SWIG 3.0.10 or later is required, but
-SWIG 4.0.0 and later is not supported (yet).
+  - For Python 3 bindings, SWIG 3.0.10 or later is required.
   - Note that SWIG 3.0.9 has some trouble with Python support.
 (See https://sourceforge.net/p/swig/news/2016/06/swig-3010-released/)
   - For Perl 5.16 and later, SWIG 2.0.8 or later is required.

Modified: subversion/trunk/subversion/bindings/swig/include/proxy.py
URL: 
http://svn.apache.org/viewvc/subversion/trunk/subversion/bindings/swig/include/proxy.py?rev=1869853&r1=1869852&r2=1869853&view=diff
==
--- subversion/trunk/subversion/bindings/swig/include/proxy.py (original)
+++ subversion/trunk/subversion/bindings/swig/include/proxy.py Fri Nov 15 
14:09:09 2019
@@ -25,13 +25,6 @@
 
 return value
 
-  # SWIG classes generated with -classic do not define this variable,
-  # so set it to 0 when it doesn't exist
-  try:
-_newclass
-  except NameError:
-_newclass = 0
-
   # Attribute access must be intercepted to ensure that objects coming from
   # read attribute access match those that are set with write attribute access.
   # Specifically the metadata, such as the associated apr_pool object, should
@@ -58,13 +51,7 @@
 
   object.__getattribute__(self, 'assert_valid')()
 
-  try:
-value = object.__getattribute__(self, name)
-  except AttributeError:
-value = _swig_getattr(self,
-  object.__getattribute__(self, '__class__'),
-  name)
-
+  value = _get_instance_attr(self, name)
 

svn commit: r1869851 - in /subversion/trunk/subversion: include/svn_client.h libsvn_client/revert.c

2019-11-15 Thread julianfoad
Author: julianfoad
Date: Fri Nov 15 12:34:57 2019
New Revision: 1869851

URL: http://svn.apache.org/viewvc?rev=1869851&view=rev
Log:
Fix doc-strings of 'revert' API.

* subversion/include/svn_client.h
  (svn_client_revert4): Document 'use commit times' behaviour.

* subversion/libsvn_client/revert.c
  (revert): Refer to existing docs.

Modified:
subversion/trunk/subversion/include/svn_client.h
subversion/trunk/subversion/libsvn_client/revert.c

Modified: subversion/trunk/subversion/include/svn_client.h
URL: 
http://svn.apache.org/viewvc/subversion/trunk/subversion/include/svn_client.h?rev=1869851&r1=1869850&r2=1869851&view=diff
==
--- subversion/trunk/subversion/include/svn_client.h (original)
+++ subversion/trunk/subversion/include/svn_client.h Fri Nov 15 12:34:57 2019
@@ -4479,6 +4479,9 @@ svn_client_relocate(const char *dir,
  * removed from the working copy. Otherwise, all items are reverted and
  * their on-disk state changed to match.
  *
+ * Consult @a ctx to determine whether or not to revert timestamp to the
+ * time of last commit ('use-commit-times = yes').
+ *
  * If @a ctx->notify_func2 is non-NULL, then for each item reverted,
  * call @a ctx->notify_func2 with @a ctx->notify_baton2 and the path of
  * the reverted item.

Modified: subversion/trunk/subversion/libsvn_client/revert.c
URL: 
http://svn.apache.org/viewvc/subversion/trunk/subversion/libsvn_client/revert.c?rev=1869851&r1=1869850&r2=1869851&view=diff
==
--- subversion/trunk/subversion/libsvn_client/revert.c (original)
+++ subversion/trunk/subversion/libsvn_client/revert.c Fri Nov 15 12:34:57 2019
@@ -57,24 +57,12 @@ struct revert_with_write_lock_baton {
 
 /* (Note: All arguments are in the baton above.)
 
-   Attempt to revert LOCAL_ABSPATH.
+   Attempt to revert LOCAL_ABSPATH by calling svn_wc_revert6(), which
+   see for further details.
 
-   If DEPTH is svn_depth_empty, revert just the properties on the
-   directory; else if svn_depth_files, revert the properties and any
-   files immediately under the directory; else if
-   svn_depth_immediates, revert all of the preceding plus properties
-   on immediate subdirectories; else if svn_depth_infinity, revert
-   path and everything under it fully recursively.
-
-   CHANGELISTS is an array of const char * changelist names, used as a
-   restrictive filter on items reverted; that is, don't revert any
-   item unless it's a member of one of those changelists.  If
-   CHANGELISTS is empty (or altogether NULL), no changelist filtering occurs.
-
-   Consult CTX to determine whether or not to revert timestamp to the
-   time of last commit ('use-commit-times = yes').
-
-   If PATH is unversioned, return SVN_ERR_UNVERSIONED_RESOURCE. */
+   If the target isn't versioned, send a 'skip' notification and return
+   no error.
+ */
 static svn_error_t *
 revert(void *baton, apr_pool_t *result_pool, apr_pool_t *scratch_pool)
 {




svn commit: r1869850 - in /subversion/site/staging: ./ docs/release-notes/1.14.html

2019-11-15 Thread julianfoad
Author: julianfoad
Date: Fri Nov 15 11:50:31 2019
New Revision: 1869850

URL: http://svn.apache.org/viewvc?rev=1869850&view=rev
Log:
In 'staging': catch-up merge from 'publish'.

Modified:
subversion/site/staging/   (props changed)
subversion/site/staging/docs/release-notes/1.14.html

Propchange: subversion/site/staging/
--
  Merged /subversion/site/publish:r1869775-1869849

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=1869850&r1=1869849&r2=1869850&view=diff
==
--- subversion/site/staging/docs/release-notes/1.14.html (original)
+++ subversion/site/staging/docs/release-notes/1.14.html Fri Nov 15 11:50:31 
2019
@@ -57,9 +57,7 @@
 releases, and is as of the time of its release considered the current
 "best" release.  Any feature or bugfix in 1.0.x through 1.13.x is also
 in 1.14, but 1.14 contains features and bugfixes not present in any
-earlier release.  The new features will eventually be documented in a
-1.14 version of the free Subversion book
-(http://svnbook.red-bean.com/"; >svnbook.red-bean.com).
+earlier release.
 
 This page describes only major changes.  For a complete list of
 changes, see the 1.14 section of the 

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

2019-11-15 Thread julianfoad
Author: julianfoad
Date: Fri Nov 15 11:46:31 2019
New Revision: 1869849

URL: http://svn.apache.org/viewvc?rev=1869849&view=rev
Log:
* staging/docs/release-notes/1.14.html
  (python2, python3): Tweak text; link to Py2 EOL PEP.

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=1869849&r1=1869848&r2=1869849&view=diff
==
--- subversion/site/staging/docs/release-notes/1.14.html (original)
+++ subversion/site/staging/docs/release-notes/1.14.html Fri Nov 15 11:46:31 
2019
@@ -219,7 +219,7 @@ users.  We'll cover those in this sectio
 Some optional features of Subversion utilize the Python scripting
 language.
 
-Subversion's SWIG Python bindings and automated test suite now
+Subversion's SWIG Python bindings and Subversion's test suite now
 support Python 3.x (and newer).
 
 
@@ -233,7 +233,8 @@ we could drop support for the oldest one
 reason to do so.
 
 Of course, we welcome contributions that extend Subversion's Python
-support to include other versions. See the section
+support to include other versions, subject to the project's other needs.
+See the section
 Enthusiastic Contributors
 Welcome below.
 
@@ -245,9 +246,8 @@ Welcome below.
 title="Link to this section">¶
 
 
-As of 1 January 2020, Python 2.7 has reached end of life. This
-means that Python 2.7 will no longer receive maintenance releases or
-patches, even for security issues. All users are strongly encouraged
+As of 1 January 2020, https://www.python.org/dev/peps/pep-0373/";>
+Python 2.7 has reached end of life. All users are strongly encouraged
 to move to Python 3.
 
 As Subversion 1.14 is a Long Term Support (LTS) release with
@@ -265,7 +265,7 @@ release, Subversion 1.10, is supported u
 will not be removed from Subversion 1.10.
 
 Of course, we welcome contributions that extend Subversion's Python
-2.7 support. See the section
+2.7 support, subject to the project's other needs. See the section
 Enthusiastic Contributors
 Welcome below.
 
@@ -276,7 +276,7 @@ Welcome below.
 
 Note that Subversion does not require Python for its basic
 operation. If you are not using Subversion's SWIG Python bindings,
-automated test suite, or other Python-coded tools that ship with
+Subversion's test suite, or other Python-coded tools that ship with
 Subversion, this change does not affect you.
  
 




svn commit: r1869837 - in /subversion/trunk/tools/dist/templates: release-notes-lts.ezt release-notes.ezt

2019-11-15 Thread julianfoad
Author: julianfoad
Date: Fri Nov 15 09:02:49 2019
New Revision: 1869837

URL: http://svn.apache.org/viewvc?rev=1869837&view=rev
Log:
Release notes templates: Stop claiming the book will be updated.

Modified:
subversion/trunk/tools/dist/templates/release-notes-lts.ezt
subversion/trunk/tools/dist/templates/release-notes.ezt

Modified: subversion/trunk/tools/dist/templates/release-notes-lts.ezt
URL: 
http://svn.apache.org/viewvc/subversion/trunk/tools/dist/templates/release-notes-lts.ezt?rev=1869837&r1=1869836&r2=1869837&view=diff
==
--- subversion/trunk/tools/dist/templates/release-notes-lts.ezt (original)
+++ subversion/trunk/tools/dist/templates/release-notes-lts.ezt Fri Nov 15 
09:02:49 2019
@@ -53,9 +53,7 @@
 releases, and is as of the time of its release considered the current
 "best" release.  Any feature or bugfix in 1.0.x through 
[previous-major-minor].x is also
 in [major-minor], but [major-minor] contains features and bugfixes not present 
in any
-earlier release.  The new features will eventually be documented in a
-[major-minor] version of the free Subversion book
-(http://svnbook.red-bean.com/"; >svnbook.red-bean.com).
+earlier release.
 
 This page describes only major changes.  For a complete list of
 changes, see the [major-minor] section of the http://svn.apache.org/viewvc/subversion/trunk/tools/dist/templates/release-notes.ezt?rev=1869837&r1=1869836&r2=1869837&view=diff
==
--- subversion/trunk/tools/dist/templates/release-notes.ezt (original)
+++ subversion/trunk/tools/dist/templates/release-notes.ezt Fri Nov 15 09:02:49 
2019
@@ -53,9 +53,7 @@
 releases, and is as of the time of its release considered the current
 "best" release.  Any feature or bugfix in 1.0.x through 
[previous-major-minor].x is also
 in [major-minor], but [major-minor] contains features and bugfixes not present 
in any
-earlier release.  The new features will eventually be documented in a
-[major-minor] version of the free Subversion book
-(http://svnbook.red-bean.com/"; >svnbook.red-bean.com).
+earlier release.
 
 This page describes only major changes.  For a complete list of
 changes, see the [major-minor] section of the 

svn commit: r1869838 - /subversion/site/publish/docs/release-notes/1.14.html

2019-11-15 Thread julianfoad
Author: julianfoad
Date: Fri Nov 15 09:02:51 2019
New Revision: 1869838

URL: http://svn.apache.org/viewvc?rev=1869838&view=rev
Log:
* publish/docs/release-notes/1.14.html: Stop claiming the book will be updated.

Modified:
subversion/site/publish/docs/release-notes/1.14.html

Modified: subversion/site/publish/docs/release-notes/1.14.html
URL: 
http://svn.apache.org/viewvc/subversion/site/publish/docs/release-notes/1.14.html?rev=1869838&r1=1869837&r2=1869838&view=diff
==
--- subversion/site/publish/docs/release-notes/1.14.html (original)
+++ subversion/site/publish/docs/release-notes/1.14.html Fri Nov 15 09:02:51 
2019
@@ -53,9 +53,7 @@
 releases, and is as of the time of its release considered the current
 "best" release.  Any feature or bugfix in 1.0.x through 1.13.x is also
 in 1.14, but 1.14 contains features and bugfixes not present in any
-earlier release.  The new features will eventually be documented in a
-1.14 version of the free Subversion book
-(http://svnbook.red-bean.com/"; >svnbook.red-bean.com).
+earlier release.
 
 This page describes only major changes.  For a complete list of
 changes, see the 1.14 section of the