Joe Cross

For now I'll merge a PR that improves the error string, if you're up for making the change. I'd like to think about the larger `BloopException` change for a few...

Removing this from the 3.0 milestone, it's up for grabs in the next minor release if anyone is interested.

Should take a look at http://docs.sqlalchemy.org/en/latest/orm/extensions/mutable.html and see how mature products already do this. At a glance, any `__set__` on the field is pushed through a `coerce` to a tracking...

Ugh. Implementing this in any reasonably performant way is killed by https://forums.aws.amazon.com/thread.jspa?threadID=162907, which indicates that paths can't overlap in expressions. In other words, the following is not allowed: ``` SET...

Moving to the 2.0 milestone since there's no way it's fixed by 1.0.

Removing from the 2.0 milestone because that's within sight and a fix for this is not.

Thanks for opening an issue, sorry this is failing (and for so long!) I'll get started on a fix to remove the loop parameter and reference, this will be a...

Looking through these references: * http://ircv3.net/specs/extensions/sasl-3.1.html * https://tools.ietf.org/search/rfc4616 I think the plain sasl method could look something like this: ```python import base64 async def sasl_plain(client, authn_id: str, authz_id: str, password:...

Thanks for the comment! It's been a few years since I added this to the backlog :) I'm happy to take another look though! To help understand what's missing, can...

It's possible to collapse them into one command, but the arg parsing is non-trivial. I just started refactoring pack.py and had to look those sections up; the command is actually...