# PEP 793 – PyModExport: A new entry point for C extension modules

**URL:** <https://discuss.python.org/t/pep-793-pymodexport-a-new-entry-point-for-c-extension-modules/93444>\
**Category:** PEPs\
**Created:** [May 27, 2025, 4:55am UTC](https://discuss.python.org/t/pep-793-pymodexport-a-new-entry-point-for-c-extension-modules/93444 "2025-05-27T04:55:15Z")\
**Posts on this page:** 1\
**Showing post:** 53

<div class="post-metadata">

**Author:** ![encukou](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/encukou/32/2461_2.png) [@encukou](https://discuss.python.org/u/encukou)\
**Post date:** [January 28, 2026, 11:35am UTC](https://discuss.python.org/t/pep-793-pymodexport-a-new-entry-point-for-c-extension-modules/93444/53 "2026-01-28T11:35:38Z")

</div>

I’d rather lok into adding slots-based inittab API, and keeping that check. It looks like the inittab could [use other improvement as well](https://discuss.python.org/t/43396).

`Py_mod_name` is currently optional. As a workaround, you should be able to leave it out.

Another workaround I’ve been doing in mutliple-ABI experiments is organizing the array to put the “new” slots first, and giving `m_slots` an offset so that it points where the “old” slots start. It’s rather cumbersome with C initializer syntax, but you might have better luck.

---

_[View the full topic](https://discuss.python.org/t/pep-793-pymodexport-a-new-entry-point-for-c-extension-modules/93444)._
