> > whitespace to files). There are way too many patches on trac with chunks > > that just remove trailing whitespace introduced in other patches, IMHO. If > > we take some stance on it (much like our official endorsement of PEP 8), > > this will be reduced. If people agree I'll make a ticket to add a couple > > lines to the developer's guide. > > Based on the no-tabs-in-Sage-code experience, the only way to have any > kind of actual effect is to add a tool to the merge or doctest scripts > so that new trailing whitespace causes an error. > > (Working on Sage has taught me that only automated tools work; asking > people to remember something or behave a certain way always fails. :)
Yup. > It seems like no one wants to have an epic break-all-patches-in-trac > patch that removes all the trailing whitespace in the Sage library -- > and, some people like some trailing whitespace, so perhaps we should > also add just a warning to the sage-merge script (or whatever release > managers use to add patches)? > I have no idea whether these things are even there in my editor - I use XCode, pico/nano, and TextEdit. But I'm sure that many first-time developers would use that at most, if not even more rudimentary tools. - kcrisman -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
