[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):

 If pycryptopp plans to do "micro releases" such as pushing to PyPI very
 frequently, it would be best to use a
 [http://www.python.org/dev/peps/pep-0440/ PEP 0440] "development release"
 tag in the version.

 The reason is that as of `1.4rc2` (or possibly prior, but not as early as
 `1.3.1`), `pip` will *not* upgrade to "development releases" unless the
 user requests it with the `--pre` flag to `pip install`.  The thinking is
 that users will be able to decide if they want to follow "stable releases"
 or "development releases".

 So, in that scheme, the `pycryptopp` version should look like
 `0.6.0.post1206569328141510525648634803928199668821045408958` instead of
 `0.6.0.1206569328141510525648634803928199668821045408958`.

 Even without the silly hash-collision scheme above to improve the
 ordering, appending git hashes to only dev releases will help ensure
 "stable releases" are monotonically increasing.

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