Page history

Jump to: navigation, search

Programming guidelines

26 April 2019

2 April 2016

11 January 2015

Sam888
no edit summary
06:25

2 January 2015

30 December 2014

Sam888
→‎Class headers
00:02
-12

15 February 2014

Sam888
→‎Imports: looks like it does now
01:05
-95

28 December 2012

24 December 2012

Patsyblefebre
→‎Pylint: pylint has a new home http://www.pylint.org/
m
08:29
+2

30 September 2012

Bmcage
→‎Coding style
m
19:28
+639

19 October 2011

Romjerome
→‎Best practices
m
09:36
+31

14 October 2011

7 January 2011

Pumba
→‎Docstrings
m
14:35
+1

30 March 2010

11 March 2010

Nick H
no edit summary
22:49
+298

3 November 2009

Bmcage
→‎Docstrings
08:27
+578

31 July 2009

29 April 2009

Pez4brian
Add sections and improve the Pylint policies.
04:30
+363

2 February 2009

Bmcage
no edit summary
19:57
+348

9 March 2008

Keestux
More explanation about spaces, TABs and indentation.
16:42
+466

17 January 2008

Tfmorris
Fix tab vs space description ("whitespace" includes tabs)
m
01:48
+16

11 November 2007

Pez4brian
add some guidelines
05:42
+177

20 September 2007

Zfoldvari
Revert new module section (mostly included in PEP8)
18:56
-2,441

18 September 2007

6 September 2007

Bmcage
no edit summary
22:08
+97

5 September 2007

Don
New page: Category:Developers/General As more and more people start editing the code, we need to establish a few guidelines to make sure the code remains maintainable. * Class headers. Each c...
03:06
+1,635

Retrieved from "https://gramps-project.org/wiki/index.php/Special:History/Programming_guidelines"