# Is there prior discussion around the build system of CPython itself?

**URL:** <https://discuss.python.org/t/is-there-prior-discussion-around-the-build-system-of-cpython-itself/2813>\
**Category:** Core Workflow\
**Created:** [December 6, 2019, 1:01pm UTC](https://discuss.python.org/t/is-there-prior-discussion-around-the-build-system-of-cpython-itself/2813 "2019-12-06T13:01:03Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![tamas](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/tamas/32/361_2.png) [@tamas](https://discuss.python.org/u/tamas)\
**Post date:** [December 7, 2019, 9:24pm UTC](https://discuss.python.org/t/is-there-prior-discussion-around-the-build-system-of-cpython-itself/2813/10 "2019-12-07T21:24:47Z")

</div>

> [@gpshead](#):
>
> What is really needed is for someone to untangle what actually _matters_ from our autoconf and setup.py pile of code. Turn that subset of needed checks into something other build systems can use to make pyconfig.h and module building decisions.

Agreed.

> An implementation of a new CPython build system that works on non-current macOS/xcode (whatever version our actual binaries use), a few Linuxes on notably different architectures, and a couple of pesky not-dead-yet BSDs would go a long way toward convincing folks of the benefits of such change. Until that work is done, we’re all just pontificating.

Apparently there is cmake build in the works here:

> **[GitHub - python-cmake-buildsystem/python-cmake-buildsystem: A cmake...](https://github.com/python-cmake-buildsystem/python-cmake-buildsystem)**
>
> A cmake buildsystem for compiling Python. Contribute to python-cmake-buildsystem/python-cmake-buildsystem development by creating an account on GitHub.

It seems pretty extensive; I’ll play around with it a bit and try to contact the author.

---

_[View the full topic](https://discuss.python.org/t/is-there-prior-discussion-around-the-build-system-of-cpython-itself/2813)._