requirements rather than mpy file?

dglaude commented 3 years ago

Maybe you should just put a requirement file that can be used to automatically download the lib, maybe circup can do that.

Adafruit also has a system to auto discover what is needed and one to produce a zip with all the project code. But that is only for learn guide project (I guess).

jliu70 commented 3 years ago

adafruit_debouncer.mpy adafruit_display_shapes adafruit_display_text adafruit_displayio_layout adafruit_hid adafruit_imageload adafruit_led_animation adafruit_macropad.mpy adafruit_midi adafruit_pixelbuf.mpy adafruit_simple_text_display.mpy neopixel.mpy

robotastic commented 3 years ago

Thanks @jliu70 & @dglaude - thanks I have been brute forcing the tooling for Circuit Python. I will go check out and see what better approaches there are for describing what packages are needed.

jliu70 commented 3 years ago

I'd recommend using circup and a requirements.txt file with the contents:

adafruit_debouncer
adafruit_display_shapes
adafruit_display_text
adafruit_displayio_layout
adafruit_hid
adafruit_imageload
adafruit_led_animation
adafruit_macropad
adafruit_midi
adafruit_pixelbuf
adafruit_simple_text_display
neopixel

Then it would be as straight forward as using circup install -r requirements.txt

More info here: Learn: John Park's CircuitPython Parsec: CircUp CircuitPython Updater https://blog.adafruit.com/2021/09/17/john-parks-circuitpython-parsec-circup-adafruit-johnedgarpark-adafruit-circuitpython/
https://www.youtube.com/watch?v=TXKoDqLprgY (9/17/2021)

https://learn.adafruit.com/keep-your-circuitpython-libraries-on-devices-up-to-date-with-circup/

https://circup.readthedocs.io/en/latest/

I've been using circup since I first learned of it from John Park's Parsec on 9/17/2021, and it's been really great.

robotastic / macropad-tic-tac-toe

requirements rather than mpy file? #1