On Wed, 28 Jan 2015 11:09:08 -0500 (EST)
Bohuslav Kabrda <bkabrda(a)redhat.com> wrote:
Hi,
I just filed 2 bugs [A], [B] for the Python 3 switch [C] and I
realized that I should probably follow the mass bug filing policy. As
I've said previously, we've already had both Python 2 and Python 3 on
LiveCDs for few releases, so it makes sense to move as much as
possible to Python 3. My intention is to mass file bugs only for
"applications" (see the second item in second list at [D]) - in
short, these are packages for which it doesn't make sense to
introduce python3- subpackage, but it only makes sense to rebuild
them with Python 3. The mass bug filing policy suggests providing
text of the bug for review, so here it is:
So, at today's FESCo meeting there was a good deal of discussion about
python as default:
http://meetbot.fedoraproject.org/fedora-meeting/2015-01-28/fesco.2015-01-...
in which we agreed defer this to F23, file bugs against rawhide after
branch (+6,0,0)
Not speaking for FESCo, but myself, if you think there is still
advantage in trumpting the python3 changes that will land in f22,
please do rescope the change and resubmit. I realize this is a
process thats going to take a while to complete.
Now, on to the mass bug filing...
Do you have a list of packages you intend to file against?
Since your package requires Python and is considered an application
as per [1], I'd like to ask you to rebuild it with Python 3. Please
see recommendations and notes at [2]. Note: this switch should only
be done assuming you need to do none or very little downstream
patching of upstream source. If upstream source doesn't work with
Python 3, it's ok to stay with Python 2.
Some general notes:
If your package depends on Python because of a Python script that
has /usr/bin/python in hashbang, you need to change this
to /usr/bin/python3. All "Requires" and "BuildRequires" on Python
extension modules have to be changed from "python-foo" to
"python3-foo" in order for this change to work. If your package is an
"application" (let's call it "foo") and it also generates a
subpackage with Python bindings (i.e. "python-foo" or "foo-python"),
you should provide a python3 subpackage ("python3-foo" or
"foo-python3") and use that as dependency of other subpackages.
[1]
http://fedoraproject.org/wiki/Changes/Python_3_as_Default
[2]
https://fedoraproject.org/wiki/Packaging:Python#Guidelines
I'd prefer people make these changes after we branch in rawhide, but as
always it's going to be up to the maintainer(s) what is best for their
packages.
If everyone agrees, I'll send a mail to devel-announce, saying
that
we're switching to Python 3 and all maintainers should rebuild with
it, assuming that upstream sources are Python 3 compatible. After a
week or so I'll file bugs for the remaining components. I haven't yet
determined the number of affected packages, since I'm mostly
interested in packages that are on LiveCD/cloud images - there are
~10 of these that don't have bugs filed.
Thats a pretty small number.
kevin