[Python-Dev] Running Clang 2.7's static analyzer over the code base (original) (raw)
Antoine Pitrou solipsis at pitrou.net
Tue May 4 01:00:02 CEST 2010
- Previous message: [Python-Dev] Running Clang 2.7's static analyzer over the code base
- Next message: [Python-Dev] Running Clang 2.7's static analyzer over the code base
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Benjamin Peterson <benjamin python.org> writes:
2010/5/3 Brett Cannon <brett python.org>: > When I check in these changes I will do it file by file, but my question is > how to handle Misc/NEWS. I have gone through the underscores and the 'a's in > Modules and already have six modified files, so the final count might be a > little high. Do people want individual entries per file, or simply a single > entry that lists each file modified? Do these changes even warrant a NEWS entry? NEWS is more for user facing changes.
Indeed. At most a single NEWS entry sounds sufficient.
Regards
Antoine.
- Previous message: [Python-Dev] Running Clang 2.7's static analyzer over the code base
- Next message: [Python-Dev] Running Clang 2.7's static analyzer over the code base
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]