Mailing-List: contact issues-help@spark.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 9 Mar 2015 09:59:38 +0000 (UTC)
From: "Sean Owen (JIRA)" <jira@apache.org>
To: issues@spark.apache.org
Message-ID: <JIRA.12780376.1425863164000.35614.1425895178386@Atlassian.JIRA>
In-Reply-To: <JIRA.12780376.1425863164000@Atlassian.JIRA>
References: <JIRA.12780376.1425863164000@Atlassian.JIRA>
 <JIRA.12780376.1425863164550@arcas>
Subject: [jira] [Commented] (SPARK-6219) Expand Python lint checks to check
 for  compilation errors
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/SPARK-6219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14352729#comment-14352729 ] 

Sean Owen commented on SPARK-6219:
----------------------------------

Isn't this being checked already because the code is compiled to run tests? The downside is the redundancy and compiling twice, I'd imagine. Is the idea to bring forward compilation failures?

> Expand Python lint checks to check for  compilation errors
> ----------------------------------------------------------
>
>                 Key: SPARK-6219
>                 URL: https://issues.apache.org/jira/browse/SPARK-6219
>             Project: Spark
>          Issue Type: Improvement
>          Components: Build
>            Reporter: Nicholas Chammas
>            Priority: Minor
>
> An easy lint check for Python would be to make sure the stuff at least compiles. That will catch only the most egregious errors, but it should help.


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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org