Christopher Armstrong

@funkyfuture Cerberus's behavior is inconsistent with your analysis: > your schema snippet says, the value can be None AND (must be a string OR a number). What does a schema...

You probably want to be using `sync_perform`, not `perform`. Perhaps I should have made `perform` have the behavior of `sync_perform` by default, and called the core function `async_perform`. I can't...

(also note the difference between `sync_perform` and `sync_performer`. Sorry.)

Yeah, I think at the very least the docs should show usage of `sync_perform` instead of `perform`. As far as having `perform` raising errors, that's not possible in general. `sync_perform`...

Yeah, sure. The problem is that most of the time (when things are actually asynchronous) the exceptions happen after `perform()` has returned. Now that I think of it it may...

yep. sounds good. It'll technically backwards incompatible because perform may start raising exceptions when previously it wasn't. My gut feeling is that it should be fine especially because very few...

@ckp95 yeah, sure, that makes sense. There are two strategies I have used: 1. I think the simplest and most practical is to write test utility functions that correspond to...

That's interesting, I didn't realize that it would be possible. I need to look in to how async/await in Python works, I haven't really looked at it.

Ah, okay. Would this be possible with specialization? I think a good place for a note would be in the documentation for `Error`, both library and in the guide.

Would this also have scope for customizing things other than strings? For example there are situations where using single-line `{}` or `[]` constructs for small structures would drastically reduce the...