RE: [Docutils-develop] Project Policies

[Tony J I. (Tibs) <to...@ls...>]

David Goodger wrote:
> I've added a "Project Policies" section to the notes:
>
>     http://docutils.sf.net/spec/notes.html#project-policies
>
> Please take a look; I'd like to hear opinions.  Is it
> reasonable?  Anything objectionable?  Thanks.

Looking at Coding Conventions...

Well, pysource is a big offender on the naming conventions for
non-classes, but I am aware of that and have intended to fix it
(camelCase method names for the visitor methods used to wander over the
Python are indicated by the visitor mechanism [you'll need to add an
allowable exception for cases like this, I'm afraid], and that rather
propagated, even though it is not normally the convention I use). As I
said, something I intend strongly to fix at some point.

The "single quote for string literals" is a problem to me - I have never
been aware of this preference - indeed, I thought the "standard" Python
preference was the other way round (for no reason I can think of).

I have a lot of existing code that would need changing to match that,
and *personally* am not very motivated, since I find 'string' harder to
see than "string" (unless colour coded). On the other hand, following a
consistent set of rules is a good thing. On the other other hand, I am
actually surprised there *is* a policy on this, since Python itself
doesn't care...

Hmm - not sure where I stand on that - obviously I'd prefer not to
change my ways, but also I prefer to code to standards if they exist.

Can you point to where this is documented outwith your text? (fighting
whilst not sure he should!)

The CVS part looks good, and I like the explanation of how to use the
sandbox.

Tibs

--
Tony J Ibbs (Tibs)      http://www.tibsnjoan.co.uk/
Give a pedant an inch and they'll take 25.4mm
(once they've established you're talking a post-1959 inch, of course)
My views! Mine! Mine! (Unless Laser-Scan ask nicely to borrow them.)