|Summary:||babel: Support Python 3|
|Product:||[Fedora] Fedora||Reporter:||Miro Hrončok <mhroncok>|
|Component:||babel||Assignee:||Felix Schwarz <fschwarz>|
|Status:||CLOSED ERRATA||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||rawhide||CC:||a.badger, fschwarz, jeff, nphilipp|
|Fixed In Version:||babel-1.3-2.fc20||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2013-10-15 06:31:24 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
|Bug Depends On:|
Description Miro Hrončok 2013-10-02 10:56:24 UTC
Hi, we would like to use Python 3 on the default installation instead of Python 2 on Fedora 22. From that perspective, your package is considered as IMPORTANT - that means, is has to be updated to Python 3, for our intention come true. The goal here is, that at least for F22 you should provide python3- prefixed subpackage. Please, help use update to Python 3 flawlessly. Check if upstream already support Python 3, if yes, use it and add te support to the package. If upstream doesn't support Python 3 yet, encourage it to do so by sending patches and offering your help. When upstream is dead or unwilling to support Python 3, you'll need to patch this package on Fedora level. Try to avoid this as much as you can, but use it, if it's the last option. Chances are, that you ARE the upstream. In that case, everything is easier, just do it yourself. Once Python 3 is supported, check your package, if it works with it. Don't switch to Python 3 yet as a default (that's still against the guidelines). I recommend to prepare your spec and conditionalize the thing with something like %global default_python 2/3. There is a table on wiki, that should list your package. Chances are, that you can see an upstream link that covers the problem. Anyway, please update the table with information you know. https://fedoraproject.org/wiki/User:Churchyard/python3 I offer my help with this task, so if you have no idea, how to work on this, or it is just not your priority, don't hesitate to ask for help. (As you've already realized, this is a bulk text, so if something is not quite exact about your package, sorry for that, just ask)
Comment 1 Felix Schwarz 2013-10-02 11:25:31 UTC
That will be done once we update Babel to 1.x (which I'm planning to do in the next 1-2 weeks if no one else is faster than me on that).
Comment 2 Toshio Ernie Kuratomi 2013-10-02 22:17:52 UTC
For people who may run across this via web searches (I note that this is going to be accomplished via an update to a newer upstream babel so it shouldn't be applicable here): Note: do not follow this portion of the advice as it is against the Packaging Guidelines: "When upstream is dead or unwilling to support Python 3, you'll need to patch this package on Fedora level. Try to avoid this as much as you can, but use it, if it's the last option." If you are in this situation, you'll essentially be forking upstream in order to produce a python3 port. In that situation, the proper thing to do is to create a new package with the python3 port. It would be even better to create the proper upstream infrastructure as well (new upstream scm and issue tracker) but that isn't 100% required by the guidelines.
Comment 3 Fedora Update System 2013-10-06 10:03:26 UTC
babel-1.3-2.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/babel-1.3-2.fc20
Comment 4 Fedora Update System 2013-10-06 18:22:47 UTC
Package babel-1.3-2.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing babel-1.3-2.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-18438/babel-1.3-2.fc20 then log in and leave karma (feedback).
Comment 5 Fedora Update System 2013-10-15 06:31:24 UTC
babel-1.3-2.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.