- Both ZODB4/ZODB5 were started to be supported since 7502fa4f (tox tests with zodb4),
- PyPy started to by supported since 6c46a29d (Added pypy to tox and travis),
- ``demo:`` URI resolver was added in 2f02bc90 (demo: URI resolver).

Bump next version due to the new features.

/reviewed-by @bertjwregeer
/reviewed-on https://github.com/Pylons/zodburi/pull/29#issuecomment-836915440

demo: URI resolver

This patch adds `demo:` URI scheme to create DemoStorage from an URI.

While several existing resolvers already handle ?demostorage argument to
wrap itself with DemoStorage and in-RAM MappingStorage for changes, this
approach has the following drawbacks:

- every resolver must do it
- it is not possible to create DemoStorage with non-MappingStorage for changes.

My particular motivation here is Wendelin.core 2: it spawn WCFS
filesystem server to serve array data from ZODB storage, and passes
storage URL to spawned wcfs process, so that wcfs could connect and
retrieve data from the same ZODB storage that client process is
using. When original ERP5 client is using DemoStorage, both `base` and
`changes` must be persisted because if changes would be in-RAM
MappingStorage, WCFS could not access that data because it runs as a
separate process.

To build a DemoStorage URI we follow XRI Cross-references approach to
embed URIs for base and changes into combining demo URI:

    demo:(base_uri)/(δ_uri)

https://en.wikipedia.org/wiki/Extensible_Resource_Identifier provides
some related details and examples.

I choose fragments as the place for ZODB.DB arguments:

    demo:(base_uri)/(δ_uri)#dbkw...

The reason fragments - instead of parameters - are used, is because
DB arguments are _local_. Even with different DB arguments the URI
refers to the same storage, and for wendelin.core 2 it is important to
be able to determine whether two client processes actually use the same
underlying ZODB storage, even if those two clients use different local
parameters, like connection_pool_size and similar. Keeping such local
arguments in fragments makes it easy to determine the underlying URI of
the storage - by dropping fragments. It also follows logic from RFC 3986,
which says that "fragment ... may be ... some view on representations of
the primary resource": https://tools.ietf.org/html/rfc3986#section-3.5

Thanks beforehand,
Kirill

/cc @tseaver, @azmeuk, @jimfulton

P.S.

It was already suggested several times to add DemoStorageURIResolver and
deprecate ?demostorage in existing URI resolvers:

https://github.com/Pylons/zodburi/pull/25#issuecomment-485506959
https://github.com/Pylons/zodburi/pull/25#issuecomment-511480572
https://github.com/Pylons/zodburi/pull/25#issuecomment-622931793

- Drop support for 3.4.
- Add support for 3.8

Co-Authored-By: Tres Seaver <tseaver@palladion.com>

Added pypy and pypy3 tests

Add tests for zodb4.

Garden changelog since 2.3.1.

Annual housecleaning

Fix PendingDeprecationWarning about cgi.parse_qsl

- Do not use smart quotes

- Perpetual year in copyright
- Current version
- Clean up imports and calls

I was running py.test based tests on a project which uses zodburi and
got many warnings:

	.../python2.7/site-packages/zodburi/resolvers.py:86: PendingDeprecationWarning: cgi.parse_qsl is deprecated, use urlparse.parse_qsl instead
	  kw = dict(parse_qsl(query))

Since for Python2 cig.parse_qsl was migrated to urlparse.parse_qsl in 2008:

	https://github.com/python/cpython/commit/c585df9476

it is safe to change to urlparse.parse_qsl unconditionally.

Fix typo in Trove classifiers.

zeo: Fix parsing URI with IPv6 address

The code was crashing this way:

---- 8< ----
======================================================================
ERROR: test_call_ipv6 (zodburi.tests.test_resolvers.TestClientStorageURIResolver)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/kirr/src/wendelin/venv/z-dev/local/lib/python2.7/site-packages/mock/mock.py", line 1305, in patched
    return func(*args, **keywargs)
  File "/home/kirr/src/wendelin/z/zodburi/zodburi/tests/test_resolvers.py", line 265, in test_call_ipv6
    factory, dbkw = resolver('zeo://[::1]:9090?debug=true')
  File "/home/kirr/src/wendelin/z/zodburi/zodburi/resolvers.py", line 141, in __call__
    host, port = netloc.split(':')
ValueError: too many values to unpack

======================================================================
ERROR: test_call_ipv6_no_port (zodburi.tests.test_resolvers.TestClientStorageURIResolver)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/kirr/src/wendelin/venv/z-dev/local/lib/python2.7/site-packages/mock/mock.py", line 1305, in patched
    return func(*args, **keywargs)
  File "/home/kirr/src/wendelin/z/zodburi/zodburi/tests/test_resolvers.py", line 258, in test_call_ipv6_no_port
    factory, dbkw = resolver('zeo://[::1]?debug=true')
  File "/home/kirr/src/wendelin/z/zodburi/zodburi/resolvers.py", line 141, in __call__
    host, port = netloc.split(':')
ValueError: too many values to unpack
---- 8< ----

Fix it by leveraging the fact that urlparse.urlsplit return() tuple-like object
with additional .hostname and .port attributes which already parse IPv6 correctly:

In [2]: u = urlsplit('http://[::1]:5553')

In [3]: u
Out[3]: SplitResult(scheme='http', netloc='[::1]:5553', path='', query='', fragment='')

In [4]: u.netloc
Out[4]: '[::1]:5553'

In [5]: u.hostname
Out[5]: '::1'

In [6]: u.port
Out[6]: 5553

In [7]: u = urlsplit('http://[::1]')

In [8]: u.hostname
Out[8]: '::1'

In [9]: u.port

In [10]: repr(u.port)
Out[10]: 'None'