On Tue, Nov 27, 2012 at 10:51 AM, Jason Grout <jason-s...@creativetrax.com> wrote: > On 11/24/12 7:41 PM, Robert Bradshaw wrote: > >> Cool. (The doable part, not the unholy mess part :-). If that's the >> case, how about we simply ignore the issue at the moment, remove it >> all in the git conversion, and document + enforce a no-whitespace >> policy as as part of the new development workflow. If there are no >> objections, I'll write this up in #11956 as a new official policy. > > > What if the line is entirely whitespace? I think it's rather nice to have > the empty line below be padded with 4 spaces so I can just move my cursor to > the empty line and start typing and things are automatically on the right > indentation level: > > for i in range(10): > some long calculation > > some other long calculation
I'd say this is not worth an exception--it's much easier to disallow all whitespace (and to use tools that strip all whitespace). Any sane editor will tab to the right place. > Here's an example of code that changes behavior when there is trailing > whitespace: > > print 1 + \ > 2 > > If there is a space after the \, it's a syntax error. If there is no space, > it prints 3. > > I'm not interpreting how this is good or bad, but just pointing out that > deleting whitespace can change code behavior, particularly in the case of > continuation characters. Interesting example. I don't think trailing whitespace is ever required though. - Robert -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To post to this group, send email to sage-devel@googlegroups.com. To unsubscribe from this group, send email to sage-devel+unsubscr...@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en.
