purepy-editor

name	purepy-editor
description	Conventions for editing the PurePy spec and related GitHub issues.

PurePy editor conventions

Style

• Minimal. State the thing; stop.
• No weasel-words like "honest", "clean", "obvious", "simply".
• No defensive coding. If a case shouldn't arise, assert it; don't silently return a safe default.

Git

• Commit after every coherent change; don't sit on uncommitted work.

GitHub issues

• New issues: add to the PurePy project with Status either Planned or Proposed.

• When an issue references other issues or external resources, add a See also paragraph at the end with a bullet list of links. Example:

  ## See also
  
  - Python language reference, §6.10 Comparisons: https://docs.python.org/3/reference/expressions.html#comparisons
  - #36
  - #50
  

  Use this for: cross-references to related issues, links to the Python language reference, links to other external specs.

• When linking to another GitHub issue in a bullet list, write just the bare #N reference — GitHub renders the issue title inline.

Meetings

• Meeting issues are titled YYYY-MM-DD; set Type to Meeting.
• Body sections: ## Adjacent meetings (links to previous), then ## To discuss containing ### Resolved since [date], ### New issues since [date], ### Work since [date].
• Bullet lists of bare #N for issues; brief notes for work items.