# 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:** 7

<div class="post-metadata">

**Author:** ![brettcannon](https://sea2.discourse-cdn.com/flex002/user_avatar/discuss.python.org/brettcannon/32/34895_2.png) [@brettcannon](https://discuss.python.org/u/brettcannon)\
**Post date:** [June 15, 2022, 9:06pm UTC](https://discuss.python.org/t/should-we-close-issues-for-platforms-not-covered-by-pep-11-or-under-active-development/16437/7 "2022-06-15T21:06:32Z")

</div>

Split this topic on June 15, 2022, 9:06pm UTC

9 posts were split to a new topic: [Usability of GitHub projects for triagers](https://discuss.python.org/t/usability-of-github-projects-for-triagers/16548)

---

_[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)._
