Clarifying PEP 11 around dropping support
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:
- Take out the line about giving the community a chance to find support
- Change it to say it's a chance to find a core dev sponsor
- We don't require a build error, but we do require a notice in What's New
- Dominant language
- Makefile
- Stars
- 183
- Forks
- 34
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from python/steering-council
-
Difficulty 1/5 Under an hour Newbie friendliness 60/100
python/steering-council#364 ·
-
PEP
Difficulty 5/5 Over a week Newbie friendliness 25/100
python/steering-council#348 · 1 comment ·
-
PEP
Difficulty 5/5 Over a week Newbie friendliness 25/100
python/steering-council#336 · 1 comment · 2 reactions ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
python/steering-council#298 · 3 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
python/steering-council#124 · 2 comments · 3 reactions ·
All issues in python/steering-council
Similar issues
-
agent-ready documentation needs-triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
untriaged
Difficulty 1/5 Under an hour Newbie friendliness 88/100
dotnet/dotnet-api-docs#13095 ·
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 91/100
-
workflow-status page template still says reusable workflows are "triggered only by workflow_call:" Open
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
refactor
Difficulty 2/5 1-3 hours Newbie friendliness 78/100