From Fedora Project Wiki
< Changes
Churchyard (talk | contribs) mNo edit summary |
(clean up and mark ready for wrangler) |
||
| Line 25: | Line 25: | ||
== Summary == | == Summary == | ||
<!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. --> | <!-- A sentence or two summarizing what this change is and what it will do. This information is used for the overall changeset summary page for each release. --> | ||
Ansible started out as a python2 only application, but in recent years a large amount of work has gone into porting things to python3. Last year, the Fedora ansible package started shipping a ansible-python3 allowing users to switch to python3 on the control host easily if they wished, but left the default as python2. Now in Fedora 29, the default will be switched and the python3 version will be | Ansible started out as a python2 only application, but in recent years a large amount of work has gone into porting things to python3. Last year, the Fedora ansible package started shipping a ansible-python3 allowing users to switch to python3 on the control host easily if they wished, but left the default as python2. Now in Fedora 29, the default will be switched and the python3 version will be the only version shipped. | ||
== Owner == | == Owner == | ||
| Line 61: | Line 61: | ||
<!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | <!-- Expand on the summary, if appropriate. A couple sentences suffices to explain the goal, but the more details you can provide the better. --> | ||
The Fedora ansible package will be changed to default to python3 with the 'ansible' | The Fedora ansible package will be changed to default to python3 with the 'ansible' package. Note that this change is on the control host, you can control what python is used on target hosts via your inventory. You may continue to use python2 there, or use python3 as your target hosts require. | ||
== Benefit to Fedora == | == Benefit to Fedora == | ||
| Line 76: | Line 76: | ||
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
* Release engineering: [https://pagure.io/releng/ | * Release engineering: [https://pagure.io/releng/7414 #releng-7414] (a check of an impact with Release Engineering is needed) <!-- REQUIRED FOR SYSTEM WIDE AS WELL AS FOR SELF CONTAINED CHANGES --> | ||
<!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuild required? include a link to the releng issue. | <!-- Does this feature require coordination with release engineering (e.g. changes to installer image generation or update package delivery)? Is a mass rebuild required? include a link to the releng issue. | ||
The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --> | The issue is required to be filed prior to feature submission, to ensure that someone is on board to do any process development work and testing, and that all changes make it into the pipeline; a bullet point in a change is not sufficient communication --> | ||
| Line 147: | Line 147: | ||
Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze. | Release Notes are not required for initial draft of the Change Proposal but has to be completed by the Change Freeze. | ||
--> | --> | ||
The ansible package has switched to python3 by default. This means python3 will be used for ansible on your Fedora control host. You can choose which python version your target hosts are using in your inventory. | |||
[[Category: | [[Category:ChangePageReadyForWrangler]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
Revision as of 19:11, 27 March 2018
Ansible python3 default
Summary
Ansible started out as a python2 only application, but in recent years a large amount of work has gone into porting things to python3. Last year, the Fedora ansible package started shipping a ansible-python3 allowing users to switch to python3 on the control host easily if they wished, but left the default as python2. Now in Fedora 29, the default will be switched and the python3 version will be the only version shipped.
Owner
- Name: Kevin Fenzi
- Email: kevin@scrye.com
- Release notes owner:
Current status
- Targeted release: Fedora 29
- Last updated: 2018-03-27
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
The Fedora ansible package will be changed to default to python3 with the 'ansible' package. Note that this change is on the control host, you can control what python is used on target hosts via your inventory. You may continue to use python2 there, or use python3 as your target hosts require.
Benefit to Fedora
Less python2 usage in the world, along with using the version of python that upstream is preferring.
Scope
- Proposal owners: Modify ansible package (already done)
- Other developers: N/A (not a System Wide Change)
- Release engineering: #releng-7414 (a check of an impact with Release Engineering is needed)
- List of deliverables: N/A (not a System Wide Change)
- Policies and guidelines: N/A (not a System Wide Change)
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
N/A (not a System Wide Change)
How To Test
N/A (not a System Wide Change)
User Experience
N/A (not a System Wide Change)
Dependencies
N/A (not a System Wide Change)
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
- Blocks product? product
Documentation
See http://docs.ansible.com/ansible/latest/python_3_support.html for more information, including how to set your target hosts to use python2 or 3.
N/A (not a System Wide Change)
Release Notes
The ansible package has switched to python3 by default. This means python3 will be used for ansible on your Fedora control host. You can choose which python version your target hosts are using in your inventory.