Mercurial > kallithea
comparison requirements.txt @ 8039:4e565c5d7b7d
lib: establish py3 compatible strategy for string handling: introducing safe_bytes and deprecating safe_str
The meaning of safe_str will change when moving to py3. All use of safe_str is
thus tech debt that we have to chop off, mostly by moving to either
safe_unicode or safe_bytes ... or dropping because we know what we are doing
and rely on the improved type safety in py3.
author | Mads Kiilerich <mads@kiilerich.com> |
---|---|
date | Sun, 15 Dec 2019 20:00:38 +0100 |
parents | 941548131765 |
children |
comparison
equal
deleted
inserted
replaced
8038:ed08a2117d8f | 8039:4e565c5d7b7d |
---|