space/tab conversion utility?

[Grant Edwards]

Is there any utility to convert Python sources from space-based
block indentation to tab-based?

You can use "expand" convert from tabs->spaces, but "unexpand"
isn't bright enough to do the reverse.

--
Grant Edwards grante Yow! By MEER biz doo
at SCHOIN...
visi.com

[Grant Edwards]

On 2004-07-29, Tim Peters <ti********@gma il.com> wrote:

[Grant Edwards, wants to convert spaces to tabs]

...
2) Simply converting all leading spaces to the right number of
tabs (unexpand knows how to do that) isn't correct. Only
the spaces that are block-indent spaces should be converted.

...

reindent.py is in your Python distribution, and is the state
of the art for "intelligen t" conversion of tab-infected files
to space-celebrating ones. I understand that's not the
direction you want, but it is the *code* you want to start
from. [...]

That does indeed sound like the right starting point. The
other option I can think of would be to hack up Jed's
Python-mode so that it attempts to automatically detect whether
tabs or spaces should be used.

Or I could go work on my car.

--
Grant Edwards grante Yow! BEEP-BEEP!! I'm a
at '49 STUDEBAKER!!
visi.com

[Martin Bless]

[Tim Peters <ti********@gma il.com>:]

reindent.py is in your Python distribution, and is the state of the
art for "intelligen t" conversion of tab-infected files to
space-celebrating ones.

I'm carrying a question around for quite a while now and it seems to
fit into this context. The issue is "configurat ion files".

I'm not really happy with "configpars er" for some reasons and would
much more use python code itself as the natural und preferred way to
write configuration data.

The idea is to read the configuration file, which should be Python
code, and accept only statements that can't be harmful. A grammar
somehow like this (as a sketch, written before breakfast):

value := "string constant" | "num constant" | ...
seq := (value*) | [value*]
assignment := name = seq | value
.... and so on. To be elaborated.

In words: have assignments in the config file and accept only values
and structures that can do no harm. I'm not familiar with tokenizing
and python source code parsing yet.

My question:

Do you think I could accomplished this using standard Python means?
I'm thinking of the tokenize module, which I haven't used yet.

Will it be possible / easy / difficult?

Martin

[Pierre-Frédéric Caillaud]

- Open file in editor which uses tabs (like Scite set to use tabs)
- Ctrl-A
- Tab
- Shift-Tab
- Et voilà...

This just indents and dedents the whole program. A side-effect is that
the editor converts spaces to tabs. It also works the other way.

If your program is worrectly indented, it'll stay that way with tabs.

On 28 Jul 2004 21:49:34 GMT, Grant Edwards <gr****@visi.co m> wrote:

Is there any utility to convert Python sources from space-based
block indentation to tab-based?

You can use "expand" convert from tabs->spaces, but "unexpand"
isn't bright enough to do the reverse.

[Marco Aschwanden]

On 28 Jul 2004 21:49:34 GMT, Grant Edwards <gr****@visi.co m> wrote:

Is there any utility to convert Python sources from space-based
block indentation to tab-based?

WingIDE (commercial; http://www.wingware.com/) does the switching in both
ways at any time!
Regards,
Marco

[Catalin Marinas]

Grant Edwards <gr****@visi.co m> writes:

So that I can submit patches to a Python application whos
devloper uses tabs. My Python editor uses spaces.

You have different options to the diff command for this:

-E --ignore-tab-expansion Ignore changes due to tab expansion.
-b --ignore-space-change Ignore changes in the amount of white space.
-w --ignore-all-space Ignore all white space.
-B --ignore-blank-lines Ignore changes whose lines are all blank.

Otherwise, a simple sed script might do it (convert 4 spaces to one
tab for example):

sed -e "s/ /\t/g/"

Catalin

[Grant Edwards]

On 2004-07-29, Catalin Marinas <ca************ *@arm.com> wrote:

So that I can submit patches to a Python application whos
devloper uses tabs. My Python editor uses spaces.
You have different options to the diff command for this:

-E --ignore-tab-expansion Ignore changes due to tab expansion.
-b --ignore-space-change Ignore changes in the amount of white space.
-w --ignore-all-space Ignore all white space.
-B --ignore-blank-lines Ignore changes whose lines are all blank.

But the lines of code I added will still be indented with
spaces, and the program's author uses tabs.
Otherwise, a simple sed script might do it (convert 4 spaces
to one tab for example):

sed -e "s/ /\t/g/"

Nope, that doesn't work for reasons already discussed. Even if
you restrict it to spaces at the beginning of the line (e.g.
unexpand -t4 --first-only) it still breaks things.

--
Grant Edwards grante Yow! I just remembered
at something about a TOAD!
visi.com