This is not my experience. Exception handling works. And with careful design long term running is no problem. I have an application which uses four pyboards communicating over radio links. The inherent unreliability of radio links means that it uses a considerable amount of exception handling. Aside from takedowns for updates it has been running for two years, with the last year's operation being entirely uninterrupted.liudr wrote: ↑Sun Apr 08, 2018 3:41 pm...No or hard-to-find well-documented exception handling, for instance, prevents developers from preparing programs for exceptions say from networking. Everything is assuming ideal situations in sample code, like that of Arduino. That will work for hours or even for days in reality but will break down when you think you've done a good job...
Trying to understand uos vs os
- pythoncoder
- Posts: 5956
- Joined: Fri Jul 18, 2014 8:01 am
- Location: UK
- Contact:
Re: Trying to understand uos vs os
Peter Hinch
Index to my micropython libraries.
Index to my micropython libraries.
Re: Trying to understand uos vs os
Where do I find some docs then? I want a list of exceptions generated by each module and what cause the exceptions.
For instance the network module:
https://docs.micropython.org/en/latest/ ... twork.html
I'd like to see what exception(s) the network.connect() might generate and I just couldn't find that information. Maybe I am not looking at the right place.
For instance the network module:
https://docs.micropython.org/en/latest/ ... twork.html
I'd like to see what exception(s) the network.connect() might generate and I just couldn't find that information. Maybe I am not looking at the right place.
Re: Trying to understand uos vs os
In order to import the non-u modules, you need to copy them onto your pi and make sure that sys.path points to the right place.