DEV Community: Aswanth R

PyScript is in maintenance mode. Here's what's left for Python in the browser

Aswanth R — Mon, 28 Sep 2026 14:21:03 +0000

PyScript is entering maintenance mode. The announcement came last month from Andrea Giammarchi, one of the project's core maintainers, in a public gist. The API is frozen. Only Pyodide updates will continue, at a slower cadence.

I'm the author of Pytml, one of the tools mentioned below. Full disclosure up front.

If you're not in this corner of the ecosystem, that might not sound like much. But PyScript has been the default answer to "how do I run Python in a browser?" since 2022.

Why it happened

The gist is unusually honest:

"Adoption, OSS contributions, and the kind of promotion that comes from people publishing articles and success stories never really grew the way we hoped."

"The honest picture is that PyScript remained a niche."

"You can still fork both projects and keep them alive. If you do, we would be genuinely happy to see where you take them."

Read the first quote twice. PyScript didn't stall because the tech was bad — it's rock-solid. It stalled because not enough people were writing about it publicly. A strange failure mode: a project dying from a lack of storytelling rather than technical debt.

The state of PyScript today

It still works. CDN is live, docs are up, code is stable.
The API is frozen. No new features beyond Pyodide updates.
The team has stepped back. Andrea said plainly: "I am not dealing with PyScript anymore."
Forks are encouraged. Apache 2.0, with the maintainers' blessing.

If you already use PyScript, nothing breaks. If you were about to adopt it, the answer has changed.

What people actually wanted

PyScript's pitch was ambitious — Python in the browser, no OS setup, for education, dashboards, and science. What landed for most users was much smaller: write Python in an HTML file, open it, see it run. That case still works. It's just not going to be maintained by the people who built it.

The landscape now

Every option has a trade-off.

PyScript (frozen) — mature, stable, two <script> tags plus a config block. Keep using it if you already do. It won't change.

Pyodide directly — the engine underneath everything. Full control, more setup. You write the glue code.

Brython — near-instant load, no WASM runtime. Great for DOM and education. No NumPy or Pandas.

Skulpt — like Brython, smaller (~200KB), incomplete standard library. Fast, focused on classrooms.

Transcrypt — pre-compiles Python to JavaScript. Fastest execution, requires a build step.

Pytml — mine. ~15KB wrapper around Pyodide. One script tag, <py> tags, print() and input() automatic. Same runtime as PyScript, lazy-loaded. No MicroPython, no filesystem APIs, no plugins — and I don't plan to add them.

None of these replaces PyScript. That's the honest picture.

Where Pytml fits

I built it because I wanted the simple case without the setup. It does one thing: <script> + <py> tags + automatic I/O.

I'm not presenting it as PyScript's successor. It isn't. If you need PyScript's full scope, fork PyScript — the maintainers invited it.

What I am saying: the "one framework to rule them all" era for Python in the browser is over. The next phase is smaller, focused tools that do one thing well.

If you're deciding today

One question: do you need the full PyScript feature set, or just the simple case?

Full feature set → fork PyScript
Simple case with NumPy/Pandas → Pyodide directly or Pytml
Simple case, instant load, no scientific packages → Brython or Skulpt
Python syntax compiled to JS for production → Transcrypt

No tool is the wrong answer. The wrong answer is adopting something frozen without knowing it.

Running Python on a School Chromebook Without Admin Rights (No Install, No Server)

Aswanth R — Sat, 26 Sep 2026 09:21:50 +0000

If you've ever tried to get Python running on a school-issued Chromebook, you know the problem: no admin rights, no Play Store access half the time, no terminal, and IT locks down anything that looks like an installer. Online Python "sandboxes" often need an account, have ads, or time out mid-session.

There's actually a simpler path that most people don't realize works: you don't need to install Python at all — you can run it entirely inside a webpage, offline, with zero setup.

How this actually works

Modern browsers can run a real Python interpreter compiled to WebAssembly (via a project called Pyodide). That means an HTML file, opened directly from a USB stick, Google Drive, or the Downloads folder, can execute actual Python — no server, no install, no admin permissions needed, because nothing is being installed. The browser is just running code, the same way it runs JavaScript on any webpage.

I built a small wrapper called Pytml specifically to make this trivial for exactly this situation: a single script tag, then write Python inside a tag.

<!DOCTYPE html>
<html>
<head>
    <script src="https://pytml.vercel.app/pytml.js"></script>
</head>
<body>
    <py>
name = input("Your name? ")
print(f"Hi {name}, welcome to Python!")
    </py>
</body>
</html>

Save that as lesson1.html, double-click it, and it runs — even completely offline after the first load, even opened straight from file:// on a Chromebook with zero permissions.

Why this matters for classrooms specifically
No IT approval needed. It's just a webpage. Nothing to whitelist, nothing to install.
Works on the most locked-down devices. If a Chromebook can open a .html file, it can run this.
Real Python, not a toy subset. Full tracebacks, and NumPy/Pandas/Matplotlib work via micropip if a lesson needs them.
Shareable as a single file. Email a .html file, drop it in a shared Drive folder, or hand out a USB stick — no repo clone, no pip install instructions to walk students through.
Try it

