# Should we close issues for platforms not covered by PEP 11 or under active development?

**URL:** <https://discuss.python.org/t/should-we-close-issues-for-platforms-not-covered-by-pep-11-or-under-active-development/16437>\
**Category:** Core Development\
**Created:** [June 10, 2022, 7:31pm UTC](https://discuss.python.org/t/should-we-close-issues-for-platforms-not-covered-by-pep-11-or-under-active-development/16437 "2022-06-10T19:31:24Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![hugovk](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/hugovk/32/14505_2.png) [@hugovk](https://discuss.python.org/u/hugovk)\
**Post date:** [June 12, 2022, 8:27am UTC](https://discuss.python.org/t/should-we-close-issues-for-platforms-not-covered-by-pep-11-or-under-active-development/16437/5 "2022-06-12T08:27:24Z")

</div>

Disadvantage of projects:

- Triagers can’t add/remove issues

---

_[View the full topic](https://discuss.python.org/t/should-we-close-issues-for-platforms-not-covered-by-pep-11-or-under-active-development/16437)._
