-
Twitter API lives
Have they decided to keep the free tier after all?
Why would the import work in one directory but not elsewhere?
I'm not a python guy, but it sounds like the include path is relative to the script that you're trying to run. You'll either need to copy the libraries into your own directory, or somehow add the path of the waveshare libraries to the set of paths that python searches for libraries.
-
Have they decided to keep the free tier after all?
1500 free per month, more than most hobby projects will use I guess.
copy the libraries into your own directory, or somehow add the path
Thanks, makes sense. For now I ended up working with 4 scripts, 1 in /home/pi doing the work and that at different times calls each of 3 different display instructions subprocesses that I saved in the examples directory. I will revisit though.
Twitter API lives and it motivated me to start using that account again this week, with mixed results
Separately I got a waveshsare e-paper 2.13 display. The test script works fine and it cycles the screen through a few display layouts.
When I try to adapt the test.py for my purposes it fails as can't import waveshare_epd though. I saved it outside of the examples directory. The new .py runs if I move it back to the examples directory, where ideally I don't want to keep the script though.
Why would the import work in one directory but not elsewhere?