[Python-Dev] Running Clang 2.7's static analyzer over the code base (original) (raw)
Antoine Pitrou solipsis at pitrou.net
Tue May 4 14:41:42 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 ]
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.
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.
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 ]