MicroPython Forum (Archive)

Yes the firmware in that case contains everything. 'rebuild' is perhaps not the best word for it, IIRC the Makefile is smart enough to figure out that if you only change one source file of the module it's only going to build/link that object file.

I tried converting the features0 example in examples/natmod

Do you really need native modules? 'user modules' are quite a lot easier to work with, plus have C++ examples: examples/usercmodules/cppexample. And micrpython-wrap also works that way.

needs to be
?

Bit hard to tell, but sounds ok to me to put those arrays in a separate module for clarity; doesn't necessarily mean they should be globals though: you could have functions like def LargeArrayA(): return [......] def LargeArrayB(): return [......] But that's just an idea, I'd probably recommend tryi...

You probably should have a look at other small Python projects, and micropython's own python code to see how things are structured. Modules are for grouping functionality i.e. functions and classes, something like 'import my_variables' and 'import my_arrays' is the opposite and looks like a red herr...

Posetd here: https://github.com/micropython/micropython/issues/8366

Something is very wrong here. Windows port for test3 (and 10 iterations of that just to make sure): dict 15.809 int 3406.55 float 22.054 Seems worth creating a Github issue for this: while it's not suprirising creating a generator has an overhead, the differences observed here are so large it's eith...

None of micropython-lib is included in firmware by default actually, not for any port.

Perhaps you were looking at CPython examples?

MicroPython indeed does not implement those functions: http://docs.micropython.org/en/latest/g ... s.html#str

Didn't check in detail, but the non-eventdriven version is one big loop hence line is on the stack as long as the program runs and as such doesn't get garbage collected because the mark phase will see it being on the stack?