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.
From: "Daniel Shahaf" <d.s_at_daniel.shahaf.name>
Sent: 19-7-2015 19:12
To: "dev_at_subversion.apache.org" <dev_at_subversion.apache.org>
Cc: "commits_at_subversion.apache.org" <commits_at_subversion.apache.org>; "Stefan Hett" <stefan_at_egosoft.com>
Subject: Re: svn commit: r1691712 - /subversion/trunk/INSTALL
rhuijben_at_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
> + 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?
Received on 2015-07-19 21:53:31 CEST