DOS, UNIX and tabs

[Ben]

Hi,

I have a python script on a unix system that runs fine. I have a python
script on a windows system that runs fine. Both use tabs to indent
sections of the code. I now want to run them on the same system,
actually in the same script by combining bits and pieces. But whatever
I try my windows tabs get converted to spaces when I transfer it to the
unix system and the interpreter complains that the indentation style is
not consistent throughout the file. Short of going through 350 lines of
code and manually replacing spaces with tabs what an I do? I'm thinking
there surely must be a simple solution I have missed here!

Cheers,

Ben

[Grant Edwards]

On 2006-12-28, Felix Benner <fe**********@i mail.dewrote:

I like using tabs. And the style guide doesn't give a reason
why one shouldn't and neither does the thread
http://www.python.org/search/hyperma...94q2/0198.html
in the archive. So what's the point in typing four spaces for
indentation instead of one tab?

So that the whole Python source tree is consistent.

--
Grant Edwards grante Yow! What I want to find
at out is -- do parrots know
visi.com much about Astro-Turf?

[Sebastian 'lunar' Wiesner]

Marc 'BlackJack' Rintsch <bj****@gmx.net typed

In <en**********@r egistered.motza rella.org>, Felix Benner wrote:

>I like using tabs. And the style guide doesn't give a reason why one
shouldn't and neither does the thread
http://www.python.org/search/hyperma...94q2/0198.html in the
archive.

This is a religious issue

It is, because god itself used four spaces for indentation when he wrote
his "world" project in seven days ;)

--
Freedom is always the freedom of dissenters.
(Rosa Luxemburg)

[Tom Plunket]

Steven D'Aprano wrote:

I don't know what "problems" with tabs you are talking about. I never have
problems with tabs. *Other people* who choose to use software that doesn't
understand tabs have problems.

I've spent a lot of time reading both sides of the tabs versus spaces
argument, and I haven't found anything yet that explains why tabs are, in
and of themselves, bad.

Indeed. In fact, I came to the conclusion several years ago that tabs
are in better for formatting code because then different people on the
team can have their preferred tabstop width, be it 8, 4, or 2 spaces.
Ironically, it has always seemed to me then that tabs are superior for
python editing, since mixing tabs and spaces in an environment like this
means that stuff won't run, whereas in C it'll still compile even if the
code looks awful.
-tom!

--

[Paul McNett]

Steven D'Aprano wrote:

But I think we all agree that mixing tabs and spaces is A Very Bad Thing.

I like mixing tabs and spaces, actually. Tabs for indentation, and
additional spaces to make the code "look pretty". Somebody please tell
me why this is bad and I'll stop.

class Apple(object):
def contrived_examp le_function(sel f, argument1, argument2,
argument3, argument4):
print "hello, world"

Apparently, emacs in python mode follows this convention, too. I like it
because I get the best of both worlds: the only thing against using
tabs-only-indentation is that wrapping long lines can be quite ugly,
while space-only-indentation allows for beautifying it somewhat by
lining up the columns to match. Tabs+spaces allows the "lining up" with
spaces to be explicitly separate from indentation.

--
pkm ~ http://paulmcnett.com

[Tim Roberts]

"Ben" <Be************ *@gmail.comwrot e:

>
Great - that worked.Thanks!
Is that a general method in linux you can always use to redirect
standard output to a file?

Works in Windows, too.
--
Tim Roberts, ti**@probo.com
Providenza & Boekelheide, Inc.

[Sebastian 'lunar' Wiesner]

Paul McNett <[e-mail] typed

Steven D'Aprano wrote:

>But I think we all agree that mixing tabs and spaces is A Very Bad
Thing.

I like mixing tabs and spaces, actually. Tabs for indentation, and
additional spaces to make the code "look pretty". Somebody please tell
me why this is bad and I'll stop.

class Apple(object):
def contrived_examp le_function(sel f, argument1, argument2,
argument3, argument4):
print "hello, world"

Apparently, emacs in python mode follows this convention, too.

That doesn't seem like a standard settings to me. I can't remember
changing the indentation settings for python, nonetheless my gnu emacs
uses four spaces for indentation. Placing wrapped lines into ordered
columns is done by inserting additional spaces. This all happens
automatically; you never need to insert spaces manually...

I like it because I get the best of both worlds: the only thing
against using tabs-only-indentation is that wrapping long lines can be
quite ugly, while space-only-indentation allows for beautifying it
somewhat by lining up the columns to match.

