To update or not to update µpython ?

General discussions and questions abound development of code with MicroPython that is not hardware specific.
Target audience: MicroPython Users.
Post Reply
mcc
Posts: 14
Joined: Fri Oct 30, 2020 4:41 am

To update or not to update µpython ?

Post by mcc » Tue Nov 03, 2020 12:37 pm

Hi,

I am unsure, when to update the mycropython on my board:
Usually I tend more to the unstable/"bleeding edge" kind of software (in general) then to the other end, where
is as stable as old (exaggerating a lot here.. ;)

I have a clone of the mycropython repo (github) on my harddisk. Last change according to the log
is: "Date: Thu Oct 29 17:36:04 2020 +1100 by Damien".

If I take a look to the daily builds (for the generic ESP32, WROVER-B) I find:
GENERIC-SPIRAM : esp32spiram-idf4-20201103-unstable-v1.13-148-ged7ddd4dd.bin
GENERIC-SPIRAM : esp32spiram-idf4-20201029-unstable-v1.13-143-g25c4563f2.bin
GENERIC-SPIRAM : esp32spiram-idf4-20201029-unstable-v1.13-127-g368c1a096.bin
GENERIC-SPIRAM : esp32spiram-idf4-20201028-unstable-v1.13-126-g05f95682e.bin

of the last four days (this is the firmware version I am currently using). All builds have a different
hash...therefore there is some change....or isn't (according to the log)?

I obviously miss something...? ;)
A "git pull" says "...is up to date"...

If something was change...where can I find, what it was?

Cheers,
mcc

stijn
Posts: 546
Joined: Thu Apr 24, 2014 9:13 am

Re: To update or not to update µpython ?

Post by stijn » Tue Nov 03, 2020 12:42 pm

esp32-idf41-cmake is a separate branch in the main MicroPython repository, whereas you use the master branch (which is completely fine)

mcc
Posts: 14
Joined: Fri Oct 30, 2020 4:41 am

Re: To update or not to update µpython ?

Post by mcc » Tue Nov 03, 2020 12:50 pm

Hi,

ah...ok...

I did a "git checkout esp32-idf41-cmake; git log" (I am on linux) and got the same log as before: Newest change is 29.10.
How can I read of the latest changes of this specific branch?
Thanks a lot for any help in advance!
Cheers!
mcc

User avatar
jimmo
Posts: 2072
Joined: Tue Aug 08, 2017 1:57 am
Location: Sydney, Australia
Contact:

Re: To update or not to update µpython ?

Post by jimmo » Tue Nov 03, 2020 1:08 pm

In general I would recommend just using the release versions unless you have a specific fix or feature you require from the unstable versions.

Something to remember is that the date shown for a commit in git log is not necessarily the date that commit was added to that branch but rather when the commit was first created (even if it has been rebased since). So for example if you scroll through the git log, the dates jump around a bit.

In particular, the commit "Date: Thu Oct 29 17:36:04 2020 +1100 by Damien" was committed at 23:35, likely after the g25c4563f2 build was made.

mcc
Posts: 14
Joined: Fri Oct 30, 2020 4:41 am

Re: To update or not to update µpython ?

Post by mcc » Tue Nov 03, 2020 2:33 pm

Hi,

thanks for your help ! :)

Cheers!
mcc

Post Reply