On Wed, 02 Dec 2015 16:05:00 -0000 Toshio くらとみ <toshio@xxxxxxxxxxxxxxxxx> wrote: ...snip... I'll put in my 2cents here. ;) > I think starting to run python3 web apps will contribute more to the > greater good than limiting apps to python2. It will help to > future-proof the web-apps since python2 probably won't be default in > RHEL8 (who knows if it will be available as an add-on, though)... so > at some point you do have to pay this price. So the real question is > whether you want to pay this price now and which people within > infrastructure are going to be doing the work: > > Do it when a RHEL releases with python3: > * sysadmins will have to manage both RHEL7 and RHEL8 web servers for > py2 and py3. > * Concentrated work for developers to get applications ported as > we'll want to migrate to rhel8 and python2 web apps will be holding > us back. > * Packagers will have to branch (and sometimes maintain) needed > packages from Fedora to EPEL. I think waiting this long is a mistake... we should get started (well, we already are really). > Do it now with the EPEL python34 (or a new python35) stack: > * packagers will have to create python3x packages in EPEL > * developers can start porting their apps now which gives them a > longer window to port and perhaps less urgency > * sysadmins will have to manage RHEL7 with python2 and RHEL7 with > python3 web servers > > Do it now with Fedora: > * developers can start porting their apps now which gives them a > longer window to port and perhaps less urgency > * Packagers still have to get packages running on python3 but not as > many due to efforts from Fedora itself. > * sysadmins will have to manage RHEL7 with python2 and Fedora with > python3 web servers. Fedora has a different lifecycle so there's > additional work involved here. I'm somewhat torn between these two. I think it's going to depend on if we can get some time to really make the python3 stack on epel7 workable. I know the folks who worked on it were waiting to land all the 35 stuff in Fedora before looking at epel, but we likely need to get that done soon and get it moved to 3.5 and see what things we need there. If it's not going to be workable we can do Fedora, it just means more work for us on the sysadmin side. One thing that feel through the cracks recently was that when we first started doing non builder Fedora instances, I wanted them to auto update. So we had yum-cron setup on them. However, new instances haven't honored this and we need to move it to dnf-automatic anyhow. Doing that might help reduce the burden of updates flow, but might also increase breakage. > Waiting for RHEL is probably the least overall work but there is a > drawback there.... porting applications to python3 is probably what > will take the most time so the sooner you can get started on that the > sooner you'll be able to stop supporting python2. Ultimately I think it's important for us to start moving to python3. If we use Fedora or EPEL7 python3 I guess might be more up to the coders working on that. kevin
Attachment:
pgplOOmAjZ90N.pgp
Description: OpenPGP digital signature
_______________________________________________ infrastructure mailing list infrastructure@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
