> My way out of this mess would be to move `signing.dumps` & `signing.loads` > onto the `Signer` class itself; this way this functionality would become > reusable while allowing to switch how signing is performed. My preference > would be to call those methods `sign_object` & `unsign_object` which would > make it clear that it will have to run some kind of serializer over it. > `signing.dumps/loads` could just call those methods then. >
It makes a lot of sense, IMO. Deprecating *signing.dumps()/loads() *is probably not necessary, we can leave them as shortcuts (you didn't suggest it, it's just my observation). Best, Mariusz -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/b7c22cef-c9f1-46ac-8304-6f63ceaa874cn%40googlegroups.com.
