Comment 1 for bug 1646320

So what's the scope involved here? Patch Python to do something better with error codes, then move Swift to only support py36+? Roll our own (C-based?) SQLite lib?

I agree that the current situation isn't great, but I'm not really seeing a better way forward. *Maybe* we could look for some particular instances (IntegrityError, maybe? Given that DatabaseError is the default, that seems too broad... we *have* to go digging through strings)

Meanwhile, by falling back to reraising, we get noisy logs that prompt us to shore up the gaps pretty quickly when they come up. Three days from bug report to fix merged seems not bad... I kinda wanna just close as Won't Fix.