This is a tracking bug for Change: Python 3 Migration Improvements
For more details, see: https://fedoraproject.org//wiki/Changes/Python_3_Migration_Improvements
Since Changes/Python_3_as_Default was retargeted for F23 mostly due to uncertainty about DNF and Anaconda porting status, this change aims to reflect current progress of Python 3 readiness in Fedora and sum up goals for Fedora 22.
This message is a reminder that Fedora 22 Change Checkpoint: Completion deadline (testable) is on 2015-02-24 .
At this point, all accepted Changes should be substantially complete, and testable. Additionally, if a change is to be enabled by default, it must be so enabled at Change Completion deadline.
This bug should be set at least to the MODIFIED state to indicate that it achieved completeness. Status will be provided to FESCo right after the deadline. If, for any reasons, your Change is not in required state, let me know and we will try to find solution. Fedora 22 is going to be strictly time based release. For Changes you decide to cancel/move to the next release, please use the NEW status and set needinfo on me and it will be acted upon.
In case of any questions, don't hesitate to ask Wrangler (jreznik). Thank you.
To provide current status of Python 3 switching:
- authconfig has already been switched
- cloud-init will be switched today
- dnf will be switched today
- gettext has already been switched
- heat-cfntools will be switched today
- nfs-utils will be switched today
- pcp will be switched today
- sos will be switched today
So everything is either switched already or will be switched today. I emailed Colin Walters to change remaining Python 2 packages to their Python 3 variant in Fedora Atomic Host, so everything should be ready by tomorrow.
The rest of the packages mentioned in the change page would be nice to switch, but we're not relying on them - the ones listed above are the hard requirements (and I made this bug depend on them).
Thanks! Let me know once the switch is completed.
Ok, so it turns out that policycoreutils-python3 exists, but doesn't work  (not fully, anyway). That means that we won't be able to achieve python2-free minimal cloud image or atomic host and the change has to be reverted. I'll make sure we only have Python 2 on both atomic host and in minimal cloud image and note in this image when I've reverted everything properly. Packages that are not in atomic host and minimal cloud image still can freely port for F22, but the rest should only port for F23.
This message is a reminder that Fedora 22 "Change Checkpoint: 100% Code Complete Deadline" is on 2015-03-31 .
All Accepted Changes has to be code complete and ready to be validated in the Beta release (optionally by Fedora QA). Required bug state at this point is ON_QA.
As for several System Wide Changes, Beta Freeze is a point of contingency plan, all incomplete Changes will be reported to FESCo for 2015-04-01 meeting. In case of any questions, don't hesitate to ask Wrangler (jreznik).
Reverted in F22.
hamster-time-tracker v2.0-rc1 promises support for Python3 (and Gtk3). But I fail to find any new dependencies as said in the announcement of upstream.
Do anyone knows what's the status of this bug?
This bug appears to have been reported against 'rawhide' during the Fedora 25 development cycle.
Changing version to '25'.
The Change was reverted for f22. For f23, it's superseded by the [Python 3 as Default] Change. For the general porting effort, [PYTHON3] is the master tracking bug.
I don't think this bug is useful as a tracker, so I believe it can be closed. However I'm not familiar with Changes Tracking bug workflows.
[Python 3 as Default]: https://fedoraproject.org/wiki/Changes/Python_3_as_Default
This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.