Hi, we would like to use Python 3 on the default installation instead of Python 2 on Fedora 22.
While this package is not in minimal buildroot, it belongs to fedora-packager stack. We would like to switch to Python 3 there as well.
The goal here is, that at least for F22 you should provide python3- prefixed subpackage.
Please, help us update to Python 3 flawlessly.
Check if upstream already support Python 3, if yes, use it and add the 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, say so and we can solve the problem together.
Chances are, that you ARE the upstream. In that case, everything is easier, just do it yourself.
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.
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)
The py3port branch should work codewise but it may be better to use a single codebase instead of dual branch strategy. Need to evaluate the feasability of this. Problems with single codebase are:
* need to support python2.4
* code needs to be very particular about whether it's dealing with bytes or text
In order to simply release the py3port branch we at least need to update the documentation (doc/ directory and docstrings) to reflect python3 instead of python2. For most of it, that's a huge review task. For some of it, it will be a rewriting from scratch (the two or three places that get into best practices as opposed to documenting API).
whats the status with Python 3 support? Do you need any help with specific things?
yes, if you'd like to take a look at the things mentioned in Comment 1: deciding whether it would be possible to go with a single code base or if two codebases makes more sense and updating the documentation to reflect python3 objects and best practices that would be the tasks that are needed.
Current HEAD: http://bzr.fedorahosted.org/bzr/kitchen/devel/files
Current python3 version: http://bzr.fedorahosted.org/bzr/kitchen/py3port/files
The kitchen source upstream has been moved from bzr to git:
Built for rawhide, with python3!