Andy Gayton

@asteven I think that test plan is great, and sufficient.

@asteven I think our two choices are: - just go for it, and hope no-one is effected - do one release that keeps the current behavior, but logs a deprecation...

Yeah, it's not too unruly for my subjective tastes, but it's definitely on the edge. We're at 1740 lines now. You're thinking split it by top level endpoint? `kv`, `event`,...

I think the time has come to make this split. I'm thinking: 1. make the spilt by top level endpoint name 2. think through if there's something we could do...

An example of where it's currently easy for endpoints do not get consistent treatment: https://github.com/cablehead/python-consul/issues/116

This is just awful. I hate magic. But just brain storming ways to make it easy to consistently and explicitly apply parameters - while preserving method signature and docstrings for...

The internals and api are currently being iterated on rapidly. As they begin to stabilize I'll look into this.

This is very related to: https://github.com/cablehead/python-consul/pull/70 Need to think through a comprehensive plan to handling time values consistently and sanely.

I think it's overkill for `python-consul` to use `requests`. The needed usage is so small, we don't really need the nicer api that `requests` provides. I think the way to...

> Hopefully that wasn't too much craziness and I didn't skip anything important. Let me know if you have any questions about all that. This is a very helpful work...