MicroPython Forum (Archive)

Was having some trouble sending data to an lcd today because of the AttributeError: 'UART' object has no attribute 'send'. Thinking that I'd screwed something up, it took me a long while to finally think to check a dir of the object I'd created: >>> import pyb >>> from pyb import UART >>> lcd = UART...

I've found that if you pull the pins low (As shown below), the module will re-start cleanly. Without this I would get the "Could not initialize the CC3000 module" error nearly every time. <snip> pyb.Pin.board.Y3.low() pyb.Pin.board.Y4.low() pyb.Pin.board.Y5.low() nic = network.CC3K(pyb.SPI(2), pyb.P...

pfalcon,
It's like adding a compile/link step to an interpreted environment. Silly, when a new command ("reimport", maybe?) could be introduced if the time/date check was considered too ponderous.

OTOH, I suppose I could just read the file from disk, and eval/exec it. (Yuck!)

Oh well...

(Apparently my replies are being deleted... WTF?) There's some misunderstanding here. The idea is to NOT, repeat NOT REBOOT, and be able to re-import an edited module. The steps involved should be as follows: 1. Module X gets imported. 2. A deficiency is found with module X. 3. Module X's code is ed...

(My response obviously got lost somewhere, I'll try to re-accomplish it.)

Note I said "without rebooting". The desktop python environment does this by checking file creation time to see if it needs to re-interpret the file, perhaps micropython can do something like that.

That's what I've been doing, but it occurs to me that python on other systems allows modules to be re-imported (Based on timestamp), so it might be available here, too.

Or, if it isn't, perhaps it should be?

You've written a module. You run it, and it's not quite right. Now, is there any way to re-import it instead of rebooting the board? Hmmm, the responses show a basic misunderstanding about the question, and for some reason I can't seem to post replies to this thread. Please note that the point of th...