# Python 3.14.0 beta 1 is near!

**URL:** <https://discuss.python.org/t/python-3-14-0-beta-1-is-near/90921>\
**Category:** Committers\
**Tags:** release\
**Created:** [May 6, 2025, 8:54am UTC](https://discuss.python.org/t/python-3-14-0-beta-1-is-near/90921 "2025-05-06T08:54:40Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![hugovk](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/hugovk/32/14505_2.png) [@hugovk](https://discuss.python.org/u/hugovk)\
**Post date:** [May 6, 2025, 8:54am UTC](https://discuss.python.org/t/python-3-14-0-beta-1-is-near/90921/1 "2025-05-06T08:54:40Z")

</div>

Today is the [scheduled release date for Python 3.14.0 beta 1](https://peps.python.org/pep-0745/). I’ll lock the `main` branch after posting this, so we can get the last few buildbot things fixed let the GitHub CI and buildbots can settle down and finish actually testing everything that will get into 3.14 before I start the release process.

If you have anything urgent you really want to get into 3.14 beta 1, **let me know right now** , either in this thread, or on the Core Dev Discord, or email (hugo at python). (I don’t just mean after I lock down the `main` branch, I mean as soon as you read this message. Like, now. Go and check any PRs you have pending.)

Otherwise, new features will have to be pushed to 3.15, and other fixes will have to wait for beta 2. If you’re not sure if your thing is a feature or you would like to find a solution to get something into 3.14 anyway, talk to me.

Thanks!

---

<div class="post-metadata">

**Author:** ![hugovk](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/hugovk/32/14505_2.png) [@hugovk](https://discuss.python.org/u/hugovk)\
**Post date:** [May 6, 2025, 6:22pm UTC](https://discuss.python.org/t/python-3-14-0-beta-1-is-near/90921/2 "2025-05-06T18:22:46Z")

</div>

Update: we hit a bug that only showed up in the release process CI and not regular testing, so let’s pause the release to give some more time to investigate, and re-evaluate tomorrow European time. The `main` branch will stay locked until then.

---

<div class="post-metadata">

**Author:** ![hugovk](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/hugovk/32/14505_2.png) [@hugovk](https://discuss.python.org/u/hugovk)\
**Post date:** [May 7, 2025, 9:53am UTC](https://discuss.python.org/t/python-3-14-0-beta-1-is-near/90921/3 "2025-05-07T09:53:26Z")

</div>

Update: after investigation, looks like the bug is just with the test itself and only shows up when running sequentially and only when run after a certain number of other tests (which can vary by system and build). We’ll make the test more robust for b2, and are now continuing the release.

---

<div class="post-metadata">

**Author:** ![hugovk](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/hugovk/32/14505_2.png) [@hugovk](https://discuss.python.org/u/hugovk)\
**Post date:** [May 7, 2025, 5:03pm UTC](https://discuss.python.org/t/python-3-14-0-beta-1-is-near/90921/4 "2025-05-07T17:03:01Z")

</div>

[Python 3.14.0 beta 1 is here!](https://discuss.python.org/t/python-3-14-0-beta-1-is-here/91117)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex002/uploads/python1/original/1X/3aff56846ebe57781a163dfc748fd1417119d8ab.png) [@system](https://discuss.python.org/u/system)\
**Post date:** [May 6, 2026, 8:54am UTC](https://discuss.python.org/t/python-3-14-0-beta-1-is-near/90921/5 "2026-05-06T08:54:43Z")

</div>

Closed on May 6, 2026, 8:54am UTC

This topic was automatically closed after 365 days. New replies are no longer allowed.