All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian Clauss via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 0/1] Travis CI: Lint for Python syntax errors and undefined names
Date: Fri, 19 Jul 2019 07:18:54 -0700 (PDT)	[thread overview]
Message-ID: <pull.290.git.gitgitgadget@gmail.com> (raw)

Several things were changed between Python 2 and Python 3. Here we are
making changes to make the code run on both Py2 and Py3. We are doing this
because the end of life of Python 2 is in 167 days. We are using print() 
function because legacy print statements are syntax errors on Py3.reduce() 
was moved in Python 3 and raw_input() was removed so we make changes to
avoid NameErrors at runtime. Signed-off-by: Christian Clauss cclauss@me.com
[cclauss@me.com]

cclauss (1):
  Travis CI: Lint for Python syntax errors and undefined names

 .travis.yml                        |  4 +++
 contrib/fast-import/import-zips.py |  3 +-
 contrib/hg-to-git/hg-to-git.py     | 47 +++++++++++++++---------------
 git-p4.py                          |  3 ++
 4 files changed, 33 insertions(+), 24 deletions(-)


base-commit: 9d418600f4d10dcbbfb0b5fdbc71d509e03ba719
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-290%2Fcclauss%2Fpatch-1-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-290/cclauss/patch-1-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/290
-- 
gitgitgadget

             reply	other threads:[~2019-07-19 14:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-19 14:18 Christian Clauss via GitGitGadget [this message]
2019-07-19 14:18 ` [PATCH 1/1] Travis CI: Lint for Python syntax errors and undefined names cclauss via GitGitGadget
2019-07-19 19:44   ` Junio C Hamano
2019-07-20 12:51   ` SZEDER Gábor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=pull.290.git.gitgitgadget@gmail.com \
    --to=gitgitgadget@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.