2.60 throws an exception if the message is a non-empty string

[oschwald]

This is a reasonably significant change in behavior that caused a number of breakages for us. I don't think the behavior is necessarily wrong, but it is a breaking change without being mentioned in the Changes and without an appropriate version bump.

[autarch]

Ah, that wasn't really intentional. I'll change it to accept an empty string again.

[oschwald]

After looking more closely into the error, I think the equivalent ident change is what is actually causing the most issues, primarily in test code.

[oschwald]

Thanks for fixing that!