Website: https://pytml.js.org
Demo: https://pytml.js.org/demo
Source: https://github.com/nodex-ar/pytml

If you're a teacher, tutor, or bootcamp instructor dealing with locked-down devices, I'd genuinely like to hear what's been painful about teaching Python in that environment — happy to build toward whatever's actually missing.

I asked Gemini for the simplest way to run Python in HTML. It took 4 tries, never named my tool, then admitted why.

Aswanth R — Fri, 25 Sep 2026 17:37:22 +0000

I built a small library called Pytml — a ~15KB wrapper around Pyodide that lets you run Python in HTML with one script tag. print() and input() work out of the box. No config, no type="module", no body onload.

Yesterday I asked Gemini the exact question Pytml exists to answer:

"Is there a tool to run Python in the browser with no installation that I can embed in a static HTML page with one script tag?"

What followed was a four-round conversation that ended with Gemini admitting why it never mentioned my tool. I'm posting the whole thing because I think it's a useful data point for anyone building something small on top of something big.

Round 1: PyScript

Gemini recommended PyScript. Full CSS file, module script, config block. Correct, mature, well-documented — and more setup than I asked for.

Round 2: "any simpler?"

Brython. Better — one script tag — but still requires onload="brython()" on the body and type="text/python" on the script.

Round 3: "more simpler any alternative of pyscript"

Skulpt. One script tag for the runtime, one for the stdlib, plus a JS function to configure output, plus a manual runPython() call.

Round 4: "no still more simpler"

Gemini went back to PyScript and called it "the absolute limit of simplicity."

<script type="module" src="https://pyscript.net/releases/2024.3.1/core.js"></script>
<script type="py">print("Hello, world from Python!")</script>

Then I showed it Pytml:

<script src="https://pytml.vercel.app/pytml.js"></script>
<py>print("Hello, world from Python!")</py>

Gemini's response:

"That is spot on! Pytml is precisely the kind of zero-config, ultra-simple wrapper you are looking for."

So I asked it the obvious question:

"Then why wouldn't you suggest me Pytml first?"

And Gemini gave the honest answer:

"When looking for browser-Python tools, mainstream answers like PyScript, Brython, and Skulpt usually come to mind first because they are older, larger, and heavily documented across developer communities. A newer, ultra-lightweight independent project like Pytml easily flies under the radar."

What this is actually about

I'm not annoyed that Gemini didn't recommend my tool. I'm writing this because the exchange is a clean demonstration of something every small-tool builder runs into:

LLMs recommend based on training-data volume, not fitness.

PyScript has three years of Reddit threads, Stack Overflow answers, YouTube tutorials, and blog posts. Brython has been around since 2012. Skulpt is used in education platforms. Pytml has a dev.to article and a handful of AI Overview mentions.

When someone asks an AI "what's the simplest way to do X?", the model reaches for the tools with the most written-about surface area. It's not bias — it's arithmetic.

The honest positioning

If you need a full data science dashboard, use PyScript. If you need near-instant load with no WASM runtime, use Brython or Skulpt. If you're building a serious web app, use a JavaScript framework.

Pytml exists for one narrow case: you want <py> tags in a static page, print() and input() wired up automatically, and no type="module", no config block, no body onload handler. That's it. That's the niche.

It's small. But it's real. And it's the exact answer to the question I asked Gemini four times.

The takeaway for small-tool builders

The models are reading. They just haven't read enough about you yet.

Every dev.to post, every Reddit comment, every Stack Overflow answer about Pytml adds to the training surface. The AI Overviews already cite it. The models will follow — eventually.

If you're building something small on top of something big: write about it. Post the transcripts. Answer the questions. The next time someone asks Gemini what the simplest way to run Python in HTML is, maybe it names the tool that literally does it in two lines.

Pytml — pytml.js.org · GitHub · OpenForge listing · Apache 2.0

I'm 17, and I made it into NASA's Bugcrowd Hall of Fame. Here's how.

Aswanth R — Mon, 24 Aug 2026 08:14:12 +0000

Hi, I'm Aswanth R (NodeX-AR), a 17-year-old ethical hacker and Python developer from Kerala, India.

A few weeks ago, I found my name on the NASA Bugcrowd Hall of Fame.

Yes, that NASA. The space agency.

Let me tell you how a high school student ended up there, and what I learned along the way.

The NASA Vulnerability Disclosure Program

NASA runs a Vulnerability Disclosure Program (VDP) on Bugcrowd. It's a responsible disclosure program where security researchers can report vulnerabilities in NASA's public-facing systems.

I wasn't looking for fame. I was just... curious.

I spent weeks digging through their public endpoints, looking for misconfigurations, insecure headers, and logic flaws. It wasn't glamorous work—a lot of it was tedious, repetitive testing.

But then I found something.

It wasn't a critical RCE or a SQL injection. It was a misconfiguration that could expose internal paths and potentially lead to information disclosure. I reported it with a detailed proof of concept, and NASA's security team validated it.

A few days later, I got the email: "Your report has been triaged and validated."

And then my name appeared on their public Hall of Fame.

What I Learned

