# Can we make the API version more readable? **URL:** \ **Category:** Core Development\ **Created:** [October 31, 2024, 10:44am UTC](https://discuss.python.org/t/can-we-make-the-api-version-more-readable/69767 "2024-10-31T10:44:55Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![da-woods](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/da-woods/32/7507_2.png) [@da-woods](https://discuss.python.org/u/da-woods)\ **Post date:** [October 31, 2024, 11:04am UTC](https://discuss.python.org/t/can-we-make-the-api-version-more-readable/69767/2 "2024-10-31T11:04:39Z")
> [@Adding Py\_PACK\_VERSION](https://discuss.python.org/t/adding-py-pack-version/58887/4): > > IMO, with any name we choose, if you see it in context you’ll almost certainly know what it does. Once you know it, it’s easier to associate PACK with bit-packing. Anyway, I’m not attached to the name. So, Py\_VERSION\_AS\_HEX and Py\_VERSION\_FULL\_AS\_HEX? In CPython, it’s useful to define PY\_VERSION\_HEX. In Cython, micro & release are used relatively often (git grep 0x030 and look for the ones with zeros). Though I’m not sure how many would be there if it was easy to omit them. Perhaps more im… --- _[View the full topic](https://discuss.python.org/t/can-we-make-the-api-version-more-readable/69767)._