Quote:
Originally Posted by blakeelias
When there's an error can't it just sit there and wait for you to load new code? Maybe that's something that could be done in robot.py inside of run(), if it catches an exception then checkRestart() continuously.
|
Waiting for new code would be good. However, if possible, it shouldn't be done in robot.py. I like the fact that run() exists because it lets you see what the code is doing (unlike in C++, where they use a magic macro), but checking for new code seems like it should really be somewhere other than user code (robot.py). It's probably possible to do it outside of user code though.
Quote:
Originally Posted by Peter Johnson
By scanning the /py/ directory for updated date/time/size files (maybe non-ideal because of multiple files...)? Or wait for a joystick button press?
|
Joystick button press might work, but how will you know which joystick and button to use? I suppose you could just use joystick 1 button 1. It's unlikely that a team doesn't have a joystick plugged in...
Quote:
Originally Posted by Peter Johnson
Unfortunately the memory leak appears to be very difficult to fix (it's a leak in Python itself).
|
Is that this issue (that is fixed in Python
3.1.3)?
Quote:
|
Issue #4838: When a module is deallocated, free the memory backing the optional module state data.
|
Is it too difficult to move RobotPy to 3.1.3?