Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Livecoding Mode for Python

Offen
#61 4 Kommentare 0 Reaktionen 1 zugewiesene Person Auf GitHub ansehen

@catilac arbeitet bereits daran.

Seit 24.1.2026.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Beschreibung

Leverage bevy_ecs to watch the currently running sketch for changes and hotswap on successfully compiling edits

Edit: I'm currently working on this, but there are some architectural questions I have.

Current Approach

I've created a new bevy Asset called Sketch and spawn that object at Startup.
When I make a change to sketch.py bevy will notice. yay

The question now is how does the actual reloading mechanism work for Python? And there is a larger question of how does this mechanism work for other language frontends (Processing4/java, lua, ocaml, scheme, ruby, etc...)

For Python (w/ pyo3)

  1. Make a change to sketch.py
  2. Bevy will observe and [emit an event]
  3. processing_pyo3 crate will check if a reload is necessary
  4. Using something like importlib.reload(), pyo3 can reload the module, and skip creating a new graphics context if it doesn't have to, and grab the new draw and setup functions.
+--------+        +------+
| Python |------->| Bevy |
+--------+        +------+
   ^                |
   |                |
   +-- onChange ----+

What about other language front-ends?

I suppose some custom plugin loading could work. The Sketch Asset could be something that Python introduces, so that would allow for us to only use any of that design only for our pyo3 implementation

The other front-ends would have to build their own systems, and we could expose hot-reloading related FFI methods?

I think at the moment, I really like the idea of just having a Python related Livecoding bevy plugin. I'm still learning about bevy's ECS system, but is it possible for us to represent our "scene graph" as an intermediary that can easily map to the existing entities in bevy?

ie:

def draw():
    background(220)

    fill(255, 0, 100)
    stroke(0)
    stroke_weight(2)
    rect(100, 100, 200, 150)

when I change stroke_weight, could bevy know to update, or refresh that particular entity?
or is it easier to just drop all the entities and re-run the sketch? I might be over thinking it.

For now I'm going to work towards getting python to hotreload.

Vorherrschende Sprache
Rust
Sterne
69
Forks
14
Ø Merge
15 T. 22 Std.
Gemergte PRs (30 T.)
3

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus processing/libprocessing

Alle Issues in processing/libprocessing

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.