Skip to content

Commit ddbda26

Browse files
fix rest of the links
1 parent e9e0f46 commit ddbda26

2 files changed

Lines changed: 2 additions & 2 deletions

File tree

_posts/2025-11-08-faster-jit-plan.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ During the Python Core Dev Sprint in Cambridge hosted by ARM, we planned to make
99

1010
You might wonder: 5% seems awfully conservative. However, note that this figure is the *geometric mean*. The number can range from slower to significantly faster. All numbers are [pyperformance](https://github.com/python/pyperformance) figures.
1111

12-
In my [previous blog post](./2025-07-05-jit-reflections.md), I talked about the Python 3.13 and 3.14 JIT's state. We're planning to change that for 3.15 and 3.16.
12+
In my [previous blog post]({{ site.baseurl }}/posts/jit-reflections.md), I talked about the Python 3.13 and 3.14 JIT's state. We're planning to change that for 3.15 and 3.16.
1313

1414
## The Plan for 3.15
1515
This is a paraphrase of what Savannah laid out [here](https://github.com/python/cpython/issues/139038). The difference is that I'm listing things in chronological order of what I expect will be merged into CPython.

_posts/2025-12-24-no-longer-sorry.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ title: Python 3.15's interpreter for Windows x86-64 should hopefully be 15% fast
55

66
24 December 2025
77

8-
Some time ago I posted an [apology piece]({{ site.baseurl }}/apology-tail-call.md)
8+
Some time ago I posted an [apology piece]({{ site.baseurl }}/posts/apology-tail-call.md)
99
for Python's tail calling results. I apologized for communicating performance
1010
results without noticing a compiler bug had occured.
1111

0 commit comments

Comments
 (0)