ansible

Commit Graph

Author	SHA1	Message	Date
Hervé Beraud	0e9ae5b8cc	[fix] no-unicode-literals sanity error on ansible.egg-info (#30446 ) * [fix] no-unicode-literals sanity error on ansible.egg-info	9 years ago
Toshio Kuratomi	ff13d58c14	Remove use of unicode_literals as it is an anti-pattern 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.	9 years ago

Author

SHA1

Message

Date

Hervé Beraud

0e9ae5b8cc

[fix] no-unicode-literals sanity error on ansible.egg-info (#30446 )

* [fix] no-unicode-literals sanity error on ansible.egg-info

Toshio Kuratomi

ff13d58c14

Remove use of unicode_literals as it is an anti-pattern

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.

2 Commits (eae23d2dbdd26b738a1702e6a064d02df391d48e)