quick branch idea -- use external Durus

[Matthew Scott]

Now that Schevo has been setuptools-ized for quite some time, I think
we should explore the idea of using a specific version of Durus as an
'install_requires' dependency in Schevo, rather than keeping it in
schevo.store.

If we did this, we'll need to do some sys.modules hacks to ensure
that existing Schevo databases that have references to schevo.store.*
classes will transparently use Durus classes.

For a given release of Schevo, it would be pinned to an exact version
of Durus to ensure stability, but this would certainly make it easier
to update Schevo to use the latest Durus now (which it isn't yet) as
well as in the future.

--
Matthew Scott
***@springfieldtech.com

[Ilias Lazaridis]

Now that Schevo has been setuptools-ized for quite some time, I think we
should explore the idea of using a specific version of Durus as an
'install_requires' dependency in Schevo, rather than keeping it in
schevo.store.
If we did this, we'll need to do some sys.modules hacks to ensure that
existing Schevo databases that have references to schevo.store.* classes
will transparently use Durus classes.
For a given release of Schevo, it would be pinned to an exact version of
Durus to ensure stability, but this would certainly make it easier to
update Schevo to use the latest Durus now (which it isn't yet) as well
as in the future.

Durus should be of course decoupled, as it _is_ an external dependency.

http://audit.lazaridis.com/schevo/wiki/SchevoSubsystems

.