-
v2.6.02f62916a · ·
* The get/set round-trip for 64-bit integers is now preserved, meaning you can now set-back what was got from a property * The full exception chain is logged when a get/subscribe failure is received * The full exception chain is raised when an exception is returned upon setting a value * The PyJapc codebase is now type-checked for easier maintainability and improved interface documentation
-
v2.5.032f93316 · ·
* The default ``onException`` handler now provides more context if the exception description is empty (as seen in https://mattermost.web.cern.ch/acc-py/pl/mo6zgxptj7bm386pfak31oabnr) * PyJapc no longer registers an atexit hook to *guarantee* that the finalizer (``PyJapc.__del__``) is called. Instead we rely on normal object lifecycle management from Python. In practice, CPython 3.x always calls the finalizer before exiting. The PyJapc finalizer continues to stop and destroy subscriptions and do an ``rbacLogout``. * PyJapc tests have been made more stable in CI
-
v2.4.059493491 · ·
* Fix crash if configured accelerator name is accessed when InCA was previously configured without accelerator (!74) * Bypass dimension check if dimensions are undefined (!78) * Fix for undefined variable code-path for specific log-level values (!77) * Upgrade cmmnbuild-dep-manager, and make use of the improved JAR guarantees (!75)
-
v2.3.0e27830d8 · ·
* Addition of the ``PyJapc.getNextParamValue`` method to await the next N value(s) acquired through a subscription. This can be handy in a few situations, for example if some signal processing algorithm needs the next 10 acquisition values this blocking method can be called and it will only return when these values are ready. * Use of ``*args`` and ``**kwargs`` has been removed entirely from PyJapc in favour of explicitly named arguments. The change is entirely backwards compatible and has resulted in easier to read documentation, improved error messages in the case of incorrectly named arguments, and better suggestions from the IDE and other static analysis tools. * Another major increase in test coverage, particularly focusing on the harder to test aspects such as subscriptions. Indirectly this will have a long term improvement on the stability of PyJapc. * There has been an overhaul of the PyJapc documentation. The methods have been split up into their own page, the content has been refreshed and there is now better use of standard Python syntax and object highlighting.
-
v2.2.2859afc1c · ·
* Fix the returned data type for numpy arrays. Since the move to JPype 1 these have been erroneously using an object dtype. The pre-JPype1 behaviour is now restored such that Java double arrays result in a numpy array with a dtype of double. * Boosted the test coverage of PyJapc in order to confirm that the code is functioning as expected with the new JPype
-
v2.2.1141fdeaf · ·
* Fix the setting of DiscreetFunction and DiscreteFunctionList values (2d arrays, and a list of 2 arrays respectively) using JPype1, which no longer allows access to private Java interfaces * Fix the type annotation files (``.pyi`` files) to reflect the PyJapc structure * Drop testing and support for ``JPype <1.1``
-
v2.2.0d26d9395 · ·
* Allow EnumSet values to be set using PyJapc.setParam (integers only) * Move pyjapc.pyjapc to a private module. Previous use of pyjapc.pyjapc.PyJapc should use move to pyjapc.PyJapc * Fix JPype 0.7 support for EnumSet with PyJapc.getParam * Improve the test coverage of Java primitive type conversion, as well as conversion to/from Enum and EnumSet
-
v2.1.0ac9bc4aa · ·
* PyJapc.clearSubscriptions can now be passed parameterName and selector * Preliminary JPype 0.7 support was added. Please report any issues encountered. * Parameter headers now include the setStamp value * Subscriptions no longer hold on to references to Python objects unnecessarily, thus avoiding potential memory problems with many subscriptions * The PyJapc Java dependencies were updated, with the obsolete ``japc-ext-cmwrda`` dependency being removed entirely * Minor improvements to the documentation and test coverage * PyJapc is now using the new cmmnbuild-dep-manager registration (via entry-points) for a more robust installation and Python wheel support
-
-
-