Alex Willmer
Alex Willmer
> 4. `jsonify()` prefers `ensure_ascii=False`, falling back to `ensure_ascii=True` on `UnicodeDecodeError`. I'm unsure what would trigger that exception only in the former case. Python 2.7 [`json.dumps()` docs](https://docs.python.org/2.7/library/json.html#json.dumps) say (emphasis mine)...
Python 3.0 doc also incorrectly lists an encoding argument.
@stefanor do you have an example of a playbook that failed when `jsonify()` was replaced with `json.dumps()`?
> I can't reproduce it any more, but I recall an empty list being turned into `[None]` or something like that. Thanks, I'll keep an eye out.
> 4. `jsonify()` prefers `ensure_ascii=False`, falling back to `ensure_ascii=True` on `UnicodeDecodeError`. I'm unsure what would trigger that exception only in the former case. Found an inverse case (`ensure_ascii=False` succeeds, `ensure_ascii=True`...
> 4. `jsonify()` prefers `ensure_ascii=False`, falling back to `ensure_ascii=True` on `UnicodeDecodeError`. I'm unsure what would trigger that exception only in the former case. I think the exception handling was first...
> 4. `jsonify()` prefers `ensure_ascii=False`, falling back to `ensure_ascii=True` on `UnicodeDecodeError`. I'm unsure what would trigger that exception only in the former case. claude.ai (with some nudging) found a case...
Notes to self - `sshpass` command, wraps `ssh` to inject password non-interactively. Last release 1.10 in 2023 - `SSH_ASKPASS` openssh environment variable, program that `ssh` will run to request a...
Ansible >= 12 (ansible-core >= 2.19) is able to act as an `SSH_ASKPASS` command, so it no longer requires `sshpass` to support connections using `ansible_ssh_password`.