store an 'archive' flag in the guarddb, so the full list of archive channels
is:

  [chan for chan, data in db.guarddb if data.get('archive')]

This involves moving the _N and _S channels back into the db
definition, which I think is not tragic.

Apparently the change in 2456a737 did have a
negative impact after all.  python3 requires all relative imports to
be explicit, which is presumably why they drop the level=-1 option.
But the option is still needed for python2.

Rather than try to recreate the defaults just capture them with
**kwargs and pass them on appropriately.  Fixes #3.

This removes the provided scripts in favor of using setuptools entry_points.
This requires modifying the tests to not depend on the previously provided
scripts.

somehow python2/3 difference

fixes error in python3

newer networkx versions don't have the same problem.

don't require loading daemon (since it imports ezca for not particularly
good reason), but requires enumerating options explicitly
here.

would be better if daemon didn't import ezca

python3 has builtins, instead of __builtin__ in python2.  This is mostly a
straight compatibility.  "reload" is not a built-in in python3, so we have
to also pull that from importlib.

This is NOT an overhaul of the whole import custom import handling, it just
allows for guardian to be imported by python3.

This includes one change that could affect python2: setting default level=0.
python3 builtins.__import__ does not support level=-1, which tells import
to automatically handle both absolute and relative imports.  Since we're only
doing absolute imports it should be safe to set this to 0.  Hopefully this
won't cause any problems.

This latest pcaspy release fixes redundant updates after initialization

This cleans up how REQUEST and REQUEST_ENUM records are updated, to
eliminate possible redundant updates.

Two main changes here:
* upstream adds Driver.setParamEnums() to update enum records
* upstream fixes to remove redundant updates

The later accounts for test suite changes.

However, there are still some race condition issues in upstream related to
updates that can occasionally result in double updates:

https://github.com/paulscherrerinstitute/pcaspy/pull/49

This issue results in occasional test suite failures (at the ~20%
level).

Hopefully these issues will be fixed in future upstream updates.

eliminate redundant confusing env file

Remove the command from the runit finish script that emails me.  This
was used during prototyping but is no longer needed.