61315cd3c5
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.
(cherry picked from commit ff13d58c14)
16 lines
330 B
Bash
Executable file
16 lines
330 B
Bash
Executable file
#!/bin/sh
|
|
|
|
UNICODE_LITERALS_USERS=$(grep -r unicode_literals . \
|
|
--exclude-dir .git \
|
|
--exclude-dir .tox \
|
|
--exclude no-unicode-literals.sh \
|
|
--exclude no-unicode-literals.rst |
|
|
grep -v ./test/results \
|
|
)
|
|
|
|
if [ "${UNICODE_LITERALS_USERS}" ]; then
|
|
echo "${UNICODE_LITERALS_USERS}"
|
|
exit 1
|
|
fi
|
|
|
|
exit 0
|