Re: I hate you all
On Saturday, April 6, 2013 7:28:55 AM UTC+3, Dylan Evans wrote: > On Sat, Apr 6, 2013 at 7:41 AM, wrote: > > Hello > > > I just tried python 3.3 with some simple script meant for unit test. > > How can python authors be so arrogant to impose their tabs and spaces options > on me ? It should be my choice if I want to use tabs or not ! > > > Don't like it? Use ruby. Actually next on my list is perl. I know ruby is sexy, but taming the wild beast is what makes me feel like the real cowboy. -- http://mail.python.org/mailman/listinfo/python-list
Re: I hate you all
On Saturday, April 6, 2013 1:42:15 AM UTC+3, Ian wrote: [...] > The "def" line has four spaces. The "for" line then has a hard tab. > This is ambiguous. If the hard tab is assumed to have a width of four > spaces, then they are at the same indentation level. If it is assumed > to have a width of eight spaces, then they are not. [...] The correct tab stop positions have always been at 8 character columns apart. The "ambiguity" was introduced by editors that do not follow the default value set in hardware like printers or used by consoles and terminal emulators. And now python forces me out of using any tab characters at all. I believe I should still have a choice, python should at lest give an option to set tab size, if the default of 8 is ambiguous now. Thank you, Timothy Madden -- http://mail.python.org/mailman/listinfo/python-list
Re: I hate you all
On Saturday, April 6, 2013 12:55:29 AM UTC+3, John Gordon wrote: > In <64d4fb7c-6a75-4b5f-b5c8-06a4b2b5d...@googlegroups.com> > terminato...@gmail.com writes: > > > How can python authors be so arrogant to impose their tabs and spaces > > options on me ? It should be my choice if I want to use tabs or not ! > > You are free to use tabs, but you must be consistent. You can't mix > tabs and spaces for lines of code at the same indentation level. They say so, but python does not work that way. This is a simple script: from unittest import TestCase class SvnExternalCmdTests(TestCase) : def test_parse_svn_external(self) : for sample_external in sample_svn_externals : self.assertEqual(parse_svn_externals(sample_external[0][0], sample_external[0][1]), [ sample_external[1] ]) And at the `for` statement at line 5 I get: C:\Documents and Settings\Adrian\Projects>python sample-py3.py File "sample-py3.py", line 5 for sample_external in sample_svn_externals : ^ TabError: inconsistent use of tabs and spaces in indentation Line 5 is the only line in the file that starts at col 9 (after a tab). Being the only line in the file with that indent level, how can it be inconsistent ? You can try the script as it is, and see python 3.3 will not run it -- http://mail.python.org/mailman/listinfo/python-list
I hate you all
Hello I just tried python 3.3 with some simple script meant for unit test. How can python authors be so arrogant to impose their tabs and spaces options on me ? It should be my choice if I want to use tabs or not ! I know people have all goten into this frenzy of using either tabs, either spaces for indentation, but using a hard-tab of 8 spaces and a soft tab of 4 spaces has worked fine long before python 3 showed up. And if they decided to throw a TabError, they should have at least created an option to specify tab size, so I can work around that. I am aware that so many editors use a tab stop of 4 spaces instead of 8 (which by the way started as a cheap way to work around their initial lack of a "soft tab stop" option, and then was kept at 4 for "compatibility"). But the rest of us who always use a tab stop of 8 should not be forced to change preferences because python reached version 3. Timothy Madden -- http://mail.python.org/mailman/listinfo/python-list
