[aur-general] Merge requests: Various python2 packages
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/ https://aur.archlinux.org/packages/python2-ngxtop/ into https://aur.archlinux.org/packages/ngxtop/ * Satisfying. * Not a library but more of a command-line tool. No need for python- prefix. ** Some of those packages are required by mediacrush-server-git, but upstream is working on native python3 support, so that won't be a problem for long (and currently the package can't be installed anyway). J. Leclanche
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
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
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
On Thursday, April 24, 2014 09:22:12 Jerome Leclanche wrote:
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
OK then, I agree with you. Have you contacted the current maintainers of those packages? (Blender and bgaleotti, in particular) I'll do the merge if they agreed or didn't respond to you after certain period of time. Regards, Felix Yan
Blender CC'd here.
Regarding ngxtop: It needs to be merged either way. I'm fine disowning
all of these by the way.
J. Leclanche
On Thu, Apr 24, 2014 at 9:28 AM, Felix Yan
On Thursday, April 24, 2014 09:22:12 Jerome Leclanche wrote:
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
OK then, I agree with you.
Have you contacted the current maintainers of those packages? (Blender and bgaleotti, in particular) I'll do the merge if they agreed or didn't respond to you after certain period of time.
Regards, Felix Yan
participants (2)
-
Felix Yan
-
Jerome Leclanche