Open mlavin opened 6 years ago
Looks like this breaks Python 2 ¯_(ツ)_/¯
It seems like your changes could be a fork for a REAL python 3 version of encrypted fields... With the python3 changes to strings/bytes/unicode, it seems unreasonable to make the encryption library backwards compatible rather than just forking and hosting a separate python3 version, imo!
@mlavin If you haven't discovered this on your own yet, you don't need this guy's package anymore as django-extensions 2.0.0 and above offers encrypted fields support.
This builds off of the previous WIP for Python 3 and uses a version of python-keyczar which supports Python 3. Everything seems to work correctly on Python 3.5 and Django 1.11 but admittedly I haven't tested other Django versions or Python 2.