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.
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)
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.
There's no upstream support for python3 and paste and from what I hear there isn't going to be any (pyramid/TG2 devs might work on something but they have yet to release a fork). paste is also wsgi implementing code (rather than wsgi consuming code) so it's a very tough thing to provide a unified code-base port of (the wsgi specification for python2 and python3 is different). If paste is ported, it's probably going to need to be in a different package because it won't be a single upstream tarball for python2 and python3.
It's probably best to port to a different library that provides something similar rather than trying to port paste itself anyway. Will note this advice on the User:Churchyard/python3 wiki page and closing this bug as CANTFIX.
Both Pyramid and TurboGears have forked parts of Paste and ported them to Python3.
I got an impression that upstream supports Python 3 now. See https://bitbucket.org/ianb/paste/commits/all
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.
More information and reason for this action is here:
Would it be possible to update paste? There is 2.0.2  version already on pypi which should support python3.
Luke, would you mind if I gave it a shot?
as discussed on #fedora-releng
I'm working on it ;). I've made a few patches on top of upstream git master, see here:
Tests are good now, opened an issue for upstream on bitbucket: https://bitbucket.org/ianb/paste/issues/13/tests-failing-under-python-3