[tahoe-lafs-trac-stream] [pycryptopp] #107: Older versions of pycryptopp have a newer-looking version number

[pycryptopp]

#107: Older versions of pycryptopp have a newer-looking version number
-------------------------+-----------------
     Reporter:  exarkun  |      Owner:
         Type:  defect   |     Status:  new
     Priority:  blocker  |  Milestone:
      Version:           |   Keywords:
Launchpad Bug:           |
-------------------------+-----------------
 The current release of pycryptopp on pypi is
 0.7.1.869544967005693312591928092448767568728501330214

 I assume the release was generated from the revision at the git tag
 pycryptopp-0.7.1

 The git tag pycryptopp-0.7.1 is about 4 revisions behind master at HEAD right
 now.  The self-reported version of pycryptopp at master at HEAD is
 0.7.1.4.182880377279460454774209806269619214747373856330.post4

 {{{
 >>> from packaging.version import Version
 >>> release =
 Version("0.7.1.869544967005693312591928092448767568728501330214")
 >>> head =
 Version("0.7.1.4.182880377279460454774209806269619214747373856330.post4")
 >>> versions = [release, head]
 >>> versions.sort()
 <Version('0.7.1.869544967005693312591928092448767568728501330214')>]
 >>> versions == [head, release]
 True
 >>>
 }}}

 The actually newer code has a version that marks it as being older.
 Perhaps this only affects postX versions but that's sufficient to break
 testing environments where it becomes difficult to get an in-development
 version of pycryptopp instead of the last release.

--
Ticket URL: <https://tahoe-lafs.org/trac/pycryptopp/ticket/107>
pycryptopp <https://Tahoe-LAFS.org/trac/pycryptopp>
python bindings to the (C++) "Crypto++" library