# Conversion between Python and C integers

**URL:** <https://discuss.python.org/t/conversion-between-python-and-c-integers/44117>\
**Category:** Core Development\
**Tags:** c-api\
**Created:** [January 25, 2024, 11:39am UTC](https://discuss.python.org/t/conversion-between-python-and-c-integers/44117 "2024-01-25T11:39:47Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pitrou](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/pitrou/32/28_2.png) [@pitrou](https://discuss.python.org/u/pitrou)\
**Post date:** [January 25, 2024, 1:50pm UTC](https://discuss.python.org/t/conversion-between-python-and-c-integers/44117/2 "2024-01-25T13:50:08Z")

</div>

> [@storchaka](#):
>
> Why there is so strange API for unsigned types? I think there are several reasons

Also the fact that unsigned _types_ (not just values) are less common and less useful than signed ones. That said, I agree that all those APIs should be made consistent in scope, and if possible cover the useful range of integer types, _including_ explicitly-sized types such as `int32_t` and `int64_t`.

---

_[View the full topic](https://discuss.python.org/t/conversion-between-python-and-c-integers/44117)._