> Does that have the effect of expanding all tabs? unicodeobject.c does > use tabs for indenting multiple levels. FWIW, if you want 4-space indents, I think you should use all spaces and not use tabs for double indents. The tabs will be confusing when the code is viewed with a different tab setting (which is sometimes unavoidable). > In my revised patch for unicodedata.c, I put just > > /* > Local variables: > c-basic-offset: 4 > End: > */ > > unicodedata.c is inconsistent in this respect: it sometimes uses tabs, > and sometimes spaces. Even MAL can't complain if you fix that to use all spaces. --Guido van Rossum (home page: http://www.python.org/~guido/)
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4