clean up ansible pip installation and test script about ansible HOT 4 CLOSED

Files identified in the description:

• lib/ansible/modules/apt.py
• lib/ansible/modules/pip.py

If these files are incorrect, please update the component name section of the description or use the component bot command.

from ansible.

I think you have misdiagnosed your issue. No matter how you install Ansible, the builtin modules (ansible.builtin.*) will be available. They are not part of a separate collection, which is why they are called "builtin". pip install ansible will also install a number of other collections, covering the full range of content that used to be included in Ansible along with quite a lot that's been added since the core/collection split.

You have not provided any information on how to replicate this issue, so I can't really say what you've done wrong, but you've clearly either ended up with a broken installation (which is not the normal result of pip install ansible) or done something wrong when you attempted to use it.

from ansible.

Hi!

Thanks very much for your submission to Ansible. It means a lot to us
to have an active community that is willing to submit feedback so that we can
continue to make Ansible better.

The Ansible Python API is considered internal and an unsupported aspect of Ansible,
as such this is not considered a bug unless it causes an issue with Ansible command line tools
(ansible, ansible-playbook, ansible-doc, etc).

We do support the provided API for use in developing plugins (modules, dynamic inventories, callbacks, strategies, etc),
but this does not seem to match that case.

If you really need a stable API target to use Ansible, consider using ansible-runner:

• https://github.com/ansible/ansible-runner

Because this project is very active, we're unlikely to see comments made on closed tickets and we lock them after some time.
If you or anyone else has any further questions, please let us know by using any of the communication methods listed in the page below:

• https://docs.ansible.com/ansible/latest/community/communication.html

Thank you once again for this and your interest in Ansible!

from ansible.

@flowerysong It is most likely user error and the fact that I am using Windows...

I think the issue stems from having to use WSL in windows, but that's all I can really share as I am not sure how or why it broke things. Perhaps pip install inside WSL puts things in different places?
@sivel
The Python API seemed like a nice convenience, but it makes sense that it may have some bugs if it is unsupported.

from ansible.