[Python-Dev] Running Clang 2.7's static analyzer over the code base (original) (raw)
Victor Stinner victor.stinner at haypocalc.com
Tue May 4 17:26:22 CEST 2010
- Previous message: [Python-Dev] Reindenting patches
- Next message: [Python-Dev] Running Clang 2.7's static analyzer over the code base
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Le mardi 04 mai 2010 14:41:42, Antoine Pitrou a écrit :
Barry Warsaw <barry python.org> writes: > Then let's do py3k and release31-maint, or whatever they will be called > under hg. Once 2.7 is released and we're on hg, how much back porting of > revisions from Python 3 -> 2 is going to happen?
Probably quite a bit still; all C extension bug fixes for example.
2.7 will be maintained for long time, longer than any other 2.x version.
I think we should reindent all 3 branches. Most of the work can probably be scripted (str.replace("\t", " " * 4)), and then a visual pass is necessary to fix vertical alignments and the like.
We should also add pre-commit scripts to avoid the reintroduction of tabulations in C (and Python?) files.
-- Victor Stinner http://www.haypocalc.com/
- Previous message: [Python-Dev] Reindenting patches
- Next message: [Python-Dev] Running Clang 2.7's static analyzer over the code base
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]