meejah

If you don't know Twisted or async programming and want to learn more about that aspect, this is a great tutorial: http://krondo.com/an-introduction-to-asynchronous-programming-and-twisted/

I agree that passing un-sanitized strings as endpoint specifiers may indeed result in surprising behavior. Any code that uses Twisted endpoints would end up passing the strings to `clientFromString` or...

Note that you should treat a colon (:) as illegal for individual args as you're building up (sanitized) endpoint strings, as Twisted uses those to delimit options in the strings.

Bump: this is an interesting issue, but I don't have a good answer yet. Since it was filed, though, the documentation (on master) is mostly-new. Perhaps now there's a good...

Hi. I'm definitely not opposed to making those things optional -- is there already a 'standard' way to do this with setuptools / setup.py that would work for your use-case?

Yes, I think this is a good idea. It's actually slightly more complicated than that: tor insists that the _parent_ directory of a unix-socket used for this be owned by...

There are now `TorState.from_protocol()` and `TorConfig.from_protocol()`. Are there any others? (The goal here is to elminate any need to mess with `.post_bootstrap` attributes ever, which is a bad pattern for...

We've also added `connect` and `launch` which are nice high-level APIs where you don't muck about with .post_bootstrap either.

The "real" way we should do this is to do away with ".bootstrap" altogether. The factory-functions should gather up any data required and pass it to the constructor for `TorState`...

This is partially done (there are factory methods) but we should also: deprecate `.bootstrap` and do the other refactorings mentioned (i.e. instead of `TorState` implementing its own "bootstrap" methods, we...