Gijs Molenaar

we already use mypy and flake8: https://github.com/gijzelaerr/python-snap7/tree/master/.github/workflows

since python-snap7 is a thin wrapper around snap7, this is actually a bug in the snap7 lib. So the long-term solution is to report it upstream. The only problem is...

there have been no commits to the repo for more than a year... @EnricGarrigo if you could report the issue upstream and link back here that would be useful.

I actually don't own a PLC, so I can't help you, unfortunately.

the philosophy is described in the snap7 documentation. the library object is a ctypes wrapper around the lower level snap7 shared library.

at what point shall we close this issue?

cool, cool, what do you think yourself? do you find it more suitable than the normal ctypes layer?

i had good experiences with CFFI, didn't try out pybind11+ yet, so not sure how they compare. I know it is a header-only solution. We can also try to write...

seems to have the same result: https://gist.github.com/gijzelaerr/57d58be34d9f98fb3dcc1e82242b6312

nope, just a normal x86_64 OSX 10.15. I guess the osx toolchain is already preparing the binaries for the upcoming switch to arm arch.