Closed jaconstantine closed 6 years ago
ARM CPUs should be fine, but the code requires Python 3.6+. I haven't made any attempt to have backwards compatibility.
Python 2.7 will no longer be supported by the Python Software Foundation in 17 months. Unfortunately, setup.py doesn't automatically prevent installation of incompatible packages, I suppose I could put a version check in the I put a version check in the setup.py to prevent installation, with a nice error message, on older versions of Python.setup.py
.
Have you tried running using the python3 binary? (Just swap in python3 for python in your commands.) Is installing 3.7, or 3.6, an option for you? (It isn't too difficult, but might take half an hour on a Pi if your distribution doesn't have a package for it.) If not, a docker image would work. (Docker is something I've been meaning to add to this library, but haven't done so yet.)
Also, it doesn't appear you are using a virtual environment. It's not advisable to install libraries into the system Python, as it can create conflicts with libraries and scripts the system depends on. For example, if this library used the requests library, but required a newer version that had a breaking change it could break your system.
Release 0.1.4 prevents installation on 2.7. https://github.com/TomFaulkner/SenseMe/releases/tag/v0.1.4 https://pypi.org/project/senseme/
Thanks for taking a look. Raspbian jessie doesn't have python3.6, the newest is python3.4. This is a remote embedded application so I won't be upgrading to stretch for a while.
I think it would be best to install 3.7 from source then. pyenv makes it convenient.
I make use of fstrings, which is a 3.6 feature. If those were replaced with the older format methods it would run on 3.5. I don't know if there is anything that wouldn't run on 3.4 other than that.
installation:
cli:
usage:
Is this an arm issue or a known issue with 2.7?