Rich, as far as ansible-base is concerned, there is/was a bug that was errantly removing __ini__.py files, which is likely the cause on python2. It’s being worked on currently.
fwiw, ansible/ansible is more similar to Ansible 2.9 at this point. ansible-base is what ansible/ansible will look like on March 23.
Rich, as far as ansible-base is concerned, there is/was a bug that was errantly removing `__ini__.py` files, which is likely the cause on python2. It's being worked on currently.
Is there an issue/pr that I can follow? I would like to run my tests with as close to ansible 2.10 as possible.
Also, I tested with python3, so at least for me, the problem manifested using other than python2 (or I'm running into a separate issue).
where install downloads it from github (if it doesn't already exist), and run does a `source {envdir}/ansible/hacking/env-setup` before running the rest of the command line.