You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by James McCoy <ja...@jamessan.com> on 2016/05/12 21:56:49 UTC
Re: svn commit: r1743550 - in /subversion/trunk: build/
contrib/server-side/ tools/client-side/ tools/dev/benchmarks/RepoPerf/
tools/dev/benchmarks/suite1/ tools/dist/
On Thu, May 12, 2016 at 07:42:36PM -0000, stefan2@apache.org wrote:
> Author: stefan2
> Date: Thu May 12 19:42:36 2016
> New Revision: 1743550
>
> URL: http://svn.apache.org/viewvc?rev=1743550&view=rev
> Log:
> Fix the usage of empty line print() under Python 2.
>
\u2026
> Modified: subversion/trunk/build/run_tests.py
> URL: http://svn.apache.org/viewvc/subversion/trunk/build/run_tests.py?rev=1743550&r1=1743549&r2=1743550&view=diff
> ==============================================================================
> --- subversion/trunk/build/run_tests.py (original)
> +++ subversion/trunk/build/run_tests.py Thu May 12 19:42:36 2016
> @@ -482,7 +482,7 @@ class TestHarness:
> for t in threads:
> t.join()
>
> - print()
> + print("")
This is another reason to use \u201cfrom __future__ import print_function\u201d.
Just because something looks the same visually doesn't mean it's the
same syntax.
Actually importing the same syntax avoids simple mistakes like this.
Cheers,
--
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <ja...@jamessan.com>