summaryrefslogtreecommitdiffstats
path: root/2025/talks
diff options
context:
space:
mode:
authorSacha Chua <sacha@sachachua.com>2025-08-22 10:54:31 -0400
committerSacha Chua <sacha@sachachua.com>2025-08-22 10:54:31 -0400
commitd9f7d511efccfc90eabfe8ea08784c40d5d5ebc8 (patch)
tree509dbaf4ffa3aeb255ee9c0a5e6b36249f51ec74 /2025/talks
parentc62b9d0d354dd632d5f9e0ec846a09313fd14e93 (diff)
downloademacsconf-wiki-d9f7d511efccfc90eabfe8ea08784c40d5d5ebc8.tar.xz
emacsconf-wiki-d9f7d511efccfc90eabfe8ea08784c40d5d5ebc8.zip
add swanky
Diffstat (limited to '')
-rw-r--r--2025/talks/swanky.md49
1 files changed, 49 insertions, 0 deletions
diff --git a/2025/talks/swanky.md b/2025/talks/swanky.md
new file mode 100644
index 00000000..83a8bb7f
--- /dev/null
+++ b/2025/talks/swanky.md
@@ -0,0 +1,49 @@
+[[!meta title="Swanky Python: Interactive development for Python"]]
+[[!meta copyright="Copyright &copy; 2025 Scott Zimmermann"]]
+[[!inline pages="internal(2025/info/swanky-nav)" raw="yes"]]
+
+<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing -->
+<!-- You can manually edit this file to update the abstract, add links, etc. --->
+
+
+# Swanky Python: Interactive development for Python
+Scott Zimmermann (he/him) - sczi@disroot.org
+
+[[!inline pages="internal(2025/info/swanky-before)" raw="yes"]]
+
+Project repository: <https://codeberg.org/sczi/swanky-python/>
+
+I'm working on a development environment for
+Python based on Emacs' SLIME mode for Common Lisp.
+In this talk I'll demonstrate some of its
+features, like an object inspector, interactive
+backtrace buffer, thread and async task viewer,
+and function tracer. I'll also discuss its
+implementation and limitations, along with future
+directions for the project.
+
+This project aims to bring a Lisp and Smalltalk
+inspired style of development to Python. You get a
+faster feedback loop by developing inside a
+running python process without needing to restart
+your program and lose state on changes, allowing
+you to immediately inspect the results of code you
+write. We can also provide more advanced tooling
+based on runtime introspection, as we have more
+information available at runtime than is available
+to traditional tools based on static analysis of
+source code, mainly we have the actual values of
+variables rather than just their types.
+
+About the speaker:
+
+Python is eating the world. Emacs is eating my computing environment. I'm
+attempting to get them working together.
+
+
+
+[[!inline pages="internal(2025/info/swanky-after)" raw="yes"]]
+
+[[!inline pages="internal(2025/info/swanky-nav)" raw="yes"]]
+
+