Python 3.6 client for aarch64/arm64 Linux?

[swjz]

Hi!

Can I ask why there's no Python 3.6 client for aarch64/arm64 Linux on PyPI (https://pypi.org/project/pulsar-client/#files)? I have a NVIDIA Jetson Nano and it only has GPU support for Python 3.6, so I tried to compile the Pulsar C++ client from source. I followed instructions from #14673, added -DBUILD_TESTS=OFF flag and got _pulsar.so. The installation was successful, but when I tried to import _pulsar from Python 3.6, I got ImportError: dynamic module does not define module export function (PyInit__pulsar).

I was able to compile Pulsar C++ client from source against Python 3.8 on the same device, and it worked smoothly. I wonder if Pulsar doesn't support Python 3.6 on arm64 devices or maybe I did something wrong?

Thanks a lot for your help!

[BewareMyPower]

You need to confirm which Boost.Python library did you link when you compiled the Python client.

See https://github.com/apache/pulsar-client-python/blob/d14aada9fc418c99f4be58f58289d1b884bcabdc/CMakeLists.txt#L56, it doesn't try to find a Boost.Python for 3.6

[BewareMyPower]

Could you go to the directory of _pulsar.so and run the following commands?

python3 -c 'import _pulsar'
ldd _pulsar.so

[swjz]

nano@nano3:~/pulsar/pulsar-client-cpp/python$ python3 -c 'import _pulsar'
Traceback (most recent call last):
  File "<string>", line 1, in <module>
