Added pem data

[spacemanspiff2007]

Pull Request Check List

This is just a friendly reminder about the most common mistakes. Please make sure that you tick all boxes. But please read our contribution guide at least once, it will save you unnecessary review cycles!

If an item doesn't apply to your pull request, check it anyway to make it apparent that there's nothing left to do.

• [x] Added tests for changed code.
• [x] Updated documentation for changed code.
  • [x] New functions/classes have to be added to docs/api.rst by hand.
  • [x] Changed/added classes/methods/functions have appropriate versionadded, versionchanged, or deprecated directives. Find the appropriate next version in our __init__.py file.
• [x] Documentation in .rst files is written using semantic newlines.
• [x] Changes (and possible deprecations) are documented in the changelog.

If you have any questions to any of the points above, just submit and ask! This checklist is here to help you, not to deter you from contributing!

[spacemanspiff2007]

Closes #73

[spacemanspiff2007]

how would you feel about adding a decoded_payload too?

Maybe use payload_raw and payload_bytes? Or rather payload_decoded?

[hynek]

I think payload_decoded is more precise/obvious, yes!

[spacemanspiff2007]

Like this?

[hynek]

(I understand now why you put it into the breaking section :) – I kinda didn't consider the constructor to be a public API, but 101% someone somewhere is doing just that)

[hynek]

as a heads up: while making is compatible, I've decided the churn isn't worth it and switched to a lazy extraction in 0a9780a, I hope you can live with that.

[spacemanspiff2007]

Yes - of course! Thanks for the heads up