Fabian Arrotin

same for CentOS Stream 8 and 9 so it will be landing in RHEL 8 and RHEL 9 soon : ``` rpm -q ansible-core ansible-core-2.13.3-1.el8.x86_64 ``` Reverting to 2.12 for...

I'm not the author, but wondering why forcing a switch to python3 while quite a few distributions are still on python2. Using myself some of those scripts for the CentOS...

hmm, tried to reproduced in a "staging" env and I can't so seems that it was something else (and not mock related). Sorry for the noise and let close this...

Just to add that I locally applied https://github.com/mitogen-hq/mitogen/pull/984/files and so far so good on my staging/test instance

you're aware that #966 is still open so afaik mitogen doesn't support (yet) ansible-core 2.13 ... haven't checked in a while but still the reason why I stick with ansible-core...

> > FWIW - just bumping ANSIBLE_VERSION_MAX to (2, 14) allows my plays to run. YMMV. Just curious .. myself I'd need to bump to 2.14 but mitogen is still...

Yes, or better : have a new mitogen tag/release that would have that ? Wondering if a mitogen dev can consider this, assuming that there were enough feedback about it...

Wanted to create an issue for this but I just hit the same error with mitogen 0.3.7, ansible-core 2.14.14 (python version = 3.9.18) ``` ERROR! [task 154152] 14:29:50.303138 E mitogen:...

seems to be related to #957 ?

@moreati : fwiw, patched 0.3.7 tag/release with https://github.com/mitogen-hq/mitogen/pull/984/files and symptom disappeared (all running fine). I'll keep testing (staging env here) and report/give feedback here