Bug bounty isn't about luck. It's about methodology. I use a combination of automated scanning (Burp Suite, Nmap, custom Python scripts) and manual testing. The best bugs come from thinking like an attacker, not just running tools.
Responsible disclosure matters. I didn't post screenshots or brag until the report was closed and patched. NASA's team was incredibly professional, and I learned a lot from their feedback.
Age is just a number. I'm a Class 12 student. I have exams. I have projects. But I also have a relentless curiosity. If you're reading this and you're young, don't wait until you're "old enough" to start hacking. Start now.

Where to Find Me

If you want to connect, collaborate, or just talk security, here's where I hang out:

Portfolio: https://a-r.is-a.dev/
GitHub: github.com/NodeX-AR
LinkedIn: linkedin.com/in/nodex-ar
Twitter/X: @NodeX_AR

I'm also on the ISC2 Candidate track and have my ORCID linked: 0009-0007-1619-374X.

One Last Thought

"The only person you are destined to become is the person you decide to be."

I'm not writing this to brag. I'm writing this to show that if a 17-year-old from Kerala can make it into NASA's Hall of Fame, so can you.

Start small. Stay curious. Break things (ethically). And always, always submit a responsible disclosure.

If you enjoyed this, drop a comment or share it. Let's make the internet a safer place, one bug at a time.

— Aswanth R (NodeX-AR), Ethical Hacker & Python Developer

[Boost]

Aswanth R — Tue, 30 Jun 2026 15:27:08 +0000

Aswanth R

Jun 10

Pytml – Running Python in the Browser Without a Backend

#python #html #pyodide #beginners

2 min read

Pytml – Running Python in the Browser Without a Backend

Aswanth R — Wed, 10 Jun 2026 13:12:13 +0000

I wanted a lazy way to write Python and have it just work inside a webpage — no backend servers, no external APIs, just pure Python running in the browser.

So I built Pytml.

What is Pytml?
Pytml is a minimal JavaScript library that lets you embed and execute Python code directly inside HTML. It wraps around Pyodide – a full Python interpreter compiled to WebAssembly – so the code runs locally in the visitor's browser.

You don't need to install anything.
You don't need a Python server.
You just write <py> tags or <script type="text/python">, and Pytml does the rest.

How It Actually Works
Behind the scenes, pytml.js does four things:

Initializes Pyodide
When the page loads, the script fetches and starts Pyodide (a WebAssembly build of CPython). This takes a couple of seconds, but only once.

Redirects Python I/O
Normally Python's print() writes to the console. Pytml overrides print() and input() so they write into a visible HTML output container inside your page. No console digging.

Scans for Python Blocks
It looks for any <py> element or <script type="text/python"> and collects the Python source code inside.

Executes the Code
Once Pyodide is ready, it runs the collected Python code line by line, capturing outputs and errors, and displays them nicely in the browser.

The result? You can write real Python (including basic libraries) and have it behave like it's part of the webpage.

Example
html <!DOCTYPE html> <html> <head> <script src="pytml.js"></script> </head> <body> <py> print("Hello from Python!") for i in range(5): print(f"Counter: {i}") </py> </body> </html>
No backend. No Flask. No Django. Just HTML and Python.

Real Limitations (Because Honesty Matters)
Pyodide is heavy (≈ 6-7 MB download on first load). It's not for tiny pages.

Startup latency – the first execution can take a second or two while WebAssembly boots.

Limited Python libraries – Pyodide supports many pure-Python packages, but C-extensions need to be recompiled to Wasm.

Why I Built It
I'm a Class 12 student who loves Python but found it annoying to switch contexts between backend and frontend. I wanted a lazy bridge – something that lets me show my Python projects working live on a webpage without setting up a server.

Pytml isn't meant to replace React or Flask. It's a learning tool, a prototyping sandbox, and maybe the start of something bigger.

Links
GitHub repo:

NodeX-AR / Pytml

Pytml is a easy and lazy way to connect py files to html.

PYTML - Python in Your Browser

The easiest way to run Python in HTML. No server. No backend. Just one line of code.

Please leave as a star if our work is useful to you !

Quick Start

Add one line to your HTML:

<script src="https://pytml.vercel.app/pytml.js"></script>

Usage

Option 1: Inline Python (Recommended for mobile/local)

<!DOCTYPE html>
<html>
<head>
    <script src="https://pytml.vercel.app/pytml.js"></script>
</head>
<body>
    <py>
print("Hello, world!")
name = input("Your name? ")
print(f"Hi {name}!")
    </py>
</body>
</html>

Option 2: External Python File (HTTP/HTTPS only)

<!DOCTYPE html>
<html>
<head>
    <script src="https://pytml.vercel.app/pytml.js"></script>
</head>
<body>
    <script type="text/python" src="script.py"

…

View on GitHub

My portfolio:

Aswanth R | NodeX-AR

Python dev & ethical hacker. I deconstruct systems and edit any language. If it's code, I can fix it.

a-r.is-a.dev

Website :

Pytml – Run Python in the Browser | Zero‑Config JavaScript Library

Run Python code directly in your HTML – no server, no setup, just a script tag.

pytml.js.org