ImportError: dynamic module does not define module export function (PyInit__pulsar)
nano@nano3:~/pulsar/pulsar-client-cpp/python$ ldd _pulsar.so
        linux-vdso.so.1 (0x0000007f889e8000)
        libboost_python3-py36.so.1.65.1 => /usr/lib/aarch64-linux-gnu/libboost_python3-py36.so.1.65.1 (0x0000007f8848e000)
        libprotobuf.so.10 => /usr/lib/aarch64-linux-gnu/libprotobuf.so.10 (0x0000007f88222000)
        libcurl.so.4 => /usr/lib/aarch64-linux-gnu/libcurl.so.4 (0x0000007f881a2000)
        libboost_system.so.1.65.1 => /usr/lib/aarch64-linux-gnu/libboost_system.so.1.65.1 (0x0000007f8818d000)
        libssl.so.1.1 => /usr/lib/aarch64-linux-gnu/libssl.so.1.1 (0x0000007f88103000)
        libcrypto.so.1.1 => /usr/lib/aarch64-linux-gnu/libcrypto.so.1.1 (0x0000007f87ec2000)
        libz.so.1 => /lib/aarch64-linux-gnu/libz.so.1 (0x0000007f87e95000)
        libdl.so.2 => /lib/aarch64-linux-gnu/libdl.so.2 (0x0000007f87e80000)
        libpthread.so.0 => /lib/aarch64-linux-gnu/libpthread.so.0 (0x0000007f87e54000)
        libc.so.6 => /lib/aarch64-linux-gnu/libc.so.6 (0x0000007f87cfb000)
        /lib/ld-linux-aarch64.so.1 (0x0000007f889bc000)
        libstdc++.so.6 => /usr/lib/aarch64-linux-gnu/libstdc++.so.6 (0x0000007f87b67000)
        libgcc_s.so.1 => /lib/aarch64-linux-gnu/libgcc_s.so.1 (0x0000007f87b43000)
        libnghttp2.so.14 => /usr/lib/aarch64-linux-gnu/libnghttp2.so.14 (0x0000007f87b13000)
        libidn2.so.0 => /usr/lib/aarch64-linux-gnu/libidn2.so.0 (0x0000007f87ae7000)
        librtmp.so.1 => /usr/lib/aarch64-linux-gnu/librtmp.so.1 (0x0000007f87abd000)
        libpsl.so.5 => /usr/lib/aarch64-linux-gnu/libpsl.so.5 (0x0000007f87a9f000)
        libgssapi_krb5.so.2 => /usr/lib/aarch64-linux-gnu/libgssapi_krb5.so.2 (0x0000007f87a4e000)
        libldap_r-2.4.so.2 => /usr/lib/aarch64-linux-gnu/libldap_r-2.4.so.2 (0x0000007f879f5000)
        liblber-2.4.so.2 => /usr/lib/aarch64-linux-gnu/liblber-2.4.so.2 (0x0000007f879d8000)
        libm.so.6 => /lib/aarch64-linux-gnu/libm.so.6 (0x0000007f8791f000)
        libunistring.so.2 => /usr/lib/aarch64-linux-gnu/libunistring.so.2 (0x0000007f8779c000)
        libgnutls.so.30 => /usr/lib/aarch64-linux-gnu/libgnutls.so.30 (0x0000007f8763b000)
        libhogweed.so.4 => /usr/lib/aarch64-linux-gnu/libhogweed.so.4 (0x0000007f875f9000)
        libnettle.so.6 => /usr/lib/aarch64-linux-gnu/libnettle.so.6 (0x0000007f875b8000)
        libgmp.so.10 => /usr/lib/aarch64-linux-gnu/libgmp.so.10 (0x0000007f8753b000)
        libkrb5.so.3 => /usr/lib/aarch64-linux-gnu/libkrb5.so.3 (0x0000007f8746b000)
        libk5crypto.so.3 => /usr/lib/aarch64-linux-gnu/libk5crypto.so.3 (0x0000007f8742d000)
        libcom_err.so.2 => /lib/aarch64-linux-gnu/libcom_err.so.2 (0x0000007f87419000)
        libkrb5support.so.0 => /usr/lib/aarch64-linux-gnu/libkrb5support.so.0 (0x0000007f873ff000)
        libresolv.so.2 => /lib/aarch64-linux-gnu/libresolv.so.2 (0x0000007f873da000)
        libsasl2.so.2 => /usr/lib/aarch64-linux-gnu/libsasl2.so.2 (0x0000007f873b2000)
        libgssapi.so.3 => /usr/lib/aarch64-linux-gnu/libgssapi.so.3 (0x0000007f8736a000)
        libp11-kit.so.0 => /usr/lib/aarch64-linux-gnu/libp11-kit.so.0 (0x0000007f87258000)
        libtasn1.so.6 => /usr/lib/aarch64-linux-gnu/libtasn1.so.6 (0x0000007f87237000)
        libkeyutils.so.1 => /lib/aarch64-linux-gnu/libkeyutils.so.1 (0x0000007f87223000)
        libheimntlm.so.0 => /usr/lib/aarch64-linux-gnu/libheimntlm.so.0 (0x0000007f8720a000)
        libkrb5.so.26 => /usr/lib/aarch64-linux-gnu/libkrb5.so.26 (0x0000007f87180000)
        libasn1.so.8 => /usr/lib/aarch64-linux-gnu/libasn1.so.8 (0x0000007f870ea000)
        libhcrypto.so.4 => /usr/lib/aarch64-linux-gnu/libhcrypto.so.4 (0x0000007f870ab000)
        libroken.so.18 => /usr/lib/aarch64-linux-gnu/libroken.so.18 (0x0000007f87088000)
        libffi.so.6 => /usr/lib/aarch64-linux-gnu/libffi.so.6 (0x0000007f8706e000)
        libwind.so.0 => /usr/lib/aarch64-linux-gnu/libwind.so.0 (0x0000007f87036000)
        libheimbase.so.1 => /usr/lib/aarch64-linux-gnu/libheimbase.so.1 (0x0000007f87019000)
        libhx509.so.5 => /usr/lib/aarch64-linux-gnu/libhx509.so.5 (0x0000007f86fc7000)
        libsqlite3.so.0 => /usr/lib/aarch64-linux-gnu/libsqlite3.so.0 (0x0000007f86ecc000)
        libcrypt.so.1 => /lib/aarch64-linux-gnu/libcrypt.so.1 (0x0000007f86e84000)

[BewareMyPower]

I'm not sure if it's a bug for ARM arch with Python 3.6, you could try building the _pulsar.so in a x86 arch Linux with Python 3.6 and test with python3 -m 'import _pulsar'.

Regarding the question before:

Can I ask why there's no Python 3.6 client for aarch64/arm64 Linux on PyPI

Python 3.6 has already reached EOL, see https://endoflife.date/python.

[swjz]

Thanks a lot! One more thing, is there a docker image for ARM arch as well? I see on https://hub.docker.com/r/apachepulsar/pulsar/tags there seems to be linux/amd64 images only, and if I pull up that image, I'm getting this error:

$ sudo docker run -it --name pulsar -p 6650:6650  -p 8080:8080 --mount source=pulsardata,target=/pulsar/data --mount source=pulsarconf,target=/pulsar/conf apachepulsar/pulsar:2.10.1 bin/pulsar standalone
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
standard_init_linux.go:228: exec user process caused: exec format error

[BewareMyPower]

#17733 The first ARM based official image might be released by 2.12.0 or later.

[merlimat]

@swjz We have decided to only support Python versions that are actively maintained: https://endoflife.date/python