ff13d58c14
from __future__ unicode_literals leads to developer confusion as developers no longer can tell whether a bare literal string is a byte string or a unicode string. Explicit marking as u"" or b"" is the way to solve the same problem in the Ansbile codebase. |
||
---|---|---|
.. | ||
ansible-var-precedence-check.py | ||
boilerplate.sh | ||
configure-remoting-ps1.sh | ||
empty-init.sh | ||
inappropriately-private.sh | ||
integration-aliases.py | ||
line-endings.sh | ||
no-basestring.sh | ||
no-dict-iteritems.sh | ||
no-dict-iterkeys.sh | ||
no-dict-itervalues.sh | ||
no-get-exception.sh | ||
no-underscore-variable.sh | ||
no-unicode-literals.sh | ||
no-wildcard-import.sh | ||
pylint-ansible-test.sh | ||
replace-urlopen.sh | ||
required-and-default-attributes.sh | ||
shebang.sh | ||
skip.txt | ||
test-constraints.sh | ||
use-compat-six.sh |