Mailing-List: contact commits-help@community.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@community.apache.org
Date: Thu, 1 Oct 2015 13:36:26 +0000 (UTC)
From: "Sebb (JIRA)" <jira@apache.org>
To: commits@community.apache.org
Message-ID: <JIRA.12896269.1443135962000.1794.1443706586612@Atlassian.JIRA>
In-Reply-To: <JIRA.12896269.1443135962000@Atlassian.JIRA>
References: <JIRA.12896269.1443135962000@Atlassian.JIRA>
 <JIRA.12896269.1443135962776@arcas>
Subject: [jira] [Resolved] (COMDEV-160) Use "python3" rather than
 "python3.4" as the command name
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/COMDEV-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sebb resolved COMDEV-160.
-------------------------
    Resolution: Fixed

> Use "python3" rather than "python3.4" as the command name
> ---------------------------------------------------------
>
>                 Key: COMDEV-160
>                 URL: https://issues.apache.org/jira/browse/COMDEV-160
>             Project: Community Development
>          Issue Type: Improvement
>          Components: Projects New, Reporter Tool
>            Reporter: Sebb
>
> The crontabs currently use python3.4 to run the scripts.
> However this symlinked to python3, so the two are currently equivalent.
> Unless the scripts actually need version 3.4 - and no other - it does not make sense to use the specific version. Using python3 will make a Python upgrade much simpler - no need to edit all the crontabs, as they will pick up the whatever is the current version.
> [If a script does specifically require Python 3.4, then it should check this and report an error.]


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)