Merging forces

Hi,

I am one of the authors of python-etcd and I have written a very crude client for etcd3 as well, which I was going to publish when I got some of the parts there to work better.

Would you like me to submit pull requests with parts of my code that are (IMHO) more complete to your current implementation? If so, what I have to offer is the following:
- Cluster discovery via DNS or a list of endpoints can be passed, then the client autodiscovers the cluster and will reconnect to another server in case of failure, pretty much how python-etcd does
- Some transaction-related syntactic sugar
- Some of the methods implementation that lack some features in your code

What I, unluckily, was unable to make work are two things that are pretty important:
- Auth (I am able to authenticate, but then I can't figure out how to use the resulting token in subsequent requests)
- Watch (watch is simply broken even with py-grpc 1.0.0 and I didn't have time to look at it thoroughly)

Let me know if you're interested!

G

Start by reviewing the current etcd3 client implementation and comparing it with the proposed cluster discovery, reconnection, transaction, authentication, and watch work. The issue names no files or tests and has no settled scope, so maintainers must define the target features and acceptance criteria before implementation can begin.

Written by the indexing model from the issue text.