I applied the trunk patch, hoping it would trigger some additional improvements. Once we are there +1 on backporting, but I don't think we should do that on every separate patch.
Bert -----Original Message----- From: "Daniel Shahaf" <d...@daniel.shahaf.name> Sent: 19-7-2015 19:12 To: "dev@subversion.apache.org" <dev@subversion.apache.org> Cc: "comm...@subversion.apache.org" <comm...@subversion.apache.org>; "Stefan Hett" <ste...@egosoft.com> Subject: Re: svn commit: r1691712 - /subversion/trunk/INSTALL rhuij...@apache.org wrote on Sat, Jul 18, 2015 at 10:14:12 -0000: > - specify Python >= 3.0 being unsupported atm ... > @@ -449,10 +449,11 @@ I. INTRODUCTION > 10. Python 2.5 or newer (http://www.python.org/) (OPTIONAL) > > If you want to run "make check" or build from the latest source > - under Unix as described in section II.B and III.D, install > - Python 2.5 or higher on your system. The majority of the test > - suite is written in Python, as is part of Subversion's build > + under Unix/Windows as described in section II.B, II.E and III.D, > + install Python 2.5 or higher on your system. The majority of the > + test suite is written in Python, as is part of Subversion's build > system. > + Note that Python 3.x is not supported and most likely won't work. I believe that, with Python 3 on Unix, autogen.sh && configure && make work, but 'make check' doesn't. But we don't have a buildbot running that config, so maybe it's right to call it "not (yet) supported". Shouldn't this be backported to 1.9? Cheers, Daniel
