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

[Ben]

I've found the unexpand command, which seems to do the trick. However,
it outputs to standard output, and I haven't worked out yet how to
capture that output to a file...

Ben

Ben wrote:

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-27, Ben <Be************ *@gmail.comwrot e:

I've found the unexpand command, which seems to do the trick. However,
it outputs to standard output, and I haven't worked out yet how to
capture that output to a file...

unexpand <file1 >file2

--
Grant Edwards grante Yow! Hey, LOOK!! A pair of
at SIZE 9 CAPRI PANTS!! They
visi.com probably belong to SAMMY
DAVIS, JR.!!

[Ben]

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

Cheers,

Ben
Grant Edwards wrote:

On 2006-12-27, Ben <Be************ *@gmail.comwrot e:

I've found the unexpand command, which seems to do the trick. However,
it outputs to standard output, and I haven't worked out yet how to
capture that output to a file...

unexpand <file1 >file2

--
Grant Edwards grante Yow! Hey, LOOK!! A pair of
at SIZE 9 CAPRI PANTS!! They
visi.com probably belong to SAMMY
DAVIS, JR.!!

[Grant Edwards]

On 2006-12-27, Ben <Be************ *@gmail.comwrot e:

>>I've found the unexpand command, which seems to do the trick. However,
it outputs to standard output, and I haven't worked out yet how to
capture that output to a file...

unexpand <file1 >file2

Great - that worked.Thanks!

Is that a general method in linux you can always use to redirect
standard output to a file?

Yup. The "<" operator redirects stdin, the ">" operator
redirects stdout. "2>" redirects stderr.

--
Grant Edwards grante Yow! Let's go to CHURCH!
at
visi.com

[Sebastian 'lunar' Wiesner]

Ben <Be************ *@gmail.comtype d

I have a python script on a windows system that runs fine. Both use
tabs to indent sections of the code.

Just a tip for you: In python you never use tabs for indentation. The
python style guide [1] recommends four spaces per indentation level.

[1] http://www.python.org/dev/peps/pep-0008/

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

[Ben Finney]

"Sebastian 'lunar' Wiesner" <ba***********@ gmx.netwrites:

Just a tip for you: In python you never use tabs for indentation.

For some value of "you".

The python style guide [1] recommends four spaces per indentation
level.

[1] http://www.python.org/dev/peps/pep-0008/

It's not quite absolute on the topic:

For new projects, spaces-only are strongly recommended over tabs.

--
\ "I filled my humidifier with wax. Now my room is all shiny." |
`\ -- Steven Wright |
_o__) |
Ben Finney

[Gabriel Genellina]

At Wednesday 27/12/2006 20:09, Ben Finney wrote:

The python style guide [1] recommends four spaces per indentation
level.

[1] http://www.python.org/dev/peps/pep-0008/

It's not quite absolute on the topic:

For new projects, spaces-only are strongly recommended over tabs.

Of course you can do it anyway you like, but you should have a
*strong* reason for not following a *strong* recommendation.
(Just a note, you can use untabify.py (inside the Tools dir) to
convert tabs to spaces, instead of unexpand)
--
Gabriel Genellina
Softlab SRL


_______________ _______________ _______________ _____
Preguntá. Respondé. Descubrí.
Todo lo que querías saber, y lo que ni imaginabas,
está en Yahoo! Respuestas (Beta).
¡Probalo ya!
http://www.yahoo.com.ar/respuestas

[Erik Johnson]

"Ben Finney" <bi************ ****@benfinney. id.auwrote in message
news:ma******** *************** *************** *@python.org...

"Sebastian 'lunar' Wiesner" <ba***********@ gmx.netwrites:

Just a tip for you: In python you never use tabs for indentation.

For some value of "you".

The python style guide [1] recommends four spaces per indentation
level.

[1] http://www.python.org/dev/peps/pep-0008/

It's not quite absolute on the topic:

For new projects, spaces-only are strongly recommended over tabs.

Even if were, read the Introduction. This is a coding standard intended
to apply to code which is going to checked in as part of the core python
build, not all Python! It's probably a pretty good standard to be following
in general, but come on... If Guido really wanted this enforced across the
board he could simply call anything that doesn't meet this standard to the
letter a SyntaxError and just stop there. For example, the standard states:

- Imports should usually be on separate lines, e.g.:

Yes: import os
import sys

No: import sys, os

>>import sys, os

Traceback (most recent call last):
File "<stdin>", line 1, in ?
ImportError: Sorry, only one module per import line!
I'm sure that's not Guido's intention. ;)

-ej

[Steven D'Aprano]

On Wed, 27 Dec 2006 20:15:33 +0100, Sebastian 'lunar' Wiesner wrote:

Ben <Be************ *@gmail.comtype d

>I have a python script on a windows system that runs fine. Both use
tabs to indent sections of the code.

Just a tip for you: In python you never use tabs for indentation. The
python style guide [1] recommends four spaces per indentation level.

[1] http://www.python.org/dev/peps/pep-0008/

[obligatory pot-shot in the never-ending spaces versus tabs war]

In Python, I frequently use tabs for indentation, and I never have any
trouble *except* when posting code to Usenet, where other people's news
readers can't cope with tabs.

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

--
Steven D'Aprano