This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author tim.peters
Recipients gvanrossum, loewis, r.david.murray, rohdef, tim.peters
Date 2009-09-29.11:42:58
SpamBayes Score 2.9903018e-07
Marked as misclassified No
Message-id <1254224580.13.0.0586554306272.issue7012@psf.upfronthosting.co.za>
In-reply-to
Content
I understand you're annoyed, but the bug tracker is not the place to
rehash arguments that were settled a decade ago.  If you need to pursue
this, please take it to the newsgroup comp.lang.python.  Before you do,
you might want to scour the newsgroup's archives, as millions of words
of debate on this topic have already taken place, mostly in the early to
mid 90's.  Nobody has anything new to say on this topic :-(

Note that nobody objects if you want to use tabs, or even mix tabs and
spaces, in your own code.  The Python "spaces only" standard is for
distributed code.  Years of early experience taught us beyond doubt that
tabs caused endless problems for /shared/ code, to the extent that the
Python distribution contains utilities to detect when mixing tabs and
spaces can cause semantic differences (tabnanny.py) and to reformat
source files to replace all tabs with spaces (reindent.py).

Indeed, if you want to contribute to the Python distribution and insist
on using tabs, that's fine:  simply run your code through reindent.py
before submitting your patch.  Otherwise, just like this feature
request, your patch will be rejected ;-)
History
Date User Action Args
2009-09-29 11:43:00tim.peterssetrecipients: + tim.peters, gvanrossum, loewis, r.david.murray, rohdef
2009-09-29 11:43:00tim.peterssetmessageid: <1254224580.13.0.0586554306272.issue7012@psf.upfronthosting.co.za>
2009-09-29 11:42:58tim.peterslinkissue7012 messages
2009-09-29 11:42:58tim.peterscreate