Mailing-List: contact dev-help@aurora.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aurora.incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of yasumoto7@gmail.com
 designates 209.85.192.174 as permitted sender)
MIME-Version: 1.0
From: Joe Smith <yasumoto7@gmail.com>
Date: Mon, 22 Sep 2014 12:16:27 -0700
Message-ID: 
 <CA+y6w6riswm2f0Mdid1oDvuVtD6-q_Y1mb4wNC6MSquNVTUrwA@mail.gmail.com>
Subject: Upgrading pants to pin our python interpreter version
To: dev@aurora.incubator.apache.org
Content-Type: multipart/alternative; boundary=047d7b111ed5c7702b0503ac4ac1

--047d7b111ed5c7702b0503ac4ac1
Content-Type: text/plain; charset=UTF-8

Hi all,

Pants is cutting a new release
<https://github.com/pantsbuild/pants/issues/597>, which includes the
ability to specify a repo-wide interpreter compatibility
<https://github.com/pantsbuild/pants/issues/483>. Using this feature will
decrease the impact the environment has on which interpreter is used (see
AURORA-462 <https://issues.apache.org/jira/browse/AURORA-462> and AURORA-585
<http://URORA-585> for examples) and overall increases reliability and
reproducibility.

As it ships, I propose we pin our repo at python27- are there any concerns
with doing so? Some people may still be using python26, in which case you
can change pants.ini to specify 2.6 on your internal fork, since we largely
decided to no longer support it
<http://mail-archives.apache.org/mod_mbox/incubator-aurora-dev/201407.mbox/%3cCA+y6w6oumbGoJy2B+KHS4UoPAQELSsCX4VhHa3ejakkijPb0bQ@mail.gmail.com%3e>
.

Thanks!
Joe

--047d7b111ed5c7702b0503ac4ac1--