Changing the whole code base with trivial changes because the editor you use is broken seems wierd. My editor is fine. Fix the editor (sounds like it needs fixing, PEP or no PEP), change editor, or live without syntax highlighting of your docstrings. The google code one is interesting. Cause the highlighting works at the top of the file, but breaks later on. But all that being said, I won't protest if you do all the work :P
Crispin On Thu, Apr 29, 2010 at 7:27 PM, Adam Bark <[email protected]> wrote: > On 29 April 2010 03:11, Joe Wreschnig <[email protected]> wrote: > >> Right now, most pyglet docstrings use ''' (triple single quotes) >> rather than """ (triple double quotes). Although ''' is valid to >> delimit Python multiline strings, it confuses a number of syntax >> highlighters such as Google Code and Emacs. I was going to fix Emacs's >> highlighter, but in checking the standard >> [http://www.python.org/dev/peps/pep-0257/], I found: >> For consistency, always use """triple double quotes""" around >> docstrings. Use r"""raw triple double quotes""" if you use any >> backslashes in your docstrings. For Unicode docstrings, use >> u"""Unicode triple-quoted strings""". >> >> This makes reading parts of the pyglet code extremely difficult, for >> example >> http://code.google.com/p/pyglet/source/browse/pyglet/sprite.py#211. >> >> So while I may fix Emacs, I think it's also a good idea to fix pyglet. >> This would be a trivial but very noisy patch, and I'd like at least >> one other person to agree with me it's a good idea before I go make >> it. Another option would be to prepare per-file or per-module patches, >> but my view is that it's usually best to do one giant >> future-conflict-creating merge instead of several smaller ones. >> > > It seems like a good idea to me, I generally try to use double quotes when > at all possible. > I also think one big patch merge makes sense for this as it's all doing the > same thing and is fairly self explanatory. > > > -- > You received this message because you are subscribed to the Google Groups > "pyglet-users" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<pyglet-users%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/pyglet-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en.
