Open tobiasjaster opened 3 months ago
Hi @tobiasjaster, it seems your PR in the mbed repository got stalled with several CI fails. No further updates?
As I mentioned in the PR, it's probably not worth fixing the bugs because the tools folder has been freed since 6.2 and then the tool system will be changed at some point (if it's still being worked on?!?). That's why I'm currently considering whether I should go to the trouble of fixing the errors.
What about the freeze in the mbed-os repository, if rework is necessary?
Thanks for the info. According to this post:
Changes to the legacy Mbed Tools are limited to absolutely critical issues only.
IMO, support for the newer Python versions is somewhat critical, so they might be interested in your PR. Anyway, I will keep this issue open even though the problem is mostly related to the framework itself.
Good to know. Then I would endeavour to fix the problems again.
After I upgraded my python to 3.12, I encountered several problems with the platformio-framework-mbed. First, I had to update the "past" module because python3.12 no longer supports "imp". This was relatively easy to do by updating the dependencies of the "future" module to 0.18.3 (1.0.0 should also work in the meantime). In addition, the distutils dependencies in the mbed-os tools had to be removed. If the PR is merged in the mbed-os repository (https://github.com/ARMmbed/mbed-os/pull/15517), an update of the future-module could ensure Python3.12 compatibility in the future