# Python 3.14.0rc3 is go!

**URL:** <https://discuss.python.org/t/python-3-14-0rc3-is-go/103815>\
**Category:** Core Development\
**Tags:** release\
**Created:** [September 18, 2025, 12:03pm UTC](https://discuss.python.org/t/python-3-14-0rc3-is-go/103815 "2025-09-18T12:03:10Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![h-vetinari](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/h-vetinari/32/1220_2.png) [@h-vetinari](https://discuss.python.org/u/h-vetinari)\
**Post date:** [September 19, 2025, 8:04pm UTC](https://discuss.python.org/t/python-3-14-0rc3-is-go/103815/14 "2025-09-19T20:04:20Z")

</div>

Thanks Paul!

> [@pf\_moore](#):
>
> It’s not like we make changes like this during the RC phase lightly. Any information about impact is useful to the RM when they make the call, but we’ll still make such changes if it seems like the benefits are greater than the costs.

My observation (no finger pointing) is that @hugovk was very [cautious](https://discuss.python.org/t/early-3-14-0-rc2-and-extra-rc3/102151/3) when the first magic build number bump happened for rc2. But no similar discussion was had (at least publicly, to my knowledge) when another bump occurred for rc3 – ironically, this could be because no-one screamed when it happened for rc2, but at least in our case, that was because we waited with starting the rebuilds until rc2 was available [precisely](https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/7648#issuecomment-3178678030) due to this issue.

---

_[View the full topic](https://discuss.python.org/t/python-3-14-0rc3-is-go/103815)._