paylogic / pip-accel

71%

master: 92%

LAST BUILD ON BRANCH 0.14

branch: 0.14

CHANGE BRANCH

x

Reset

• 0.14
• 0.12.1
• 0.12.10
• 0.12.11
• 0.12.2
• 0.12.3
• 0.12.4
• 0.12.5
• 0.12.6
• 0.12.7
• 0.12.8
• 0.12.9
• 0.13
• 0.13.1
• 0.13.2
• 0.13.3
• 0.13.4
• 0.13.5
• 0.14.1
• 0.14.2
• 0.15
• 0.16
• 0.17
• 0.18
• 0.19
• 0.19.3
• 0.20
• 0.21.1
• 0.22
• 0.22.1
• 0.22.2
• 0.22.3
• 0.22.4
• 0.22.5
• 0.23
• 0.24
• 0.25
• 0.26.1
• 0.26.2
• 0.26.3
• 0.27
• 0.27.1
• 0.28
• 0.28.1
• 0.28.2
• 0.28.3
• 0.29
• 0.29.1
• 0.29.2
• 0.29.3
• 0.30
• 0.31
• 0.31.1
• 0.32
• 0.32.1
• 0.33
• 0.33.2
• 0.33.3
• 0.33.4
• 0.34
• 0.35
• 0.36.1
• 0.36.2
• 0.37
• 0.37.1
• 0.38
• 0.39
• 0.40
• 0.41
• 0.42
• 0.42.1
• 0.42.2
• 0.42.4
• 0.42.5
• 0.43
• HEAD
• master
• windows-support

Build # 50

Build Type

push

travis-ci

Committed by xolox

Commit Message

Merge pull request #33: Amazon S3 cache support

See also pull request #33 on GitHub:

  https://github.com/paylogic/pip-accel/pull/33

As discussed in the pull request I definitely see the value of being
able to keep the binary cache in Amazon S3. What I didn't like about the
pull request was that it introduced a call to store_file_into_s3_cache()
inside the module pip_accel.bdist. Conceptually that module has
absolutely nothing to do with Amazon S3 so that had to change :-)

This change set merges pull request #33 but also introduces a new
pluggable cache backend registration mechanism that enables cache
backends to be added without changing pip-accel. This mechanism uses
setuptools' support for custom entry points to discover the relevant
modules and a trivial metaclass to automagically track cache backend
class definitions.

The local binary cache backend and the Amazon S3 cache backend
(introduced in the pull request) have been modified to use the pluggable
registration mechanism. Maybe more backends will follow. We'll see :-)

Run Details

475 of 671 relevant lines covered (70.79%)

2.11 hits per line