Python 3.14.0 Is Now Available

Posted3 months agoActive3 months ago

runningmike

24 points

11 comments

blog.python.orgTechstory

supportivepositive

Debate

20/100

PythonProgramming LanguagesSoftware Releases

Key topics

Python

Programming Languages

Software Releases

The Python community is notified of the release of Python 3.14.0, with the discussion focusing on the implications and features of the new version.

Snapshot generated from the HN discussion

Discussion Activity

Light discussion

First comment

N/A

Peak period

0-2h

Avg / period

2.2

Comment distribution11 data points

Loading chart...

Based on 11 loaded comments

Key moments

01Story posted
Oct 7, 2025 at 3:11 PM EDT
3 months ago
Step 01
02First comment
Oct 7, 2025 at 3:11 PM EDT
0s after posting
Step 02
03Peak activity
4 comments in 0-2h
Hottest window of the conversation
Step 03
04Latest activity
Oct 8, 2025 at 3:52 PM EDT
3 months ago
Step 04

Generating AI Summary...

Analyzing up to 500 comments to identify key contributors and discussion patterns

Discussion (11 comments)

Showing 11 comments

runningmikeAuthor

3 months ago

1 reply

Python 3.14 has great new features like: - Free-threaded Python is now officially supported

- Template string literals (t-strings) for custom string processing

- Syntax highlighting in PyREPL and more!

Great work , congratulations with this release!

dlojudice

3 months ago

1 reply

+ experimental JIT compiler

this could be the beginning of something very promising

Neywiny

3 months ago

1 reply

Problem is, it's too late. Most performant code I've seen and written isn't using numba, it's using numpy to vectorize. And sadly, there's a lot of wasted iteration when doing that just to be faster than scaler. My point being, that code won't speed up at all without a rewrite.

tkcranny

3 months ago

1 reply

Introducing JIT features has a lot of opportunities beyond numerical numpy/numba vectorisation. There’s endless amounts of hot loops, data shuffling, garbage collection, and monomorphisation that could be done in real world python that would benefit a lot, much like V8 has done for JS.

Neywiny

3 months ago

1 reply

I guess my point is that truly performant python code, at least for number crunching, uses vectorized numpy functions instead of loops, and the overhead on type checking for those is fairly minimal. I have a PR in on a compute heavy python program that I tried using numba to jit. Timing was within margins on using numpy and numba (even though the numba code could exit the loop early, which was why I was trying it) except with numba I'd be adding a dependency and it's more work to maintain the algorithms myself instead of relying on numpy.

I think of the JS code I've seen, it's mostly written in JS. So making JS faster makes JS faster. With python, the fast code is written outside python. It's too late by like 20 years. The world won't rewrite itself into native python modules

zahlman

3 months ago

> and the overhead on type checking for those is fairly minimal

Well, yeah; the underlying C code assumes the type that was described to it by the wrapper (via, generally, the .dtype of an array), so it's O(1).

But I do wonder what the experience of Numpy has been like for the PyPy users.

ivanche

3 months ago

3 replies

Shouldn't this version be called Pi-thon?

I'll walk myself out.

tkcranny

3 months ago