community.general/docs/docsite/rst/dev_guide/testing/sanity/no-basestring.rst

Sanity Tests » no-basestring
============================

Do not use ``isinstance(s, basestring)`` as basestring has been removed in
Python3.  You can import ``string_types``, ``binary_type``, or ``text_type``
from ``ansible.module_utils.six`` and then use ``isinstance(s, string_types)``
or ``isinstance(s, (binary_type, text_type))`` instead.

If this is part of code to convert a string to a particular type,
``ansible.module_utils._text`` contains several functions that may be even
better for you: ``to_text``, ``to_bytes``, and ``to_native``.
Initial ansible-test sanity docs. (#26775) * Rename no-iterkeys test for consistency. * Require docs for all ansible-test sanity tests. * Initial ansible-test sanity docs. * Fix capitalization of Python. * Fix sanity code smell test false positives. * Fix another code-smell false positive. 2017-07-14 15:24:45 +02:00			`Sanity Tests » no-basestring`
			`============================`

code-smell test changes * Create get_exception and wildcard import code-smell tests * Add more detail to boilerplate and no-basestring descriptions * Remove the no-list-cmp test as the pylint undefined-variable test covers it 2017-08-02 01:18:27 +02:00			Do not use ``isinstance(s, basestring)`` as basestring has been removed in
			Python3. You can import ``string_types``, ``binary_type``, or ``text_type``
			from ``ansible.module_utils.six`` and then use ``isinstance(s, string_types)``
			or ``isinstance(s, (binary_type, text_type))`` instead.

			`If this is part of code to convert a string to a particular type,`
			``ansible.module_utils._text`` contains several functions that may be even
			better for you: ``to_text``, ``to_bytes``, and ``to_native``.