# The next manylinux specification

**URL:** <https://discuss.python.org/t/the-next-manylinux-specification/1043>\
**Category:** Packaging\
**Created:** [March 22, 2019, 7:59pm UTC](https://discuss.python.org/t/the-next-manylinux-specification/1043 "2019-03-22T19:59:25Z")\
**Posts on this page:** 1\
**Showing post:** 233

<div class="post-metadata">

**Author:** ![pf\_moore](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/pf_moore/32/35_2.png) [@pf\_moore](https://discuss.python.org/u/pf_moore)\
**Post date:** [October 1, 2019, 7:26pm UTC](https://discuss.python.org/t/the-next-manylinux-specification/1043/233 "2019-10-01T19:26:51Z")

</div>

> [@zwol](#):
>
> me and @sumanah have tentative plans to scare up funding, to hire someone with current experience with the guts of the GNU Compiler Collection, to put in that time and write that report. Once we have it, I think I can promise to produce a proposal.
> 
> I can’t commit to a timeframe for any of that at the moment, but since I think PEP 600 should be deferred until after the manylinux2014 rollout has happened _anyway_ , and that’s going to be several months at least, I don’t see that as a problem.

Any update on this? It’s been a bit over a month since you made that comment, and `manylinux2014` is moving along. I don’t want to get into a debate over when the rollout will be considered to “have happened” but hopefully you at least have a better idea of when you expect a proposal to be ready (in ballpark terms if nothing else).

---

_[View the full topic](https://discuss.python.org/t/the-next-manylinux-specification/1043)._