Yasuhito FUTATSUKI wrote on Wed, 16 Oct 2019 04:40 +00:00:
> On 2019/10/16 10:36, Daniel Shahaf wrote:
> > Yasuhito FUTATSUKI wrote on Tue, Oct 15, 2019 at 16:19:46 +0900:
> >> On 2019-10-15 07:04, Daniel Shahaf wrote:
> >>> Yasuhito FUTATSUKI wrote on Sun, 13 Oct 2019 04:01 +00:00:
> >>>> On 2019/10/13 7:24, Daniel Shahaf wrote:
>
> >>> Also, what about the svnadmin_tests.py patch you posted upthread? Is
> >>> there a reason not to go ahead and commit it to trunk? (and even nominate
> >>> it for backport in 1.13.x/STATUS)
> >>
> >> I think that is no probrem.
> >
> > Let me elaborate. By my reckoning, «make check» on trunk has a false positive
> > when ${PYTHON} is python3; and furthermore, python2 will reach EOL during the
> > lifetime of the 1.13 branch; therefore, we should fix the false positive and
> > backport the fix to supported branches. What's your view?
>
> I agree with you, because I think we should publish at least one relase
> support Python 3, so that we can remove the sentence "Note that Python 3.x
> is not supported and most likely won't work." in "Dependencies in Detail"
> section of INSTALL file, before EOL of Python 2.
Good catch. Yes, we should update INSTALL to reflect that Python 3 is
supported for the build and test process, even if it's not yet supported
by the swig bindings in trunk and 1.13.x. Would you be able to update
that? You're welcome to just commit changes to trunk/INSTALL directly,
if that's easier for you.
As to the test suite patches, I think they're ready to be committed,
aren't they?
Thanks,
Daniel
Received on 2019-10-16 09:55:55 CEST