For linux: creates running 'manifest' of bluetooth devices around you with their RSSI
-
didn't want to bother with a database, so I had 'buildManifest.py' literally write entries into 'manifest.py'.
-
this does a couple things. it means that you have a listing accessable by all other programs, and a dictionary for all your python programs.
-
I was using this for bluetooth tracking, but can definitely be used for a bunch of other purposes.
It is only being used here as it properly starts bluetoothctl (which I had a hard time doing in my own shell script),
and prints a nice feed to look at while buildManifest.py runs. All the data is collected and processed by my own code
in buildManifest.py.
because you're updating manifest.py with each run of buildManifest.py. You need to restart a program that has ported
manifest.py in order to get any updates to it. I suggest a control program that uses subprocess to call each .py
script using manifest.py. This allows for manifest.pyc to be regenerated with each run.