{lang}[foss/2017a] Python v2.7.13

[henkela]

(created using eb --new-pr)

[boegelbot]

Travis test report: 8/8 runs failed - see https://travis-ci.org/hpcugent/easybuild-easyconfigs/builds/225712699

Only showing partial log for 1st failed test suite run 4394.1;
full log at https://travis-ci.org/hpcugent/easybuild-easyconfigs/jobs/225712700

...
FAIL: Check whether any conflicts occur in software dependency graphs.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/travis/build/hpcugent/easybuild-easyconfigs/test/easyconfigs/easyconfigs.py", line 152, in test_conflicts
    "No conflicts detected")
AssertionError: No conflicts detected

----------------------------------------------------------------------
Ran 6907 tests in 287.260s

FAILED (failures=1)
ERROR: Not all tests were successful.

• 4394.2 - errored => https://travis-ci.org/hpcugent/easybuild-easyconfigs/jobs/225712701
• 4394.3 - errored => https://travis-ci.org/hpcugent/easybuild-easyconfigs/jobs/225712702
• 4394.4 - errored => https://travis-ci.org/hpcugent/easybuild-easyconfigs/jobs/225712703
• 4394.5 - errored => https://travis-ci.org/hpcugent/easybuild-easyconfigs/jobs/225712704
• 4394.6 - errored => https://travis-ci.org/hpcugent/easybuild-easyconfigs/jobs/225712705
• 4394.7 - errored => https://travis-ci.org/hpcugent/easybuild-easyconfigs/jobs/225712706
• 4394.8 - errored => https://travis-ci.org/hpcugent/easybuild-easyconfigs/jobs/225712707
  (bleep, bloop, I'm just a bot, please talk to my owner @boegel if you notice you me acting stupid)

[boegel]

@henkela The easyconfig for this Tk version includes a dependency on zlib 1.2.8, which conflicts with the zlib used in this easyconfig file.

Besides that, any reason you are not porting the easyconfig for Python 2.7.13 we have with the intel/2017a toolchain to foss/2017a instead?

We took a slightly different approach there, by avoiding to include Tk as a dependency since that requires X11 (which is kind of silly as a dep for Python). That does mean the Tkinter part of Python is not available (see also #4225).

[henkela]

@boegel I updated my local version of Tk to use zlib 1.2.11.
I missed the 2.7.13 version because I didn't check the develop branch earlier. Sorry for that.
For easyconfigs that need other updated easyconfigs, how should I pull-request them? All needed files in one pull request?

[boegelbot]

Travis test report: 8/8 runs failed - see https://travis-ci.org/hpcugent/easybuild-easyconfigs/builds/226280310

Only showing partial log for 1st failed test suite run 4411.1;
full log at https://travis-ci.org/hpcugent/easybuild-easyconfigs/jobs/226280311

...
FAIL: Check whether any conflicts occur in software dependency graphs.
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/travis/build/hpcugent/easybuild-easyconfigs/test/easyconfigs/easyconfigs.py", line 152, in test_conflicts
    "No conflicts detected")
AssertionError: No conflicts detected

----------------------------------------------------------------------
Ran 6908 tests in 274.301s

FAILED (failures=1)
ERROR: Not all tests were successful.

• 4411.2 - errored => https://travis-ci.org/hpcugent/easybuild-easyconfigs/jobs/226280312
• 4411.3 - errored => https://travis-ci.org/hpcugent/easybuild-easyconfigs/jobs/226280313
• 4411.4 - errored => https://travis-ci.org/hpcugent/easybuild-easyconfigs/jobs/226280314
• 4411.5 - errored => https://travis-ci.org/hpcugent/easybuild-easyconfigs/jobs/226280315
• 4411.6 - errored => https://travis-ci.org/hpcugent/easybuild-easyconfigs/jobs/226280316
• 4411.7 - errored => https://travis-ci.org/hpcugent/easybuild-easyconfigs/jobs/226280317
• 4411.8 - errored => https://travis-ci.org/hpcugent/easybuild-easyconfigs/jobs/226280318
  (bleep, bloop, I'm just a bot, please talk to my owner @boegel if you notice you me acting stupid)

[boegel]

@henkela You should drop the easyconfig for Python 2.7.12 if it's no longer relevant (see http://easybuild.readthedocs.io/en/latest/Integration_with_GitHub.html#deleting-easyconfig-files-or-patches), and update the PR title.

To answer your question w.r.t. dependencies: if the total amount of easyconfigs is reasonable (say, < 10), it's OK to pack them all in a single pull request, especially if they're trivial version/toolchain updates since those are easy to review for us via --review-pr (cfr. http://easybuild.readthedocs.io/en/latest/Integration_with_GitHub.html#reviewing-easyconfig-pull-requests-review-pr).

One thing you should do is clean up the contributed easyconfig file, by removing the auto-added comments like # Built with EasyBuild and the buildstats.

[boegel]

Test report by @boegel
SUCCESS
Build succeeded for 1 out of 1 (1 easyconfigs in this PR)
node2507.golett.os - Linux centos linux 7.3.1611, Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz, Python 2.7.5
See https://gist.github.com/48cf2a3aaaffe950b61ef0f8966894f0 for a full test report.

[boegel]

Test report by @boegel
SUCCESS
Build succeeded for 1 out of 1 (1 easyconfigs in this PR)
node2109.delcatty.os - Linux centos linux 7.3.1611, Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz, Python 2.7.5
See https://gist.github.com/e6cef0f009e5c52f1900489e515e1aa6 for a full test report.

[boegel]

lgtm

[boegel]

Going in, thanks @henkela!