Mailing-List: contact reviews-help@spark.apache.org; run by ezmlm
Precedence: bulk
From: Stibbons <git@git.apache.org>
To: reviews@spark.apache.org
Reply-To: reviews@spark.apache.org
References: <git-pr-14963-spark@git.apache.org>
In-Reply-To: <git-pr-14963-spark@git.apache.org>
Subject: [GitHub] spark issue #14963: [SPARK-16992][PYSPARK] Virtualenv for Pylint and pep8 in...
Content-Type: text/plain
Message-Id: <20161008124437.6D7B3DFE65@git1-us-west.apache.org>
Date: Sat,  8 Oct 2016 12:44:37 +0000 (UTC)
archived-at: Sat, 08 Oct 2016 12:44:40 -0000

Github user Stibbons commented on the issue:

    https://github.com/apache/spark/pull/14963
  
    sorry I wrote on the wrong pull request, I was talking about the virtualenv support for executor (#14180) :(
    This one is indeed only to reenable pylint. Merging this would allow me to submit new patch with minor code style corrections, and get rid of this weird manual pep8 package download. virtualenv and pip have been made to make life of python developers easy, make deployment reproductible and cheap to maintain, I just would like to instill this to the Spark project. There are many reason why playing with the PYTHONPATH is wrong.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

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