Edgewall Software
Home
Trac
Trac Hacks
Genshi
Babel
Bitten
Home
Download
Documentation
Mailing Lists
License
FAQ
Search:
Login
Preferences
Help/Guide
About Trac
Wiki
Timeline
Roadmap
Browse Source
View Tickets
New Ticket
Search
Context Navigation
+1
Start Page
Index
History
Editing TracDev/CodingStyle
Adjust edit area height:
8
12
16
20
24
28
32
36
40
Edit side-by-side
= Trac Coding Style = Like most Python projects, we try to adhere to [http://www.python.org/peps/pep-0008.html PEP 8 (Style Guide for Python Code)]. Be sure to read that document if you intend to contribute code to Trac. Note that some of the current Trac code violates a couple of the rules below. We are currently in the process of refactoring the offending modules so that all code uses the same conventions. == Naming conventions == * Package and module names should be all lower-case, words ''may'' be separated by underscores. * Class names use CamelCase. * The names of functions, variables and class members use all lower-case, with words separated by underscores. * Internal methods and variables are prefixed with a single underscore. == Miscellaneous == * Lines shouldn't exceed a length of 80 characters. * Prefer list comprehension to the built-in functions {{{filter()}}} and {{{map()}}} when appropriate. ---- See also: TracDev
Note:
See
WikiFormatting
and
TracWiki
for help on editing wiki content.
Change information
Your email or username:
E-mail address and name can be saved in the
Preferences
Comment about this change (optional):
Note:
See
TracWiki
for help on using the wiki.