I'm hoping to see a python26-sphinx package appear in EPEL5. It's currently not possible due to missing dependencies but when they are complete I'll try to come back with some patches. Steve.
Hi Steve, Are you a Fedora packager? We could use the multi-Python template so the same spec builds for both the default system Python as well as Python 2.6 -- it's normally used to target Python 3, but it should work in this case as well -- but it'd be nice if someone who actively use it can co-maintain the EL5 branch.
Hi Michel, Yes the multi-python from the same package is definitely an option, as soon as some of the blocking bugs make some progress I'll try to provide a suitable .spec file. Steve.
I'd much rather see python26 packages in separate packages from the python-default packages. Although there's many reasons for this, the one that is the most compelling for me is that it's an opportunity to ship a later release than what's in the default. For instance, the python26-sphinx package could be based on sphinx-1.0.x if it's a separate package.
I'm going to close this bug. If someone is interested, we'd love to have a separate package for this that uses a more recent sphinx.
Just a note: there is a python-sphinx10 package on EPEL5 and EPEL6, so a python26-sphinx package can be based on python-sphinx10