Here's an idea.

Currently, the [Sentry docs](http://sentry.readthedocs.org/en/latest/developer/client/index.html#writing-a-client) encourage you to do async submission whenever possible:

> Additionally, the following features are highly encouraged:
> - Automated error handling (e.g. default error handlers)
> - Logging integration (to whatever standard solution is available)
> - Non-blocking event submission
> - Basic data sanitization (e.g. filtering out values that look like passwords)

This is clearly the desirable configuration in 99% of production cases, but it means that simple "hey look I can send" demos don't work if you don't make your goroutine sleep.

The raven-python client only has a send method, and [automatically decides whether or not to send asynchronously based on the transport](https://github.com/getsentry/raven-python/blob/6032462a763c9f74779baa63a2f75998c2cef8ad/raven/base.py#L529). We can decide whether or not to do that in a separate issue, but I think you're right that I should change this to `Send` for now.