summaryrefslogtreecommitdiff
path: root/lib/ansible/parsing/ajson.py
diff options
context:
space:
mode:
authorcos <cos>2024-04-20 10:08:13 +0200
committercos <cos>2024-04-20 10:12:35 +0200
commit9d0c7ef4dc8d7f3bea3ff70c977a87d154316a26 (patch)
tree7e3797bdd2403982f4a351608d9633c910aadc12 /lib/ansible/parsing/ajson.py
parentc224b4bf4a6538c3ddc5cb762367c0d53462fa12 (diff)
downloaddebian-ansible-core-upstream/second-failed-recreation-attempt.zip
Recreate upstream branch stateupstream/second-failed-recreation-attempt
Work around that version control is behind the actual package version in trixie. As is obvious from the lacking commits in the salsa repository and also visible on https://tracker.debian.org/pkg/ansible-core with the report from vcswatch stating: VCS repository is not up to date. This commit was generated using `gbp import-dsc`, which should hopefully have made it a squashed representation on the same set of changes on the uploader's unpushed git tree.
Diffstat (limited to 'lib/ansible/parsing/ajson.py')
-rw-r--r--lib/ansible/parsing/ajson.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/ansible/parsing/ajson.py b/lib/ansible/parsing/ajson.py
index 48242271..8049755b 100644
--- a/lib/ansible/parsing/ajson.py
+++ b/lib/ansible/parsing/ajson.py
@@ -8,7 +8,7 @@ __metaclass__ = type
import json
# Imported for backwards compat
-from ansible.module_utils.common.json import AnsibleJSONEncoder # pylint: disable=unused-import
+from ansible.module_utils.common.json import AnsibleJSONEncoder
from ansible.parsing.vault import VaultLib
from ansible.parsing.yaml.objects import AnsibleVaultEncryptedUnicode