Did you try to open your code files with another editor, which has a
different length for tabulator chars? It would look quite ugly, I
guess...

--
Freedom is always the freedom of dissenters.
(Rosa Luxemburg)

[Paul McNett]

Sebastian 'lunar' Wiesner wrote:

Paul McNett <[e-mail] typed

>Steven D'Aprano wrote:

>>But I think we all agree that mixing tabs and spaces is A Very Bad
Thing.

I like mixing tabs and spaces, actually. Tabs for indentation, and
additional spaces to make the code "look pretty". Somebody please tell
me why this is bad and I'll stop.

class Apple(object):
def contrived_examp le_function(sel f, argument1, argument2,
argument3, argument4):
print "hello, world"

Apparently, emacs in python mode follows this convention, too.

That doesn't seem like a standard settings to me. I can't remember
changing the indentation settings for python, nonetheless my gnu emacs
uses four spaces for indentation. Placing wrapped lines into ordered
columns is done by inserting additional spaces. This all happens
automatically; you never need to insert spaces manually...

I never tried emacs, but somebody once told me that if you have set
indentation-by-tab, it will indent with tabs but insert additional
spaces in wrapped lines to look pretty.

>I like it because I get the best of both worlds: the only thing
against using tabs-only-indentation is that wrapping long lines can be
quite ugly, while space-only-indentation allows for beautifying it
somewhat by lining up the columns to match.

Did you try to open your code files with another editor, which has a
different length for tabulator chars? It would look quite ugly, I
guess...

Actually, no. Everyone can choose their own number of spaces-per-tab and
it'll look right, as long as everyone uses a monospace font.

--
pkm ~ http://paulmcnett.com

[Marc 'BlackJack' Rintsch]

In <ma************ *************** ************@py thon.org>, Paul McNett
wrote:

>Did you try to open your code files with another editor, which has a
different length for tabulator chars? It would look quite ugly, I
guess...

Actually, no. Everyone can choose their own number of spaces-per-tab and
it'll look right, as long as everyone uses a monospace font.

You never tried that with tabs plus additional spaces to line up e.g.
arguments that are broken across lines, right?

And there are a number of environments where you can't change the length
of a tab like email or terminals where code will be displayed from time to
time for example as diffs from a version control system.

Ciao,
Marc 'BlackJack' Rintsch

[Lawrence D'Oliveiro]

In message <pa************ *************** *@gmx.net>, Marc 'BlackJack'
Rintsch wrote:

In <ma************ *************** ************@py thon.org>, Paul McNett
wrote:

>Everyone can choose their own number of spaces-per-tab and
it'll look right, as long as everyone uses a monospace font.

You never tried that with tabs plus additional spaces to line up e.g.
arguments that are broken across lines, right?

I prefer a more two-dimensional layout, keeping consistent indentation. To
illustrate using the example from Paul McNett:

class Apple(object):
Â*Â*Â*Â*Â*Â*Â*Â *def contrived_examp le_function \
(
self,
argument1,
argument2,
argument3,
argument4
) :
Â*Â*Â*Â*Â*Â*Â*Â *Â*Â*Â* print "hello, world"
#end contrived_examp le_function
#end Apple

[Tom Plunket]

Marc 'BlackJack' Rintsch wrote:

Did you try to open your code files with another editor, which has a
different length for tabulator chars? It would look quite ugly, I
guess...

Actually, no. Everyone can choose their own number of spaces-per-tab and
it'll look right, as long as everyone uses a monospace font.

You never tried that with tabs plus additional spaces to line up e.g.
arguments that are broken across lines, right?

You must not understand what they're talking about, because it works
fine.

The example is this:

"""\
class Foo:
\tdef Function():
\t\tAnotherFunc tionThatTakesMa nyArguments(arg 1,
\t\t arg2,
\t\t arg3)
"""

And there are a number of environments where you can't change the length
of a tab like email or terminals where code will be displayed from time to
time for example as diffs from a version control system.

That's the point of doing it in this way with tabs to specify indent
level and spaces to specify tabular alignment.

Me, I could never get emacs's python stuff to work suitably so I just
use a Dead Simple Editor (SciTE) in which I use tabs exclusively;
continuation indents are always exactly one additional tab over the
thing that's being continued.

Perhaps interestingly, for development I have my editor set to show tabs
as fairly short, but my diff program shows them as eight characters. I
find that makes indentation changes easier to spot in the diffs.
-tom!

--