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
|
||
|---|---|---|
| .. | ||
| api | ||
| bin | ||
| docsite | ||
| man | ||
| templates | ||