On Wed, May 23, 2018 at 4:52 PM Miro Hrončok <mhroncok(a)redhat.com> wrote:
On 23.5.2018 22:51, Martin Bukatovic wrote:
> What do you think? Do we want to continue dropping python2 modules and
> encourage people to reconfigure ansible to run under python 3 while
> shipping ansible with python 2 or do we want to keep python2 modules
> used by ansible available, even thouhg this is not easy to track right
I think that we can drop them from Fedora 29, where Ansible switches
Removal from Fedora 28 was indeed a bad move, however, as said, the
maintainer here probably had no idea that it may break Ansible, since
the dependency is not tracked.
+1 - Once Fedora 29 lands, I think that makes sense.
Do we need to reintroduce it?
I think from a Fedora user perspective, it would be nice to reintroduce it
for Fedora 28 just because Ansible is still shipping python2 by default.
Retiring python2-firewall in Fedora 29 makes sense given the impending
change to Ansible being python3 only. However from an upstream Ansible
perspective, if there is a strong case not to re-introduce it in Fedora
then I don't have a hard preference because it's relatively easy to direct
users to the module documentation informing them of the change and the need
to use python3 mode (which is now even more clear on the specific issue
thanks to the results of the bugzilla referenced previously in this thread).
python-devel mailing list -- python-devel(a)lists.fedoraproject.org
To unsubscribe send an email to python-devel-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines