José Padilla

I think that https://github.com/evonove/django-oauth-toolkit might be the go to project now for this. Not really sure though

@bukosabino this looks good, thanks! any chance you could add some tests for this?

I have no problem following whatever we do in [DRF](https://github.com/tomchristie/django-rest-framework/blob/master/CONTRIBUTING.md).

@davidfischer-ch thanks! A small test and update the docs would make this even better.

Hey @gertjanol thanks for putting this together. I'm kind of torn and not sure what the right solution would be. This as is would be a breaking change right now....

@gertjanol I'd rather not make this type of assumption going on forward and instead enable users to override the parser however they see fit. I'm actually inclined on just adding/documenting...

@gertjanol that's right, by default this new method will just return whatever the original value was. In the release note we would have to document what the original behavior was...

I'm actually running into this too. We're using sops in development with PGP and KMS for production. KMS will always be tried first and fail while in development. A `--use-key`...

@deanmalmgren I'll try to get this done in a few.

For one thing, pyth seems to have issues with charsets on the existing RTF files in textract which will make it harder to test. Might be related to https://github.com/brendonh/pyth/pull/30