two (minor) bug reports:

  v0.6.0.1206569328141510525648634803928199668821045408958 is a
  ridiculous version number.  I am reminded of people asking how to
  force RCS revisions of all files to be 2.0 for their 2.0 release.
  Version numbers should conform to the norms of the rest of the world,
  and it's of course fine to have a tag in git.

  https://tahoe-lafs.org/trac/pycryptopp does not contain a link to
  download a tarball.

Attachment: pgpqGm99NDFQm.pgp
Description: PGP signature

_______________________________________________
tahoe-dev mailing list
tahoe-dev@tahoe-lafs.org
http://tahoe-lafs.org/cgi-bin/mailman/listinfo/tahoe-dev

Reply via email to