# Proposal: close old feature-request issues (Language summit follow up)

**URL:** <https://discuss.python.org/t/proposal-close-old-feature-request-issues-language-summit-follow-up/15776>\
**Category:** Core Development\
**Created:** [May 15, 2022, 10:06pm UTC](https://discuss.python.org/t/proposal-close-old-feature-request-issues-language-summit-follow-up/15776 "2022-05-15T22:06:47Z")\
**Posts on this page:** 1\
**Showing post:** 39

<div class="post-metadata">

**Author:** ![AA-Turner](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/aa-turner/32/4979_2.png) [@AA-Turner](https://discuss.python.org/u/AA-Turner)\
**Post date:** [June 8, 2022, 2:58pm UTC](https://discuss.python.org/t/proposal-close-old-feature-request-issues-language-summit-follow-up/15776/39 "2022-06-08T14:58:37Z")

</div>

> [@iritkatriel](#):
>
> something like close if 3 core devs/triagers vote -1 and nobody votes +1.

This seems quite a high requirement – requiring on the order of 15,000 votes to work through the backlog of issues. But perhaps formality is what is required – I’m not sure, for instance, if I can close issues for platforms unsupported per PEP 11 currently, or for EOL versions of Python – this would cut down the backlog significantly (at least a couple of hundred issues, if not 4 figures).

A

---

_[View the full topic](https://discuss.python.org/t/proposal-close-old-feature-request-issues-language-summit-follow-up/15776)._
