explicitly define build environment about open-race-scale HOT 3 CLOSED

Python dependencies don't default to anything. It depends on your environment. If you were running pip for python 2.7, the libraries got installed to python 2.7, and then I agree it wouldn't work.

This code is essentially pre-alpha and anyone trying it at this point would be running the code from an IDE anyways. I don't think I have even tried to run kivy on the Pi yet. I have just been getting everything ready in Windows.

I'm probably going to reorganize this repo (move hw stuff to separate repo) then I can make a python package so dependencies get installed automatically.

from open-race-scale.

I will improve the docs soon, but you should not have to do anything fancy to get this to work on a Pi, unless you are using an older Pi OS image that doesn't have Python 3.x.

Step should basically be:
Grab latest RPi NOOBS image from RPi website and load onto Pi
`pip3' install the dependencys (which I will list soon in readme)
git pull this repo and run main.py

Once I have assembled hardware I will make a proper pip package so that it's easy to install.

from open-race-scale.

The issue is your dependencies default in most cases to a python2.7 build regardless of if they work in 3 or not. Kivy is a classic example. Most utils don't default to python3 yet and as a courtesy devs using 3 typically call it out.

There were also a couple of gcc libs that were dependencies of of the dependencies. For someone that works in the shell it's not an issue, for regular users it's a gigantic issue. I've seen it hundreds of times. The people that are going to use your project want to build and use scales, not hack the shell. The easier you make if for them to do that, the more successful your project will be.

from open-race-scale.