/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

Will Wall Street require Python?

SEC considers regulations expressed in popular programming languages  —  17 I like it!  —  Failure is difficult.  Sometimes success is even more so.  —  What if, for example, Python not only:  — becomes popular for its role …

claird's blog Cameron Laird

Context & Ripple Effects

The claim here is explicitly unconfirmed: per the reporting around this post, the SEC is rumored to be considering drafting regulations expressed in popular programming languages such as Python. Nothing in the record at this point confirms the agency has committed to anything — but the idea lands on real momentum, including developer-side accounts of Python displacing older web scripting choices, such as joestump.net's account of why he switched from PHP to Python.

What makes the rumor plausible enough to track rather than dismiss is the SEC's own enforcement history: the agency has repeatedly shown willingness to pursue technically novel conduct, from Operation Spamalot against spam-promoted stocks in 2007 to emergency halts of hacking-driven fraud schemes. A regulator comfortable with technical investigations eyeing machine-readable rule text is a natural next step — and it would pull Wall Street compliance into direct contact with the open-source toolchain.

First-order effects

  • If the SEC actually drafts rules in an executable language, bank compliance departments would need working programmers on staff or contract — legal interpretation would become code review, and every rule amendment would ship like a software release.

Second-order effects

  • Language selection would instantly become a standards fight: whichever language the SEC blessed would gain regulatory lock-in across financial services, forcing law firms and compliance-software vendors to build translation and validation tooling around it.

Third-order effects

  • A confirmed move would establish 'regulation as code' as precedent — agencies writing deterministic, testable rules instead of prose — shifting the boundary between lawyers and engineers inside both regulators and regulated firms, with open-source communities becoming de facto participants in federal rulemaking.

The trend: Regulation is drifting from prose toward executable, machine-checkable form, and Python's growing developer adoption positions it as the leading candidate for that role.