iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

minor revision by the author

This commit is contained in:
David Goodger 2005-09-26 23:38:14 +00:00
parent 7eb98f7425
commit d9383b4772
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
pep-0350.txt
View File

@ -7,7 +7,7 @@ Status: Draft
Type: Informational
Content-Type: text/x-rst
Created: 27-Jun-2005
Post-History: 10-Aug-2005
Post-History: 10-Aug-2005, 26-Sep-2005
Abstract
@ -20,11 +20,11 @@ making Python code more uniform across projects. Codetags also
represent a very lightweight programming micro-paradigm and become
useful for project management, documentation, change tracking, and
project health monitoring. This is submitted as a PEP because its
ideas are Pythonic, although the concepts are not unique to Python
programming. Herein are the definition of codetags, the philosophy
behind them, a motivation for standardized conventions, some examples,
a specification, a toolset description, and possible objections to the
Codetag project/paradigm.
ideas are thought to be Pythonic, although the concepts are not unique
to Python programming. Herein are the definition of codetags, the
philosophy behind them, a motivation for standardized conventions,
some examples, a specification, a toolset description, and possible
objections to the Codetag project/paradigm.
This PEP is also living as a wiki_ for people to add comments.
@ -270,7 +270,7 @@ The codetags of interest are listed below, using the following format:
``SEE (REF, REFERENCE)``
*See*: Pointers to other code, web link, etc.
``DOCDO (TODOC, DODOC, NEEDSDOC, EXPLAIN, DOCUMENT)``
``TODOC (DOCDO, DODOC, NEEDSDOC, EXPLAIN, DOCUMENT)``
*Needs Documentation*: Areas of code that still need to be
documented.