We have been registering our custom level names ("BLATHER", "TRACE) in the
wrong order since 2004.  Before Python 3.4, the stdlib ``logging`` module
masked the error by registering them in *both* directions.

'width=1' causes excess wrapping.

See: http://blog.travis-ci.com/2014-12-17-faster-builds-with-container-based-infrastructure/

Downloaded from http://downloads.buildout.org/2/bootstrap.py

Small fixups while learning ZODB

As noted in recent commit, verbose option handling in fsrefs.py was
broken. On review Tres suggested to make VERBOSE a local variable as
currently it is used only in one function main().

Suggested-by: Tres Seaver

Currently that script does not run because of import error:

    $ python src/ZODB/scripts/netspace.py
    Traceback (most recent call last):
      File "src/ZODB/scripts/netspace.py", line 13, in <module>
        from ZODB.referencesf import referencesf
    ImportError: No module named referencesf

and that ZODB.referencesf module was moved to ZODB.serialize long ago in

    ec014812    (Move referencesf to ZODB.serialize.)
    ae7e113e    (Ack!  Deleted the wrong file in the last checkin.)
    355ff4ac    (One more try.  Commit the version with referencesf.)

only the conversion missed the netspace.py script.

Fix it.

provide more information when logging setstate failures

For this script verbose mode was added in 57bca1f0 (Add -v option to
control whether tracebacks are printed.) and was later broken in
6dd809d2 (Converted to a buildout and converted externals to
dependencies.) - the change forgot to add global specifier for VERBOSE
variable while moving its assignment into function context.

As a result currently we have

    $ python ./src/ZODB/scripts/fsrefs.py -v data.fs
    Traceback (most recent call last):
      File "./src/ZODB/scripts/fsrefs.py", line 155, in <module>
        main()
      File "./src/ZODB/scripts/fsrefs.py", line 104, in main
        VERBOSE += 1
    UnboundLocalError: local variable 'VERBOSE' referenced before assignment

Fix it.

Fix for #16

Thanks!

see https://github.com/zopefoundation/ZODB/issues/16

see https://github.com/zopefoundation/ZODB/issues/16

For pypy, set the persistent_id attribute of the pickler, since it uses a python implementation even in Py2

This adds 'repozo --verify' to check your backup integrity

Extract size/checksum computation logic into separate functions for
gzipped and non-gzipped files.

Could be used as a workaround for https://bugs.launchpad.net/zodb/+bug/906057

Should fix http://winbot.zope.org/builders/ZODB_dev%20py_265_win32/builds/1086/steps/test/logs/stdio

Should fix a test failure on Windows:
http://winbot.zope.org/builders/ZODB_dev%20py_265_win32/builds/1083/steps/test/logs/stdio

Also, avoid shadowing the 'file' builtin / alias with locals.