<!-- Kamailio Pull Request Template -->

<!-- IMPORTANT: - for detailed contributing guidelines, read: https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md - pull requests must be done to master branch, unless they are backports of fixes from master branch to a stable branch - backports to stable branches must be done with 'git cherry-pick -x ...' - code is contributed under BSD for core and main components (tm, sl, auth, tls) - code is contributed GPLv2 or a compatible license for the other components - GPL code is contributed with OpenSSL licensing exception -->

#### Pre-Submission Checklist <!-- Go over all points below, and after creating the PR, tick all the checkboxes that apply --> <!-- All points should be verified, otherwise, read the CONTRIBUTING guidelines from above--> <!-- If you're unsure about any of these, don't hesitate to ask on sr-dev mailing list --> - [ ] Commit message has the format required by CONTRIBUTING guide - [ ] Commits are split per component (core, individual modules, libs, utils, ...) - [ ] Each component has a single commit (if not, squash them into one commit) - [ ] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated)

#### Type Of Change - [ ] Small bug fix (non-breaking change which fixes an issue) - [ ] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality)

#### Checklist: <!-- Go over all points below, and after creating the PR, tick the checkboxes that apply --> - [ ] PR should be backported to stable branches - [ ] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number)

#### Description <!-- Describe your changes in detail --> Implement script reloading by copying the method used in app_lua: the version of the script is incremented by RPC.

For each worker, the next time it handles a method, python_exec.c:apy_exec() will check for a newer version and reload, if necessary.

Set a lock so the script reload only occurs at depth 0 (in the unlikely case that apy_exec() is called recursively).

This is not thread-safe as we are using a process-wide lock: don't call back into apy_exec() from a Python C extension that uses threads.

For Pythonistas, we are reloading the module, not reinitializing the interpreter. Standard caveats about reloading modules apply. E.g, references in the old module that are not redefined in the newer module remain.

You can view, comment on, or merge this pull request online at:

https://github.com/kamailio/kamailio/pull/1456

-- Commit Summary --

* app_python3: implement script reloading

-- File Changes --

M src/modules/app_python3/app_python_mod.c (220) M src/modules/app_python3/app_python_mod.h (2) M src/modules/app_python3/apy_kemi.c (47) M src/modules/app_python3/doc/app_python3_admin.xml (14) M src/modules/app_python3/python_exec.c (98)

-- Patch Links --

https://github.com/kamailio/kamailio/pull/1456.patch https://github.com/kamailio/kamailio/pull/1456.diff