Jake Peacock

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...

@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.

Will create tests to cover this new usage if you let me know whether this is an acceptable addition to the Keyword Processor.

Additionally, perhaps this could be a separate method that takes in a 'prepend' and an 'append' rather than a 'replacement' and this could eliminate the need for str.replace() in keyword.py:644