# Requires-Python upper limits

**URL:** <https://discuss.python.org/t/requires-python-upper-limits/12663>\
**Category:** Coordination\
**Created:** [December 20, 2021, 6:22pm UTC](https://discuss.python.org/t/requires-python-upper-limits/12663 "2021-12-20T18:22:46Z")\
**Posts on this page:** 1\
**Showing post:** 84

<div class="post-metadata">

**Author:** ![notatallshaw](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/notatallshaw/32/10861_2.png) [@notatallshaw](https://discuss.python.org/u/notatallshaw)\
**Post date:** [February 2, 2025, 7:46pm UTC](https://discuss.python.org/t/requires-python-upper-limits/12663/84 "2025-02-02T19:46:09Z")

</div>

I plan to write a pre-PEP in the next couple of months that formalizes the semantics of `Requires-Python`, based on the discussion in [https://discuss.python.org/t/requires-python-and-pre-release-python-versions/62959](https://discuss.python.org/t/requires-python-and-pre-release-python-versions/62959)

It will specify the semantics as only being the language version part of the version string, i.e. 3.10, 3.11, so not something like 3.11.1, and that the only valid operators as “\>”, “\>=”, and “!=”, and that tools should warn users when they find requires Python strings that don’t match this, and may throw an error (I’m thinking specifically of tools that build source trees).

We’ll see if it achieves consensus and is accepted.

---

_[View the full topic](https://discuss.python.org/t/requires-python-upper-limits/12663)._