Currently, if you install the GitHub version of bpython, the version is identified as mercurial. This has two downsides. The first obvious, but the second is it makes pip list --outdated act a bit strange. It will always show the same thing no matter how up to date your GitHub version is:

$ pip list --outdated
bpython (Current: mercurial Latest: 0.13.1)

It would be nice if bpython used a versioning scheme compatible with distutils.version.StrictVersion (like 0.14a0 assuming that is what the master branch represents):

    class StrictVersion(Version)
     |  Version numbering for anal retentives and software idealists.
     |  Implements the standard interface for version number classes as
     |  described above.  A version number consists of two or three
     |  dot-separated numeric components, with an optional "pre-release" tag
     |  on the end.  The pre-release tag consists of the letter 'a' or 'b'
     |  followed by a number.  If the numeric components of two version
     |  numbers are equal, then one with a pre-release tag will always
     |  be deemed earlier (lesser) than one without.
     |
     |  The following are valid version numbers (shown in the order that
     |  would be obtained by sorting according to the supplied cmp function):
     |
     |      0.4       0.4.0  (these two are equivalent)
     |      0.4.1
     |      0.5a1
     |      0.5b3
     |      0.5
     |      0.9.6
     |      1.0
     |      1.0.4a3
     |      1.0.4b1
     |      1.0.4