Hello,
for the time being, I think the first step should be disabling packaging the app_python on the distros that does not have Python2 any more, but still keep it in the git repo, because some people can compile newer kamailio version on older distros.
Over the time, we can reconsider and decide again if the module should be completely removed.
Cheers, Daniel
On 22.12.20 13:08, Anthony Alba wrote:
Hi devs,
Background: I am the porter of app_python.so to Python 3 (app_python3.so) nearly 3 years ago.
As we all know Python 2 reached EoL almost one year ago, it may be timely to discuss the issue of when(if) to remove the Python 2 module app_python.so in kamailio.
- Debian: just over a year ago:
https://lists.debian.org/debian-devel-announce/2019/11/msg00000.html
- Python 2 EOL:
https://www.infoworld.com/article/3365221/python-2-end-of-life-how-to-surviv...
- Debian Bullseye (not yet released):
https://wiki.debian.org/Python/2Removal "; "port upstream package to python3 (or file upstream bug): make sure package doesn't call python at build- or compile time (as there won't be a python package and no python command in bullseye, only python3.) "
- Debian Buster/Stretch - used in CI by the (Sipwise I think)
builders. EoL LTS ~2022 for Stretch, ~2024 for Buster. https://wiki.debian.org/DebianReleases
Discussion: should app_python be dropped for Kamailio 5.5.x or 5.6.x? What are your thoughts?
Cheers Anthony
Kamailio (SER) - Development Mailing List sr-dev@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev