Clarifying PEP 11 around dropping support

Open
#226 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
documentation

Research direction

Read PEP 11's “Unsupporting Platforms” section and the linked Python Discourse discussion first. Determine which support or notification policy the Steering Council adopts, then update the relevant policy wording or What's New notice; done means the interpretation is explicit and consistent with the selected option.

Written by the indexing model from the issue text.

Description

https://discuss.python.org/t/im-stepping-down-as-sponsor-of-emscripten/41064/6 has Pyodide asking how to interpret https://peps.python.org/pep-0011/#unsupporting-platforms and the fact it calls for building to fail to "potential users of the platform a chance to step forward and offer maintenance" while we have no concept of community support w/o a sponsor.

A couple of options that I can think of:

  1. Take out the line about giving the community a chance to find support
  2. Change it to say it's a chance to find a core dev sponsor
  3. We don't require a build error, but we do require a notice in What's New
Dominant language
Makefile
Stars
183
Forks
34
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from python/steering-council

All issues in python/steering-council

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.