This message was deleted.

Hi, thanks for your interest in helping with this. I haven’t looked at this for a while, but I think where we are currently is: • The Python lib is only using 2.x features (for the most part at least) so some tests and probably corresponding production code changes are needed to take advantage of 3.x features. • Basic Testcontainers implementation is working well but we’re lacking specific Python bindings for most of the startup options meaning you have to construct CLI parameters instead (which isn’t a great experience). • Community feedback about the native version is that folks don’t like having a big Java JAR baked into the distribution so I think we’d be better off removing this and focusing on the two other use cases - connecting to a remote server and Testcontainers. This does present a bit of a backwards compatibility issue though, so we could do something along the lines of downloading the JAR on demand if you explicitly choose that strategy, rather than having it there all the time.