# Adoption of new Python in PyPI packages, longer RC periods?

**URL:** <https://discuss.python.org/t/adoption-of-new-python-in-pypi-packages-longer-rc-periods/66158>\
**Category:** Core Development\
**Created:** [September 30, 2024, 6:46am UTC](https://discuss.python.org/t/adoption-of-new-python-in-pypi-packages-longer-rc-periods/66158 "2024-09-30T06:46:37Z")\
**Posts on this page:** 1\
**Showing post:** 44

<div class="post-metadata">

**Author:** ![hauntsaninja](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/hauntsaninja/32/12451_2.png) [@hauntsaninja](https://discuss.python.org/u/hauntsaninja)\
**Post date:** [October 9, 2024, 7:19pm UTC](https://discuss.python.org/t/adoption-of-new-python-in-pypi-packages-longer-rc-periods/66158/44 "2024-10-09T19:19:19Z")

</div>

> [@methane](#):
>
> I don’t want to create new release only for adding a classifier for new Python version. Should I do?

Personally, I’d add the classifier at the time it’s green in CI, but only make a release whenever I usually would. There’s some more discussion [in this thread](https://discuss.python.org/t/handling-stale-python-version-classifiers-for-low-churn-projects/66537/6). I would still make a release ASAP when adding version specific wheels (and thank you for adding 3.13 wheels to msgpack!).

I like your idea of opt-in notifications when your build / CI dependencies support the RC!

---

_[View the full topic](https://discuss.python.org/t/adoption-of-new-python-in-pypi-packages-longer-rc-periods/66158)._