meejah

Okay, I did that and released 17.3.0

Thanks for the report! I think all that needs to happen is an Autobahn release containing dd1cff8f9480a125e510108482bfaf5b9eedc916

I think anyone doing a fresh install of autobahn (or anything requiring it) right now will get the newest txaio, which will not work. But yes, limiting txaio to

@jchampio can you describe what you did? I did `pip install autobahntestsuite` in a fresh virtualenv and get the correct txaio version (2.1.0).

@warner any opinions? would this have made Foolscap's tor-support easier..?

Thanks for the clear report! This does indeed sound like a bug. (Sorry for the delay responding. I believe I now have a better way to pay attention to github...

I'm not sure what we can/should do here? In Python3, `str` is basically the same as `unicode` in Python2: a string with some encoding. We're just assuming everything is UTF8...

The reason I think py3-str or unicode is the right answer for GETINFO (and most other things in tor-control-protocol) is because they're "things that get shown to users, or typed...

:+1: this sounds like a great idea. Also probably fairly easy, great for anyone looking for a "first txtorcon PR".

Hi @KyleRConway, great! If you use IRC, the best way to real-time chat with me is to join the `#tor-dev` channel on the OFTC network (I'm "meejah" there). Or we...