6:50 a.m.
Hello,
I like to drop Python 2 support from current master. For over two years,
the FreeIPA development team has worked hard on porting FreeIPA to
Python 3. Since release 4.6, FreeIPA has been using Python 3 by default
on Fedora. Now it's time to make the final step and remove Python 2
compatibility completely.
Benefits & Reasons
==================
Python 2.7 will reach its extended support lifetime by 2020-01-01. After
2020, the upstream developers will no longer provide any fixes or
security patches.
Python 2 support has become a burden for the FreeIPA team. With removal
of Python 2 support, FreeIPA can finally start to use new Python 3
language features like f-strings and type annotations, or improved
standard library modules like configparser. Removal of Python 2 support
would speed up development and testing as well as allow us to clean the
code base. The code is littered with special casing for Python 2 / 3
differences.
Dependency on Python 2 is also blocking improvement like new Python
installer for 389-DS, see https://github.com/freeipa/freeipa/pull/1563.
The lib389 Python package is only available for Python 3.
The Fedora Python maintenance team is working on mass removal of Python
2 packages, see
https://fedoraproject.org/wiki/Changes/Mass_Python_2_Package_Removal .
FreeIPA depends on lots of Python packages. Dropping Python 2 support
will allow us to remove additional Python 2 dependencies, too.
Time line
=========
FreeIPA 4.8 will be the first release that requires at least Python 3.6.
The version is going to be released either end of 2018 or early 2019.
4.8 is scheduled to land in Fedora 30 (GA 2019-05-07).
Scope
=====
The server, client and all Python libraries of FreeIPA 4.8 will require
Python 3.6 or newer.
FreeIPA 4.7 and 4.6 will continue to support Python 2.
Affected packages / distributions
=================================
Fedora 30 will no longer contain the following packages:
* python2-ipalib
* python2-ipaclient
* python2-ipaserver
* python2-ipatests
This change affects Ipsilon Project and Fleet Commander packages:
* python2-ipa-desktop-profile-client
* fleet-commander-admin
* ipsilon-tools-ipa
Further more, Debian and Ubuntu need to use Python 3.6 or newer instead
of Python 2.7. As far as I know, Samba is holding back FreeIPA on these
distributions.
Patrick (Ipsilon), Oliver (Fleet Commander), and Timo (Debian/Ubuntu)
have been working on Python 3.
Pull request
============
https://github.com/freeipa/freeipa/pull/2020/files
Regards,
Christian
--
Christian Heimes
Senior Software Engineer, Identity Management and Platform Security
Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael Cunningham, Michael
O'Neill, Eric Shander
9:54 a.m.
On 03.09.2018 14:50, Christian Heimes wrote:
Further more, Debian and Ubuntu need to use Python 3.6 or newer
instead
of Python 2.7. As far as I know, Samba is holding back FreeIPA on these
distributions.
Right, the root reason is this:
https://github.com/samba-team/samba/pull/110
same issue with src:talloc, so if there's anyone at RH who could help to
fix this issue upstream then that would be great.
--
t
7:24 a.m.
On ma, 03 syys 2018, Timo Aaltonen via FreeIPA-devel wrote:
On 03.09.2018 14:50, Christian Heimes wrote:
> Further more, Debian and Ubuntu need to use Python 3.6 or newer instead
> of Python 2.7. As far as I know, Samba is holding back FreeIPA on these
> distributions.
Right, the root reason is this:
https://github.com/samba-team/samba/pull/110
same issue with src:talloc, so if there's anyone at RH who could help to
fix this issue upstream then that would be great.
This is *not* a root reason for us
not using Python 3 in Samba. A real
reason is that Samba AD DC code cannot be run with Python 3 yet at all,
as well as majority of the Samba test suite.
We have a long term effort across Red Hat, SUSE, and Catalyst to move
Samba code fully to Python 3. We are in the process of improving both
Python code in Samba and migrating Samba's build system to Python 3.
In Fedora we are building Samba components required by FreeIPA for
Python 3 and Python 2 at the same time. We are utilizing these Python 3
modules in FreeIPA without issues for several releases already. So there
is no limiting factor on providing parallel installation of Python 3 and
Python 2 of Samba for the sake of FreeIPA use of the Python 3 parts.
When FreeIPA would remove Python 2 code itself, this will not affect
Samba in any capacity. Python 2 is still required by Samba AD builds but
since Samba AD does not require anything from FreeIPA, there is no
problem with us removing Python 2 subpackages.
--
/ Alexander Bokovoy
Sr. Principal Software Engineer
Security / Identity Management Engineering
Red Hat Limited, Finland
8:04 a.m.
On 04.09.2018 15:24, Alexander Bokovoy wrote:
On ma, 03 syys 2018, Timo Aaltonen via FreeIPA-devel wrote:
> On 03.09.2018 14:50, Christian Heimes wrote:
>> Further more, Debian and Ubuntu need to use Python 3.6 or newer instead
>> of Python 2.7. As far as I know, Samba is holding back FreeIPA on these
>> distributions.
>
> Right, the root reason is this:
>
> https://github.com/samba-team/samba/pull/110
>
> same issue with src:talloc, so if there's anyone at RH who could help to
> fix this issue upstream then that would be great.
This is *not* a root reason for us not using Python 3 in Samba. A real
reason is that Samba AD DC code cannot be run with Python 3 yet at all,
as well as majority of the Samba test suite.
No, but it's a problem for Debian/Ubuntu to provide py3 bindings which
freeipa needs.. talloc et al. Having the multiarch string in the
resulting library name is bad. This needs to be fixed upstream.
--
t
8:56 a.m.
On ti, 04 syys 2018, Timo Aaltonen via FreeIPA-devel wrote:
On 04.09.2018 15:24, Alexander Bokovoy wrote:
> On ma, 03 syys 2018, Timo Aaltonen via FreeIPA-devel wrote:
>> On 03.09.2018 14:50, Christian Heimes wrote:
>>> Further more, Debian and Ubuntu need to use Python 3.6 or newer instead
>>> of Python 2.7. As far as I know, Samba is holding back FreeIPA on these
>>> distributions.
>>
>> Right, the root reason is this:
>>
>> https://github.com/samba-team/samba/pull/110
>>
>> same issue with src:talloc, so if there's anyone at RH who could help to
>> fix this issue upstream then that would be great.
> This is *not* a root reason for us not using Python 3 in Samba. A real
> reason is that Samba AD DC code cannot be run with Python 3 yet at all,
> as well as majority of the Samba test suite.
No, but it's a problem for Debian/Ubuntu to provide py3 bindings which
freeipa needs.. talloc et al. Having the multiarch string in the
resulting library name is bad. This needs to be fixed upstream.
"bad" is
an opinion. Technically we have it working and there is no
reason to claim Debian couldn't do the same as upstream does.
So it works for upstream which runs its build farm on Ubuntu and it
works for Fedora/OpenSUSE. At this point if Debian/Ubuntu needs
something else, I'd rather see you guys actively involved upstream to
explain and provide patches. The pull request above seems stuck with not
much of explanation of why is it needed beyond an opinion how shared
objects should be named.
--
/ Alexander Bokovoy
Sr. Principal Software Engineer
Security / Identity Management Engineering
Red Hat Limited, Finland
7:16 a.m.
On 2018-09-03 13:50, Christian Heimes via FreeIPA-devel wrote:
Hello,
I like to drop Python 2 support from current master. For over two years,
the FreeIPA development team has worked hard on porting FreeIPA to
Python 3. Since release 4.6, FreeIPA has been using Python 3 by default
on Fedora. Now it's time to make the final step and remove Python 2
compatibility completely.
For your information,
I have created a change proposal for Fedora 30,
https://fedoraproject.org/wiki/Changes/FreeIPA_Python_2_Removal
Christian
--
Christian Heimes
Senior Software Engineer, Identity Management and Platform Security
Red Hat GmbH, http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael Cunningham, Michael
O'Neill, Eric Shander
1662
days inactive
1664
days old
freeipa-devel@lists.fedorahosted.org
5 comments
3 participants
participants (3)
-
Alexander Bokovoy -
Christian Heimes -
Timo Aaltonen