Today is the last day for #CircuitPython2023. However, if you need more time, just email and we’ll wait for you before doing the final wrap up post. When you post, please email [email protected] to let us know. (Email us even if you miss the “deadline”.)
We’ve gotten a couple more #CircuitPython2023 posts! Thank you all!
Mark (aka @[email protected], @Gamblor on the Adafruit Discord) posted to Mastodon.
I have been thinking what to write for #circuitpython2023. I felt like I did not contribute much in 2022, but looking back at GitHub was a great reminder to me of what I did accomplish (even if some wasn’t directly CircuitPython related).
I do not have any specific feature I would like to see added, but I hope I can continue to contribute picking up smaller community core requests that may not be top priority for the core team. Bonus points for flashy/showy requests.
tekktrik posted a GitHub gist. Here is the introduction (there is much more detail in the post):
My hope (and personal goal) for #CircuitPython2023 is to improve the #CircuitPython development experience, particularly for users. I’ve especially been interested in creating tools for intermediate users, as the entry/beginner experience for CircuitPython is already phenomenal – so much so that (at least in my own case) afterwards they start looking for more advanced opportunities. In 2022, I created build-mpy for allowing users to create .mpy files for their projects using GitHub Actions. I also personally created circlink as a way to develop and test user code for microcontrollers from a local repository on the computer. Additionally, moving much of the existing CI in the libraries to shared compositve actions means both that there’s often less patching to do when upgrades happen, and that both Adafruit and Community bundles get these improvements passively, with no opt-in required.
axelmagnus posted to the Adafruit Forum:
Sparklines – see https://github.com/adafruit/Adafruit_Ci … /issues/25
I would so much like to be able to present say, 144 h of data , 72 points, from my feeds in a (or even more!!) sparkline on my Pyportal. It seems made for it! But with a couple of buttons to change feed, progress bar and sounds, there is not much memory, so is there possibly a way to make the sparkline more memory efficient?
by using vectorio, that dont use bitmaps as suggested by Kmatch https://github.com/adafruit/Adafruit_Ci … -824823875
or any other way?Some other things that has sprung to mind
* be able to set feed callback functions in the pyportal object for easy display updates. Maybe it is?
* github link and project bundle at the top of the learn guides
* each guide project separate repo for easy cloningCheers,
Axel
#CircuitPython2023 is our annual reflection on the state of CircuitPython. We’d love to hear from you too! See the kick-off post for all of the details. Please post by January 18th.
Past posts:
- Footleg posted on Twitter and Mastodon.
- Bill Minarick (aka @[email protected]) posted on Mastodon.
- TreasureDev (aka @[email protected], @DJDevon3 on the Adafruit Discord) posted on Mastodon.
- Bradán Lane (aka @[email protected]) posted on Mastodon.
- Andy Warburton (aka @[email protected]) posted twice on Mastodon.
- Stylus (aka @[email protected], @jepler on the Adafruit Discord) posted a longer post on Mastodon covering challenges in 2022 and goals for #CircuitPython2023.
- Seth Kerr (aka @[email protected], @skerr on the Adafruit Discord) posted on Mastodon.
- Ladyada and pt talked about it on the Python on Hardware portion of Ask an Engineer last night.
- ComfortableAd9286 posted on r/CircuitPython.
- JohnHind posted on the CircuitPython forum.
- Anne (aka @anne_engineer) posted on Twitter
- Tim (aka @FoamyGuy on Discord) posted to GitHub.
- dglaude posted on Adafruit Learn.
- Dan posted on the Adafruit Blog.
