Ian Denhardt

Yeah, that looks like some kind of transient network failure. I just restarted the build, we'll see how it goes.

Failed again. Related: https://github.com/travis-ci/travis-ci/issues/9112 But I think this may not be the only issue. I just pushed another commit that tries using 3.4; see the comment there. We'll see if...

Works for me. Quoting Lucas H. Xu (2018-03-06 14:08:56) > Should we use this issue to keep track of the Python 3 support? We just > started

So, we should probably come up with a triage strategy for this; we're running the CI against python 3, but that as far as I can see nobody (including myself)...

It's a bit hard to just enumerate a list when what we're seeing is a test suite that fails up-front. Right now we're getting an error early on. Ideally we'd...

Bringing this up again, I'd like to start tackling this. We've got some time, but I'd like to switch over before python 2.7 goes EOL in 2020. This isn't as...

There's no entry for 0.5 yet, because this will be the first user-visible change we've merged so far (@naved001 tagged 0.4 just the other day). So you'll have to add...

I don't see any reason to keep it admin-only, though we'd definitely want to change it to operate on nics instead of ports. I think this is an artifact of...

I don't know that there's anything "standard." setting the Warning header sounds like a good idea, and we could modify the client lib and cli to log a warning header...

I think making the privileged role configurable is a good idea. The patch would be trivial.