The core of this project is the code_tracer.py file that runs the user's script and builds a display of its execution. That script can be called from any editor, so it's not too hard to add basic support for live coding in another editor like vim, Atom, or Sublime. The first version doesn't need to worry about more complicated features like turtle graphics.

The Emacs support was generously contributed by users, so I'm adding this issue with the help wanted label to ask for contributions for other editors. Just add a comment here, or start a new issue describing the editor you want to work on.

You can find some general guidance in the contributing fiile.

• [x] implement plugin
• [x] adapt to space_tracer changes
• [x] package the plugin
• [x] publish in the marketplace
• [x] update the developer docs for publishing a release
• [x] test installing from the marketplace, after it is accepted
• [x] update installation instructions to use the marketplace

Would you be interested in adding support for matplotlib?

Currently, examples using that library prints nothing.

It would be neat if the matplotlib.figure.Figure called p below were shown in a buffer.

import seaborn as sns
sns.set(style="ticks")

# Load the example dataset for Anscombe's quartet
df = sns.load_dataset("anscombe")

# Show the results of a linear regression within each dataset
g = sns.lmplot(x="x", y="y", col="dataset", hue="dataset", data=df,
               col_wrap=2, ci=None, palette="muted", size=4,
               scatter_kws={"s": 50, "alpha": 1})#.getfig()

p = g.fig

Example from here: Anscombe’s quartet

