On Tuesday 27 September 2005 03:07 am, Paul Rubin wrote: > [EMAIL PROTECTED] (Bengt Richter) writes: > > 2) In general, I think it might be good to meet Paul Rubin half way > > re convention vs syntax, but I don't think code tagging should be > > part of the language syntax per se. (-*- cookies -*- really are > > defacto source syntax that snuck in by disguise IMO) So perhaps a > > python command line option could invoke an "official" tool, with > > some more options passed to it to do various checking or extracting etc. > > I think there should be a single tool that knows about as many of > these conventions as possible and warns about misuse, not a bunch of > different tools. If there are a bunch of different tools, then > knowing which tools to use is yet another convention. > [...] > Maybe the checking functions don't really belong in the > compiler/interpreter. PyChecker might be a good home for them, if > it's made part of the distro. There could be an interpreter flag to > invoke PyChecker automatically.
But that's precisely why it would be valuable to have a PEP -- a central catalog of such conventions makes it possible for checking software to be consistent. If PyChecker were going to check for such things, it would do so only because a standard convention had been established. -- Terry Hancock ( hancock at anansispaceworks.com ) Anansi Spaceworks http://www.anansispaceworks.com -- http://mail.python.org/mailman/listinfo/python-list
