xolox / python-humanfriendly

96%

master: 93%

LAST BUILD ON BRANCH 1.35

branch: 1.35

CHANGE BRANCH

x

Reset

• 1.35
• master
• 1.8.1
• 1.8.2
• 1.8.3
• 1.8.4
• 1.8.5
• 1.8.6
• 1.9
• 1.9.1
• 1.9.2
• 1.9.3
• 1.9.4
• 1.9.5
• 1.10
• 1.9.6
• 1.11
• 1.12
• 1.13
• 1.14
• 1.16
• 1.17
• 1.19
• 1.20
• 1.21
• 1.22
• 1.23
• 1.23.1
• 1.24
• 1.25
• 1.25.1
• 1.26
• 1.27
• 1.37
• 1.38
• 1.39
• 1.40
• 1.41
• 1.42
• 1.43
• 1.43.1
• 1.44.1
• 1.44.3
• 1.44.4
• 1.44.5
• 1.44.6
• 1.44.7
• dev

Build # 93

Build Type

push

travis-ci

Committed by xolox

Commit Message

Issue #6: Support for milleseconds in timespan parsing/formatting

Technically speaking this breaks backwards compatibility but only
by dropping a nasty (_not_ documented) implementation detail.
Quoting from the old code:

  # All of the first letters of the time units are unique, so
  # although this check is not very strict I believe it to be
  # sufficient.

That no longer worked with [m]illiseconds versus [m]inutes as was
also evident from the feature request / bug report on GitHub.

Run Details

8 of 8 new or added lines in 1 file covered. (100.0%)

631 of 658 relevant lines covered (95.9%)

3.8 hits per line