GitLab

Resign to the fact that there is no releases v1 that is usable to PyJapc, and no *development* version available either (since https://github.com/jpype-project/jpype/issues/848 was added before https://github.com/jpype-project/jpype/pull/832).

Update JPype dependencies, which are a very constrained set due to the instability of JPype (and ultimately the tests failing for all of the excluded versions).

Added an atexit handler to deal with user threads in Java blocking the Python & Java shutdown. It appears that JapcMock has a static attribute which starts a thread upon class instantiation.
https://github.com/jpype-project/jpype/issues/817 refers. It is likely that other JPype1 1.x uses will hit this limitation quite quickly, so we await a long term solution to the problem.

Move the tests into the package as it is hard to avoid testing the source of PyJapc rather than the installed PyJapc. (e.g. https://gitlab.cern.ch/pelson/pyjapc/-/jobs/7187874)

In the process, modernise the setup.py, publish a wheel, and automatically version via setuptools_scm.
Note that we make use of no-local-version for setuptools_scm as it is invalid to have the X.Y.Z.dev0+{hash} style version information in the cmmnbuild-dep-manager entry-point.

Initial tests against centos:7 were not sucessful due to the requirement for a full compiler environment in order to install Jpype1.