Foolscap-0.10.1 released

[Brian Warner]

I made another Foolscap release, with just one fix: the __version__
string in builds made from tarballs (but not git checkouts) was unicode,
which broke some unit tests, and would probably break use of `flogtool
tail` and the LogPublisher mechanism.

The underlying cause is a non-trivial design question for Versioneer:
should versions be strings? or bytes? Since Foolscap is py2-only the
question is kind of moot, but Versioneer is py2+py3. In the py3 world
"string" (i.e. unicode) is the most obvious answer. In py2 I think
"string" (i.e. bytes) is the most obvious answer. But versions are
derived from git tags and directory names, and both can sometimes be
non-ASCII, so it's not cut-and-dried. Please comment on the bug[1] if
you have some thoughts on the matter.

Anyways, Foolscap-0.10.1 is out which fixes this, and hopefully this
will resolve the debian issue. Grab it from PyPI as usual.


NEWS:

* Release 0.10.1 (21-Jan-2015)

** Packaging Fixes

This release fixes a version-string management failure when the "log
publisher" feature was used in a tree built from a release tarball (rather
than from a git checkout). This caused a unit test failure, as well as
operational failures when using `flogtool tail`. Thanks to Ramakrishnan
Muthukrishnan (vu3rdd) for the catch and the patch. (#248)


cheers,
 -Brian

[1]: https://github.com/warner/python-versioneer/issues/71