Environment: Windows XP 32-bit JRE SE 7 U21 10.21.2.11 Python 3.3.2 (that's CPython, not Iron Python, Jython, or a more exotic implementation) Eclipse Classic 4.2.2 PyDev 2.7.5.2013052819 live-py 2.5.0.201304211713

Error: Live evaluation window does not appear. The menu entry itself /does/ appear, and responds to being checked/unchecked.

Message from Error Log: "Plug-in live-py was unable to load class live_py.PyEditDecorator."

Eclipse and PyDev itself appear to be functional (e.g. Python code completion works, as does live syntax checking, and executing valid code and viewing the output in the console).

This occurs reliably.

Downgrading the version of live-py to the previous version, and upgrading PyDev to the nightly version, did not change anything.

Knowledge of any workarounds would be appreciated. I may have installed something wrong, but I followed the instructions as best I could.

I attempted to report this bug before on the blog, but my posting was deleted for some reason. Since I had already deleted the installation of everything, I had to re-install just to get the information to resubmit the bug report here, once I found out how. I hope it won't be ignored or destroyed a second time.

File->New->PyDev Project->demo->Finish

Right click on demo project in PyDev Package Explorer,->New->File->demo.py Type code "s='hello'",but the code is shown as "'olleh'=s"(that is to say when you type a letter such as 's',the cursor automatically jump to begin of 's' ) and no result display.

Tested with:

Win7 32bit+python 2.7.3+eclipse 3.7,3,8 and 4.0+pydev.org/updates

ubuntu 11.04+python 2.6.5+eclipse 3.7,3.8+pydev.org/updates

Pydev 2.5, 2.6 works well with live-py_2.0.0.201209171018.jar, but Pydev 2.7 has the above bug with live-py_2.0.0.201209171018.jar.

Note: this bug originally described a different problem with earlier versions of live-py.

What I did

Edit a babel block in an org file (org-edit-special). This will open a second buffer with only the code in the block from where org-edit-special was invoked. In this new buffer enable live-py-mode.

What happened

the live buffer pops-up but it displays the following:

------------------------------------------------------------- |
FileNotFoundError: [Errno 2] No such file or directory: 'Src' |
------------------------------------------------------------- |

What I wanted to happen

I expected live-py-mode not to require an actual file on disk but just a buffer to do its magic.

My environment

• Emacs 26.3
• Ubuntu 18.04
• Python 3.6.8
• Org mode 9.1.9

There are a couple of scenarios where it might be useful to change the tracing from within the code.

1. If we add a command-line version of the code tracer, it could be used as a debugging tool. However, you'd probably only want to trace one or two methods instead of the whole file. We could use a decorator like PySnooper does to select which methods to trace. It might also be nice to be able to trace code without having to install one of the plugins. Tracing a couple of functions might also make sense if they are called within a large program. You could even call the command-line version with watch to update the trace whenever you save a file, so it's sort of like live coding without the IDE integration.
2. Within one of the plugins, you might want to tell it not to trace some of the variables. Long variables like lists or strings can make loop displays harder to read.

Here's an example:

import code_tracer       | 
                         | 
                         | 
@code_tracer.trace_code  | 
def foo(n):              | n = 3 
    s = 'x'              | s = 'x' 
    for i in range(n):   | i = 0    | i = 1     | i = 2 
        s += 'y'         | s = 'xy' | s = 'xyy' | s = 'xyyy' 
    return s             | return 'xyyy' 
                         | 
                         | 
def bar(n):              |
    s = 'a'              |
    for i in range(n):   |
        s += 'b'         |
                         | 
                         | 
print(foo(3))            |
print(bar(3))            |

Possible features (probably move most to separate issues):

• [x] Move Python files into a package, with a setup.py file.
• [x] Mark a method to be the only section that gets traced.
• [x] Replace first positional argument with --source: "file to read the traced module from, or - for stdin. Defaults to standard Python loading."
• [x] Replace second positional argument with --trace_module: "module to display trace for. Defaults to __main__"
• [x] Add --live option: "load main module as __live_coding__ instead of __main__."
• [x] Refactor top level code tracer to simplify it.
• [x] Fix alignment when @traced is used in the editor.
• [x] Add --traced option to select module or method
• [x] ~~Add --stdin option: "file to read stdin from, or - for normal stdin. Defaults to /dev/null."~~ moved to #238.
• [x] ~~Add --stdout option: "file to write stdout to (not tracing), or - for normal stdout. Defaults to /dev/null."~~ moved to #238.
• [x] ~~Add --stderr option: "file to write stderr to, or ! for normal stderr. Defaults to /dev/null."~~ moved to #238.
• [x] ~~Add --report option: "file to write tracing to, or - for stdout, or ! for stderr. Defaults to -."~~ moved to #238.
• [x] Replace --dump with --source_width option: "Width of source code - use 0 to hide or negative numbers to trim columns from the end, -1 to fit source code. Defaults to -1."
• [x] Add --source_indent option: "Number of spaces to indent source code. Negative to skip first columns of source code. Defaults to 0."
• [x] Add trace_width option: "number of columns to display, including source code. Use negative numbers to trim columns from the end, 0 for no limit." Defaults to display width? One less?
• [x] ~~Add --trace_offset option: "number of columns to skip at start of tracing display."~~ moved to #239.
• [x] ~~Add --hide option: "variable name to hide from display." Also allow hide parameter in decorator.~~ moved to #239.
• [x] ~~Add --start_line and --end_line options: "first/last line to trace in trace_module." Also allow start_line and end_line parameters in decorator.~~ moved to #239.
• [x] ~~Mark a section with a with block.~~ moved to #239.
• [x] ~~Add --depth option: "trace the methods that the marked method calls, within the same file, up to the given depth."~~ moved to #240.
• [x] --live and --traced=__live_coding__ are incompatible with Pyglet, because the __main__ module gets deleted?
• [x] publish the package on pypi

[NEW] - mock_pyglet.py - Class for monkey patching pyglet in traced code. Pyglet seems to have many entry points so it may be unrealistic to support everything. So far we patch Window and app.run which will service a simple hello world example.

If the value of scroll-margin is not 0, the live buffer won't align with source code buffer properly.

Wasn't sure whether to compensate for scroll-margin manually, so decided to set it to 0 locally for sake of simplicity.

What I did

1. Open CLion
2. Create main.py
3. Write some code, e.g. a = 1
4. Run it normally
5. Run it again by clicking "Start Live Coding"
6. Try to add more code, e.g., b = 2

What happened

In the split window, line 1 shows created for main.py. After updating the code, nothing changes.

What I wanted to happen

Show variable names their values like how this plugin works in PyCharm.

My environment

• CLion 2020.3.3
• Windows 10 Pro
• Python 3.7.9

Other feedbacks

Change github issue template to use ## for section names, # is usually used as titles.

Hello and thanks for the awesome plugin. I am here to report that the live-py-mode does not work correctly with Doom Emacs. The cursor decides to jump to the live window even if I am in the insert mode (evil).

What I did

Any Python code would reproduce this. As an example:

import os

print(os.path.join('foo', 'bar')

What happened

The cursor jumps to the live-py-trace buffer while typing if you delay the typing for more than one second.

What I wanted to happen

Normal behavior as for Spacemacs or Vanilla Emacs.

My environment

Describe the versions of everything you were using:

• Editor Doom Emacs
• Operating system Linux Manjaro
• Python 3.7

Other feedback

I love this mode and being able to utilize it using Doom Emacs would be highly appreciated.

What I did

Describe the steps you took, probably including your Python code, like this:

• Created a Python script which had more lines than could fit in the window showing its buffer, let's say it could show 10 lines).
• Activated Live Py Mode using M-x live-py-mode
• In the code window:
  • Moved point (next-line) to the last line of the buffer, scrolling all the way down.
  • Moved point (previous-line) to the first visible line in the window.
  • Moved point up one more line (previous-line).
  • Finally, moved point down one line.

print(21)

print(42)

print(21)

print(42)

print(21)

print(42)

print(21)

print(42)

print(21)

print(42)

print(21)

print(42)

What happened

Describe what you saw, probably including the live coding display, like this:

• After scrolling to the last line in the code window (! indicates position of point):

                                         |                                         
print(42)                                |print('42')                              
                                         |                                         
print(21)                                |print('21')                              
                                         |                                         
print(42)                                |print('42')                              
                                         |                                         
print(21)                                |print('21')                              
                                         |                                         
print(42)                                |print('42')                              
                                         |                                         
print(21)                                |print('21')                              
                                         |                                         
print(42)                                |print('42')                              
                                         |                                         
print(21)                                |print('21')                              
                                         |                                         
print(42)                                |print('42')                              
                                         |                                         
!                                        |!                                        
-UU-:----F1  blub.py        Bot (25,0)   |-UUU:**--F1  *live-py-trace_blub.py_17080
End of buffer

• Right after moving point to the top line in the code window (! indicates position of point):

!                                        |!                                         
print(42)                                |print('42')                              
                                         |                                         
print(21)                                |print('21')                              
                                         |                                         
print(42)                                |print('42')                              
                                         |                                         
print(21)                                |print('21')                              
                                         |                                         
print(42)                                |print('42')                              
                                         |                                         
print(21)                                |print('21')                              
                                         |                                         
print(42)                                |print('42')                              
                                         |                                         
print(21)                                |print('21')                              
                                         |                                         
print(42)                                |print('42')                              
                                         |                                         
                                         |                                         
-UU-:----F1  blub.py        Bot (6,0)    |-UUU:**--F1  *live-py-trace_blub.py_17080

• Right after moving point up one more line (! indicates position of point, note: point no longer visible in output window):

!print(21)                               |                                         
                                         |print('42')                              
print(42)                                |                                         
                                         |print('21')                              
print(21)                                |                                         
                                         |print('42')                              
print(42)                                |                                         
                                         |print('21')                              
print(21)                                |                                         
                                         |print('42')                              
print(42)                                |                                         
                                         |print('21')                              
print(21)                                |                                         
                                         |print('42')                              
print(42)                                |                                         
                                         |print('21')                              
print(21)                                |                                         
                                         |print('42')                              
print(42)                                |                                         
                                         |                                         
-UU-:----F1  blub.py        Bot (5,0)    |-UUU:**--F1  *live-py-trace_blub.py_17080

What I wanted to happen

Describe what you wanted, probably including changes to the live coding display, like this:

• I would like the code and output windows to stay synchronized when scrolling up, and point in the output window to remain visible at all times, like this:

!print(21)                               |!print('21')                              
                                         |                                         
print(42)                                |print('42')                              
                                         |                                         
print(21)                                |print('21')                              
                                         |                                         
print(42)                                |print('42')                              
                                         |                                         
print(21)                                |print('21')                              
                                         |                                         
print(42)                                |print('42')                              
                                         |                                         
print(21)                                |print('21')                              
                                         |                                         
print(42)                                |print('42')                              
                                         |                                         
print(21)                                |print('21')                              
                                         |                                         
print(42)                                |print('42')                              
                                         |                                         
-UU-:----F1  blub.py        Bot (5,0)    |-UUU:**--F1  *live-py-trace_blub.py_17080

My environment

Describe the versions of everything you were using:

• Editor (PyCharm, Eclipse, or Emacs)

$ emacs --version | head -n 1
GNU Emacs 25.3.1

• C-h P live-py-mode RET

live-py-mode is an installed package.

     Status: Installed in ‘live-py-mode-20180129.2352/’ (unsigned). Delete
    Version: 20180129.2352
[...]

• Operating system

• Void Linux (x86_64, glibc)

• Python

import sys                               |                                         
ver = sys.version                        |ver = '3.6.4 (default, Dec 19 2017, 18:0$

What I did

Started the live canvas in PyCharm.

What happened

It displayed an outdated canvas, what the code used to draw a few minutes before. Sometimes, the current file is out of date, and sometimes the driver file is out of date.

Sometimes, it also scrolls to a different place in the source file. The top, I think.

What I wanted to happen

It should run the current code.

Workaround: edit the current file, or press Ctrl+S.

My environment

Describe the versions of everything you were using:

• PyCharm 2022.3
• Live Coding 4.9.1
• Ubuntu 20.04
• Python 3.9

What I did

Describe the steps you took, probably including your Python code, like this:

- I installed the plugin in PHPStorm;
- I opened a Python file and the error occured;

What happened

Describe what you saw, probably including the live coding display, like this:

- PHPStorm displayed an error and because the plugin is not a product of Jetbrains, I was unable to submit the report. Here is the contents of 

What I wanted to happen

Describe what you wanted, probably including changes to the live coding display, like this:

**What do you get when you multiply six by nine?** That would be 54

Please see the attached files for errors and stacktrace (induced.txt and stacktrace.txt)

My environment

Describe the versions of everything you were using:

• Editor: JetBrains PHPStorm Version 2022.2.3 Build #PS-222.4345.15, built on October 5, 2022

• Live Coding plugin: Live Coding in Python 2.25.1

• Operating system: Edition: Windows 10 Pro Version: 22H2 Installed on: 2022-‎09-‎22 ‎Thu OS build: 19045.2311 Experience: Windows Feature Experience Pack 120.2212.4190.0

• Python

Other feedback

While you're here, we'd love to know how you learned about the project, what you use it for, or anything else you'd like to tell us.

I just wanted something similar to Python Intellisense to assist with Python development.

induced.txt stacktrace.txt.txt

Writing visual unit tests to compare graphics code is powerful, but often brittle. Things like antialiasing can make the comparison unreliable.

Adapt the smeared comparison from the four-letter blocks project, so that comparison will ignore minor changes in text or antialiasing, but will detect the wrong text, the wrong font, or other failures.

• [ ] port the numpy image and smearing code
• [ ] probably fail if numpy isn't installed, because the smear calculation will be very slow
• [ ] increase the dtype size as the smear radius gets bigger?

Some ideas for how to use the file system in pyodide:

• add a list of data files to load in the tutorial header
• carry the same script through several editors in the same tutorial, with a hint about where to scroll to
• edit module and test module, but run the test against the edited module

Make Image.show(), or ImageShow.show() display the image on the live canvas. It looks like you can register a new display method.

Also look for some tutorial ideas.

• realpython.com tutorial

What I did

Tried to compare two images without alpha channels.

from PIL import Image
from space_tracer import LivePillowImage, LiveImageDiffer

a = LivePillowImage(Image.new('RGB', (100, 100)))
b = LivePillowImage(Image.new('RGB', (100, 100)))
differ = LiveImageDiffer()
differ.compare(a, b)

What happened

It complained about the missing alpha channel.

/home/don/.local/share/virtualenvs/svg-turtle-7kVEgXjr/bin/python /home/don/.config/JetBrains/PyCharm2021.3/scratches/scratch.py
Traceback (most recent call last):
  File "/home/don/.config/JetBrains/PyCharm2021.3/scratches/scratch.py", line 7, in <module>
    differ.compare(a, b)
  File "/home/don/.local/share/virtualenvs/svg-turtle-7kVEgXjr/lib/python3.9/site-packages/space_tracer/live_image.py", line 262, in compare
    diff_fill = self.compare_pixel(fill1, fill2, is_missing)
  File "/home/don/.local/share/virtualenvs/svg-turtle-7kVEgXjr/lib/python3.9/site-packages/space_tracer/live_image.py", line 334, in compare_pixel
    ar, ag, ab, aa = actual_pixel
ValueError: not enough values to unpack (expected 4, got 3)

What I wanted to happen

Make the alpha channel default to 255, the same as changing the code sample above to use mode 'RGBA'.

My environment

Describe the versions of everything you were using:

• space_tracer 4.7.0
• Ubuntu 20.04
• Python 3.9.9

Analysis

Add a helper function to pad pixels to four channels, and call it in compare_pixel(). Think about grayscale images, as well.