From 6690d030e83cae632d3c88a984edb858956a9c17 Mon Sep 17 00:00:00 2001 From: Aldriana Date: Sat, 6 Nov 2010 11:13:19 -0700 Subject: [PATCH] Decision on what python version we're using. --- style.txt | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/style.txt b/style.txt index 4d3c51a..5ffd676 100644 --- a/style.txt +++ b/style.txt @@ -5,8 +5,9 @@ its pretty important to get the framework roughed out so people can start building off it; however, once the initial flurry settles down, I will start enforcing these a bit more strenuously. -0) We are not using Python 3.x. I haven't looked at what's changed in 2.7 - closely enough to know if we're using that, but it'll be 2.6 or 2.7. +0) Assume for the moment that we're using Python 2.6. If there's some 2.7 + feature that you feel would be a real asset for something you're doing, + let me know and we can discuss it. We are not using 3.x. 1) Indents are 4 spaces. Tabs are strictly forbidden. 2) Avoid trailing whitespace in all cases. And I do mean all cases. 3) Line length: Try to keep comments to 80 characters. For general code I'm @@ -59,4 +60,4 @@ possible. You only write the code once, but it will be read many many times. Hence its worth spending an extra couple of minutes writing it if it saves the readers even a few seconds in understanding it. As the saying goes: always write code as though the person who has to maintain it is a dangerous -psychopath that knows where you live. \ No newline at end of file +psychopath that knows where you live.