On Friday, October 10, 2014 5:19:06 PM UTC-5, Matt Wilkie wrote:
>
> Replying here 'cause I'm not sure it's worth re-opening beautify #68 for
> more work at this point, but should still be in the record for future:
>
> Over zealous escaping single quotes. Escapes those within triple quotes,
> and behind comment markerS:
>
> # this doesn't need a doesn\'t
> ''' and neither does this one: ain't it true? '''
>
Version 1.23 fixes the problem with escapes in comments.
However, under still-unclear conditions a top-level docstring following a
comment will either a) disappear entirely (!!!) or b) move before the
comment. Obviously, this is unacceptable data loss or corruption. I'll
look into it.
We may need a setting that chooses between the newly-improved legacy
beautifier or PythonTidy. I'd like to avoid that, but PythonTidy does not
look robust. As another problem, tidy will throw an exception on
indentation errors, which is not smooth...
Extra brackets (this might be just me discovering that I really do have a
> strong personal preference at odds with pep8 after all ;-)
>
> for k in "some, list, easy, to, type".split(', '):
> ...
> d['path'],d['size'],d['md5'] = d['compound'].split()
>
> becomes the extra noisy:
>
> for k in ("some, list, easy, to, type").split(', '):
> ...
> (d['path'], d['size'], d['md5']) = d['compound'].split()
>
This appears to have been fixed, provided you set::
@bool tidy_parenthesized_tuple_display = False
Edward
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/leo-editor.
For more options, visit https://groups.google.com/d/optout.
