# \#six

**URL:** https://forum.ansible.com/tag/six/475.md

[Latest](https://forum.ansible.com/latest.md) · [Categories](https://forum.ansible.com/categories.md) · [Tags](https://forum.ansible.com/tags.md)

---

## [Ansible.module\_utils.six is deprecated - what to do for collections that support both ansible-core 2.16 (or even before) and 2.20?](https://forum.ansible.com/t/ansible-module-utils-six-is-deprecated-what-to-do-for-collections-that-support-both-ansible-core-2-16-or-even-before-and-2-20/44616)

<div class="topic-metadata">

**Author:** [@felixfontein](https://forum.ansible.com/u/felixfontein)\
**Replies:** 28\
**Last updated:** [November 26, 2025, 6:34pm UTC](https://forum.ansible.com/t/ansible-module-utils-six-is-deprecated-what-to-do-for-collections-that-support-both-ansible-core-2-16-or-even-before-and-2-20/44616 "2025-11-26T18:34:52Z")

</div>

Recently ansible-core’s ansible-test’s pylint sanity test started to flag ansible.module\_utils.six imports as ansible-bad-import-from. This was easy to ignore with some tests/sanity/ignore-2.20.txt entries, but raised th…