Chris Nuernberger

Hey, thanks, an embedded use case is an interesting pathway for sure. The entire stack trace would be helpful. That method gets called from a lot of potential places. On...

That stack trace did help but I am stumped a bit. The module object created by calling 'add-module' has no `__name__` attribute which seems to be a failure in the...

That is great. One thing I noticed is that you are running in a 32 bit arm environment. While I tried to make everything just work on 32 bit environments,...

I have none of those things lying around :-). Well, probably a micro-usb cable here or there. As I said, I think the first move is to get the entire...

OK, if we want to go here I think it will be instructive for all of us. The python bindings assume 64 bit architectures in a few places. The first...

`clj-python/libpython-clj-2.00-beta-1` now supports 32 bit architectures via a ton of work to the ffi interface in dtype-next. If you have a moment, could you please test this out?

Hmm. What is the output of `libpython-clj2.python/initialize!`?

OK, this is helpful. 1. Could you output all of the output from the initialization procedure? There is a bunch of logging showing how libpython-clj decides which pythons to try....

Ah, ok, could you include `ch.qos.logback/logback-classic {:mvn/version "1.1.3"}` in your dependencies? This will allow logging to work in your case. The issue there is something brought in slf4j (libpython-clj does...

OK, so does "/data/data/com.termux/files/usr/lib/libpython3.9.so.1.0" exist? Or any libpython*so file in that location? The problem just comes down to finding the correct shared library to load if there is one. Note...