tracing/stepping with variable watch

[dz0]

locals() and globals() are available in Brython -- so one can show them on each step.

ps.: https://github.com/amrdraz/python-debugger is designed for Brython and probably is better than the one Reeborg uses now :)

[aroberge]

The way I evaluate the code is effectively to do eval(python_code). Brython's eval first transforms the python_code into javascript and then runs it: there is no stepping through the code. When an "atomic" javascript instruction is encountered, such as move(), its result is recorded in a "frame" where I record the entire state of the world at that point. When all the code execution is done, a series of such frames will have been recorded.

So, no stepping of the code takes place, and neither Brython's locals() nor globals() are necessarily available at a given step. If you recall,you can choose either Python or Javascript (or Coffeescript) as programming language.

After this code execution is done, I play back the frames one at a time with a specified time delay. The instruction "think(delay)" can be used in a given frame to change the delay between frames being shown from that point on.

The Python debugger you found looks like something extremely worthwhile to look at ... but it would mean changing significantly the way the program is run (and would likely not be compatible with the Javascript or Coffeescript implementation).

[dz0]

Probably what I call "stepping", is called "line highlighting" in Reeborg.

My idea/hack would be to inject variable "logging" alongside line highlighting

tracecall_name = 'print(list(locals().keys())); RUR.set_lineno_highlight'

[aroberge]

Oh, I see ... this makes sense, of course! It's definitely something I will want to explore.

[aroberge]

EDIT: narration (mentioned previously in this comment) has been changed to print_html; my plan is to enhance print_html.

I could not get something sensible that works. However, I could define a "watch" function, that would need to be called explicitly, and working like the following:

World("Empty")
no_highlight()
think(0)

r = UsedRobot()
def watch(*args):
    out = []
    for arg in args:
        try:
            out.append("{}: {}".format(arg, eval(arg)))
        except:
            pass
    print_html("<br>".join(out))

for i in range(3):
    move()
    watch("r.body.x", "r.body.y", "a")
    a = 3
    pause(1000)

Perhaps I could create a dialog where the variable to watch are entered; when this is done, then a call to watch() is inserted in the same way I enter the code to highlight lines of code being executed...

[dz0]

Strange issue with locals()

But in their demo env this works ok:

print( locals() )

http://brython.info/tests/editor.html?lang=en
Brython version: 3.2.3

but Reeborg uses a bit recent version -- maybe there's some bug?
http://cdn.rawgit.com/brython-dev/brython/3c551ae3bf6d29191f7f62bf0d2ce987d70fc340/www/src/brython.js
// implementation [3, 2, 4, 'alpha', 0]

ps.: adding watch variables via dialog is also a good way, imo :)
even easier to use might be a textbox, where one could list them (add or
delete)

On Sat, Dec 5, 2015 at 3:51 PM, André Roberge notifications@github.com
wrote:

I could not get something sensible that works. However, I could define a
"watch" function, that would need to be called explicitly, and working like
the following:

World("Empty")
no_highlight()
think(0)

