On 4/7/22 07:40, 'Felix Fontein' via Ansible Project wrote:
I really wish you would stop repeating this procedure on every Ansible
release. If you want things to actually change, start a proper
discussion in the appropriate place
(https://github.com/ansible-community/community-topics/).
This topic came up here and is IMHO relevant for normal Ansible users.
So please don't try to push it away from the users.
Getting collection updates from Ansible 5 with ansible-core 2.11.x
-----------------------------------------------------------------
Ansible 5 includes ansible-core 2.12.x which has raised the minimum
python requirement to python>=3.8 and users have expressed an
interest in getting collection updates as they ship in Ansible 5
while keeping ansible-core 2.11.x which still supports python>=2.7.
An ansible-galaxy requirements file based on the collections from
Ansible 5 has been made available for this use case:
https://github.com/ansible-community/ansible-build-data/blob/main/5/galaxy-requirements.yaml
I really wish you or the appropriate upstream maintainer could update
the documentation to stop saying this. It's just not true.
You have to distinguish between the PyPi package called `ansible`, and
the product/distribution called Ansible.
Understood, but...
The *product/distribution* Ansible consists of both `ansible` and the
`ansible-core` PyPi packages. The *docsite*
(https://docs.ansible.com/ansible/latest/) describes both. The
*changelog* describes both. The *porting guide* also describes both.
That is why our announcement is written as it is. We are talking about
the product/distribution.
The PyPi package `ansible` does indeed depend on `ansible-core` and
does not contain it. But that it is split up into two PyPi packages is
an **implementation detail** to Ansible users.
...I have to agree with Nico that the wording and the versioning also
confused me in the beginning.
Ansible users like me are interested to know whether they should update
or not, especially in the case of security fixes.
Doing pip upgrade on PyPI package 'ansible' is easy because it might
have a dependency on a newer version of 'ansible-core' which gets pulled
in automatically. That's fine.
But if there's an important security fix only in ansible-core Ansible
users have to be aware to explicitly invoke
pip install --upgrade ansible-core
to get the updates. So this "implementation detail" is indeed quite
relevant to Ansible users who want to properly maintain their controller.
Ciao, Michael.
--
You received this message because you are subscribed to the Google Groups "Ansible
Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/83ace2be-f1de-57f1-a28b-a1f0e5c97668%40stroeder.com.
