Closed krzema12 closed 2 years ago
By the way, it's getting more difficult to update the both targets. First of all, our main target remains plain Python, right? And MicroPython is just an indicator of current state?
We could, for example, move reports generation to CI, to a special branch for it. I've done it for GH Pages here, should be similar in our case. If you like the idea, I can try doing it.
Yeah, I realize that MicroPython means some extra complexity and burden when contributing :sweat: I also thought about automating report generation, like you propose. I propose to merge it as is for now, and we can have a follow-up story to move it to CI. It would be cool if you could give it a try.
Main target - yes, Python. However, I hope that we'll ultimately also support MicroPython. We should actually already start taking it into account when making changes in the compiler.
Adding data about MicroPython to the SVG git plot will be done in another PR. Here we deal only with text reports.