Tag

Python

6 stories

Python's JIT shipped in 3.13, and its own authors just withdrew the PEP that would keep it (lwn.net)

The JIT, merged in 2024 without a standards-track PEP, was paused in June 2026 until one was accepted. Its maintainers drafted PEP 836, but the council wanted concrete support, performance and security plans, and objected to a compatibility review not due until August 2028. On October 19 the authors gave up.

Readers split between mourning and shrugging, and one pointed at a pattern.

Not just a headline — the discussion unpacked

The top HN threads: facts from the discussions, both sides, insider voices. Email, Telegram, or RSS.

UUIDv7 only promises uniqueness, and Python's version can run ahead of your clock (alexsci.com)

Alex Scott's post argues the three properties people credit to UUIDv7, monotonic order, a trustworthy creation time and unguessability, are not guaranteed by RFC 9562. Even Postgres warns that an extracted timestamp may differ from the creation time.

Commenters said that misses the real reason to use it: keeping new rows together in the index.

🚀Tech ★ 114 · 💬 99 · 4 days ago · #data#programming#web#Postgres#Python#RFC 9562+1

Ruff 0.16 turns 413 lint rules on by default (astral.sh)

Ruff is a Rust-based Python linter and formatter. The release folds many broadly useful checks into the default configuration, making a fresh run capable of finding a much wider class of code-quality problems.

HN’s likely concern is not whether more checks are valuable. It is how a project absorbs them: defaults are convenient for greenfield code, but established repositories need an intentional migration boundary.

At one bank, the Python source code lives in the database, not on disk (calpaterson.com)

Investment banks run secret forks of the entire Python ecosystem. In Paterson's account, one bank's system reads and writes Python dataclasses straight into a single global object database, called Barbara, shared by the whole firm.

The platform's own source code is stored in that same database, not in files. A thread of ex-bankers traces the idea back to Goldman's SecDB and Slang in the 1990s, and one calls the result "an alternate IT reality" you can't even google your way out of.

A Rust clone of pylint, byte-for-byte identical, built almost entirely by an AI agent (pypi.org)

The pitch reads like a benchmark dream: same warnings as pylint, same bugs reproduced on purpose, and black's 26.7-hour lint run finishing in 41 seconds. It was generated by Fable, an agentic coding system, with a human mostly steering.

The thread split fast. One side called it malware-SEO with an LLM-written README and asked if the project is even legit. The other side shrugged: if it passes pylint's own tests, who cares who typed it?

🚀Tech ★ 84 · 💬 110 · Jun 20 · #AI#dev tools#programming#Claude#prylint#pylint+3