How do I verify a
Just some documentation fixes. Largely released so there is a stable release with an extension module built for Python 3.5 (Ubuntu Wily).
* Use `dbase32.using_c_extension` flag to determine whether the Dbase32 C implementation is being used:
* Fix some documentation typos
Add a quick test to make sure the Dbase32 C extension is being used rather than the pure-Python fallback.
For more details, please see the Dbase32 changelog:
Now that lp:1264618 has been fixed, re-enable directory rename tests in unit tests:
Small documentation updates, otherwise no change.
* Big update to documentation: http://docs.novacut.com/filestore/index.html
* All Sphinx doctests now pass, and are automatically run during the build
* `FileStore.verify_and_move()` now accepts an `io.BufferedWriter` for the *tmp_fp*, in the same way that `FileStore.hash_and_move()` has for some time
* Rename `misc.write_files()` to more apt `misc.write_test_vector_files()`, important especially now that it's documented
* `setup.py test` now does static analysis with `pyflakes3`
* Fix a number of small issues in filestore/tests/*.py found by pyflakes
* setup.py: strictly require python >= 3.4 as we wont be testing with 3.3 anymore
* A number of improvements and fixes in the filestore/protocols.py docstrings:
* Unconditionally run full test for 'dmediasum --version' as we dropped Python 3.3 support (what argparse outputs to stderr vs stdout changed in this case between Python 3.3 and 3.4)
* Disable part of FileStore.statvfs() test that tended to fail frequently on the build servers
* Update test for `dmediasum` script as in Python 3.4, argparse --version now outputs to stdout instead of stderr
Disabled part of the _create_filestore() unit test that was failing on Python 3.4 Beta3 because of this Python 3.4 bug:
Otherwise, no change.