Refered this way from CleaningUpCode
Generalized python format so you don't have to infer date format from the TAL example.
|Deletions are marked like this.||Additions are marked like this.|
|Line 12:||Line 12:|
|# XXX: SteveAlexander 2007-03-12 bug=12345: This code is going to
# fail after next year.}}}
|# XXX: SteveAlexander YYYY-MM-DD bug=NNNN: Comment here.}}}|
Policy Name: XXX Policy (aka The Triple X Policy)
Policy Owner: Joey Stanford
- We put "XXX" in our code in a specific format to denote areas requiring follow up.
# XXX: SteveAlexander YYYY-MM-DD bug=NNNN: Comment here.
<tal:XXX condition="nothing">YYYYMMDD mpt: Comment here.</tal:XXX>
The XXX cannot be followed by a colon here, because that would be an XML error. And if the XXX was put inside the element instead, that would make the code longer and XXXes a bit harder to find. (See also bug 120005, "Page template comment syntax is too verbose".)
- We should ensure that there is a bug or spec assigned to each XXX.
Our current tools use the following regex (XXX:?|TODO|FIXME) which means XXX will be found even if it does not have a colon.
TODO comments are permitted in the same format. See Zope's comments on this.
- FIXME items should be listed as XXX.
- Reviewers will not approve code that does not follow this format.
- Developers when modifying code which contains an XXX block should strive to resolve the XXX if possible.
- The use of this standardized format allows us to write scripts which scan our code for these areas and generate reports. This enables us to identify areas of our code which may need further attention.
- Affects: All Launchpad Code
- Term: Permanent
XXX Listing (python only, doesn't cover TAL comments)