@jsjames currently I’m working on 2 things in parallel.
First one is the jython binding, where I follow the development process of jython itself and keep the binding up to date with the latest jython releases. Additionally I observe the progress of the python3 implementation.
My own python scripts are based on this binding. I use my own python abstraction layer to make my live easier. I would recommend this for technical experienced users, because it is very close to the openhab java API, with the advantage that you can do absolutely anything.
For long term, I work on a python binding which should base on graalpy. I don’t know when this will be ready, because I currently have problems that I don’t really understand. Help is always welcome here. The current state is, that from the source code side I converted the jython binding completely to a version which uses the graalvm polyglot api and compiles absolutely fine with dependencies to “org.graalvm.python”. But if I start the openhab demo system I get exceptions that the binding don’t find the polyglot based python language implementation. I’m already active on the graalpy slack channel and get some hint some graalvm developers. My guess is that this is related to the maven package process.