There is a python interface to HAL, pyhal, that loads liblinuxcnchal.so (CDLL interface). It accesses the underlying HAL memory and data directly and has no volatility idea, knowledge or consideration. It also violates a separation policy we want to enforce (like in a getter/setter interface).
The normal HAL interface from python is hal (halmodule), but that lacks the port interface, which is used by the raster component (see the entertaining link in #2644). I suggest that the port type gets implemented in hal and the pyhal module retired asap.
A quick grep to see where pyhal is imported comes up with these file matches:
configs/sim/axis/laser/python/remap.pylib/python/raster.pytests/pyhal/testtests/raster/test
All these files are related to laser/raster operation and should be easily portable when hal has the port interface.
Does anybody know of other places where pyhal is used?
There is a python interface to HAL,
pyhal, that loadsliblinuxcnchal.so(CDLL interface). It accesses the underlying HAL memory and data directly and has no volatility idea, knowledge or consideration. It also violates a separation policy we want to enforce (like in a getter/setter interface).The normal HAL interface from python is
hal(halmodule), but that lacks theportinterface, which is used by the raster component (see the entertaining link in #2644). I suggest that the port type gets implemented inhaland thepyhalmodule retired asap.A quick grep to see where
pyhalis imported comes up with these file matches:configs/sim/axis/laser/python/remap.pylib/python/raster.pytests/pyhal/testtests/raster/testAll these files are related to laser/raster operation and should be easily portable when
halhas the port interface.Does anybody know of other places where pyhal is used?