[Python-mode] bug lp:328842, flexible-indentation of multiline assignements

Andreas Röhler andreas.roehler at online.de
Fri Mar 25 22:20:02 CET 2011


Am 25.03.2011 19:32, schrieb skip at pobox.com:
> I find this indentation truly grating:
>
>          self.last_abc_attr = self.last_xyz_attr = \
>                               self.last_abc_other = \
>                               self.last_xyz_other = None
>
> Now, I can move self.last_xyz_attr to a continuation line, but though the
> result is slightly different, it is, in my opinion, just as bad:
>
>          self.last_abc_attr = \
>                             self.last_xyz_attr = \
>                             self.last_abc_other = \
>                             self.last_xyz_other = None
>
> What I would like to see is this (given a four-space block indent):
>
>          self.last_abc_attr = \
>              self.last_xyz_attr = \
>              self.last_abc_other = \
>              self.last_xyz_other = None
>
> or, if the second expression remained on the first line:
>
>          self.last_abc_attr = self.last_xyz_attr = \
>              self.last_abc_other = \
>              self.last_xyz_other = None
>
> I don't care if this behavior is the default.  I just want to be able to
> control it.  Currently, I have to manually format lines like this, and if
> I'm not careful and reindent an entire function or file, then python-mode
> undoes my work.
>
> Skip
>

Hi Skip,

think that may be done.

As it's a different thing though than indenting inside tuples, lists etc.,
would you mind making a bug entry giving your last examples?

Andreas




More information about the Python-mode mailing list