r = UsedRobot()def watch(*args):
out = []
for arg in args:
try:
out.append("{}: {}".format(arg, eval(arg)))
except:
pass
narration("
".join(out))
for i in range(3):
move()
watch("r.body.x", "r.body.y", "a")
a = 3
pause(1000)

Perhaps I could create a dialog where the variable to watch are entered;
when this is done, then a call to watch() is inserted in the same way I
enter the code to highlight lines of code being executed...

—
Reply to this email directly or view it on GitHub
#196 (comment).

Jurgis Pralgauskis
tel: 8-616 77613;
Don't worry, be happy and make things better ;)
http://galvosukykla.lt

[aroberge]

The reason why locals() is behaving strangely I suspect is that I run the code using exec(src, some_dict) inside a function named generic_translation_python which prepopulates some_dict with some custom-defined functions, instead of a simple exec(src) which would only use the built-ins.

[aroberge]

I should add: Brython's 3.2.3 has bugs which I found and were affecting the way my program was working - which is why I linked to a newer version that had those bugs fixed.

[dz0]

hm, now world.html throws errors,

but in world_old.html I can get list of local vars

print(list(locals().keys()))

http://reeborg.ca/world_old.html?proglang=python-en&world=%7B%22robots%22%3A%5B%7B%22x%22%3A2%2C%22y%22%3A1%2C%22tokens%22%3A%22infinite%22%2C%22orientation%22%3A0%2C%22_prev_x%22%3A1%2C%22_prev_y%22%3A1%2C%22_prev_orientation%22%3A0%7D%5D%2C%22walls%22%3A%7B%7D%7D&editor=move()%0Aprint(list(locals().keys()))&library=%23%20'import%20my_lib'%20in%20Python%20Code%20is%20required%20to%20use%0A%23%20the%20code%20in%20this%20library.%20%0A%0A

On Sat, Dec 5, 2015 at 11:23 PM, André Roberge notifications@github.com
wrote:

I should add: Brython's 3.2.3 has bugs which I found and were affecting
the way my program was working - which is why I linked to a newer version
that had those bugs fixed.

—
Reply to this email directly or view it on GitHub
#196 (comment).

Jurgis Pralgauskis
tel: 8-616 77613;
Don't worry, be happy and make things better ;)
http://galvosukykla.lt

[aroberge]

I have changed the UI for this in two ways: adding placeholder text in the input which, hopefully should be nearly self-explanatory; using only one image/button which is used to toggle the input: if the input is invisible, no variable is watched. The previous "red magnifying glass" could be confusing: does pressing the red button means stop ... or does it mean that something is stopped?

[dz0]

seems nice! :) few notices:

• print("hi") doesn't seem to work..
  probably would be good to have "debug" output alongside "standart
  output".. Output pane could be split in two parts..?

• if the input is invisible, no variable is watched.
  If I toggle textbox to invisible, variables are still watchet/updated..

On Sun, Dec 6, 2015 at 4:52 PM, André Roberge notifications@github.com
wrote:

I have changed the UI for this in two ways: adding placeholder text in the
input which, hopefully should be nearly self-explanatory; using only one
image/button which is used to toggle the input: if the input is invisible,
no variable is watched. The previous "red magnifying glass" could be
confusing: does pressing the red button means stop ... or does it mean that
something is stopped?

—
Reply to this email directly or view it on GitHub
#196 (comment).

Jurgis Pralgauskis
tel: 8-616 77613;
Don't worry, be happy and make things better ;)
http://galvosukykla.lt

[dz0]

PS.: seems like I managed to get the list of system variables:

system_default_vars = list(locals().keys()) # before the user code

def filter_user_vars( vars ):
return set( vars ) - set( system_default_vars )

watch ( filter_user_vars( list(locals().keys()) ) ) # would call watch
with just vars from user code...

On Sun, Dec 6, 2015 at 8:26 PM, Jurgis Pralgauskis <
jurgis.pralgauskis@gmail.com> wrote:

seems nice! :) few notices:

• print("hi") doesn't seem to work..
  probably would be good to have "debug" output alongside "standart
  output".. Output pane could be split in two parts..?

• if the input is invisible, no variable is watched.
  If I toggle textbox to invisible, variables are still watchet/updated..

On Sun, Dec 6, 2015 at 4:52 PM, André Roberge notifications@github.com
wrote:

I have changed the UI for this in two ways: adding placeholder text in
the input which, hopefully should be nearly self-explanatory; using only
one image/button which is used to toggle the input: if the input is
invisible, no variable is watched. The previous "red magnifying glass"
could be confusing: does pressing the red button means stop ... or does it
mean that something is stopped?

—
Reply to this email directly or view it on GitHub
#196 (comment).

Jurgis Pralgauskis
tel: 8-616 77613;
Don't worry, be happy and make things better ;)
http://galvosukykla.lt

Jurgis Pralgauskis
tel: 8-616 77613;
Don't worry, be happy and make things better ;)
http://galvosukykla.lt

[aroberge]

Fixed broken print. I was trying to be too smart, appending the output of the watch to the previous recorded frame so that they would appear to be kept in sync. However, because both the watch() and the print() used a code of "output" for the frame, the watch appended would effectively replace the print.

I need to fix the toggle so that it works properly.

I'll look at your smart filtering option some time later today.