Red Hat Bugzilla – Bug 1306951
Keep providing a py2 version
Last modified: 2016-07-01 07:58:26 EDT
While it is great that radicale defaults to py3, it would be even nicer if we would still provide a py2 version.
Not every web-app currently runs in py3 and one cannot mix py2 and py3 in the same apache server. So no mod_wsgi and python3-mod_wsgi together.
Which means, one cannot effectively run radicale (py3) and say pagure (py2) on the same server. That's a pity.
Could we do:
- radicale -> py3
- raciale-python2 -> py2
This way we still allow to run radicale with another web-app but still default to py3.
I'll investigate the best way to do it. I agree it's interesting to have both versions available.
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.
More information and reason for this action is here:
This bug is still valid, re-setting it to rawhide and the best way would be to simply do a radicale-python2 subpackage
I've modified the spec file to add support for python2. Could you please help me testing it?
It's in this copr repository:
You can enable it with:
dnf copr enable jorti/python2-radicale
The subpackages radicale-httpd and radicale-python2-httpd provide the Apache configuration examples. I've left the standalone daemon with the python3 version only.
I've pushed it to rawhide:
I've split the package in the python modules:
The standalone server (only python3):
And the httpd support:
Any feedback is welcomed.
Many thanks, I have had the time to test them but will try to do it soon.
Would it be possible to consider updating F24 and F23 for these as well?
I'd like to give it a more extensive testing in rawhide first, then I'll push it to the stable releases.
Fedora 24 update: