[tahoe-lafs-trac-stream] [pycryptopp] #90: upgrade versioneer

[pycryptopp]

#90: upgrade versioneer
-------------------+---------------------
Reporter:  zooko   |          Owner:
    Type:  defect  |         Status:  new
Priority:  major   |      Milestone:
 Version:  0.5.29  |     Resolution:
Keywords:          |  Launchpad Bug:
-------------------+---------------------

Comment (by nejucomo):

 I like having the commit hash in the version from the standpoint of
 "coolness".  The purported advantage is that no two releases from
 different revisions will have colliding versions.  Also, it is
 theoretically possible to find the git revision starting from the package
 version.

 It does present a problem for making frequent releases and using a tool
 like `pip` to install those releases, because version comparison means the
 least significant releases may have a "smaller" version than releases from
 older revisions.

 A funny idea is to put a file with random entropy, or add entropy to the
 commit comment, such that the integer encoding of the git revision
 increases with every micro commit.  A commit hook would repeatedly
 generate commits until the version number increases, at the expensive of
 fossil fuels and sanity.

-- 
Ticket URL: <https://tahoe-lafs.org/trac/pycryptopp/ticket/90#comment:2>
pycryptopp <https://tahoe-lafs.org/trac/pycryptopp>