Essentially, the only user of the version 2 of these packages is (was) mediacrush-server-git and we are currently working for proper Python 3 support in there. In the mean time, the mediacrush-server-git package does not actually build and is currently useless due to other reasons. Imo there is no real point in keeping the python2 package around for a long time unless it is actually needed by something, same logic as for all "old versions of libs" applies here. J. Leclanche
On Thu, Apr 24, 2014 at 7:44 AM, Felix Yan <felixonm...@gmail.com> wrote: > On Thursday, April 24, 2014 05:19:06 Jerome Leclanche wrote: >> https://aur.archlinux.org/packages/python2-flask-classy/ into >> https://aur.archlinux.org/packages/python-flask-classy/ >> >> https://aur.archlinux.org/packages/python2-flask-markdown/ into >> https://aur.archlinux.org/packages/python-flask-markdown/ >> >> https://aur.archlinux.org/packages/python2-tabulate/ into >> https://aur.archlinux.org/packages/python-tabulate/ > > Why? I don't think it wrong to keep both python 2.x and python 3.x of a same > library. Especially when something else depending on them, like python2-flask- > markdown required by mediacrush-server-git. > > Regards, > Felix Yan