27722
Comment:
|
16543
|
Deletions are marked like this. | Additions are marked like this. |
Line 19: | Line 19: |
* [[http://twistedmatrix.com/projects/core/documentation/howto/policy/coding-standard.html|Twisted Coding Standard]] * [[http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/CodingStyle|CodingStyle for Zope 3]] |
* [[http://twistedmatrix.com/trac/browser/trunk/doc/core/development/policy/coding-standard.xhtml?format=raw|Twisted Coding Standard]] * [[http://wiki.zope.org/zope3/CodingStyle|Zope 3 Coding Standards]] Although Launchpad is still written in Python 2, there are several things you can do to improve compatibility with Python 3, making an eventual port easier. There are some good guidelines in the [[https://wiki.ubuntu.com/Python/3|Ubuntu wiki]] about Python 3. |
Line 34: | Line 36: |
* For statements that span multiple lines, use {{{()}}} rather than {{{\}}}. | |
Line 40: | Line 41: |
literal that spans multiple lines. In these cases, you should always format these literals as such: |
literal that spans multiple lines. In these cases, you should consider formatting these literals as follows. This format makes changes to the list clearer to read in a diff. Note the trailing comma on the last element. |
Line 57: | Line 59: |
Things to note: * The opening brace (or parenthesis or bracket) sits at the right end of the first line. Nothing follows this open brace. * Every subsequent item in the sequence is on a line by itself, and every line ends in a comma. This includes the last item in the sequence. * The closing brace lives on a line by itself and is indented to be under the first non-whitespace character of the last item line. This style holds for `__all__` declarations, such that this is correct: {{{#!python __all__ = [ 'HeldMessageDetails', 'MailingList', 'MailingListSet', 'MailingListSubscription', 'MessageApproval', 'MessageApprovalSet', ] }}} In the past there was an exception for import lines but that is no longer the case. See [[#imports|Imports]] for more details about our import style. === Multiline function definitions === When your code ''defines'' a function or method with lots of parameters, it could very well exceed the 79 character maximum. In that case, you have two options for wrapping the parameter list. The first one is preferred. {{{#!python def do_something(the_first_argument, the_second_argument, the_third_argument, the_fourth_argument, the fifth_argument): }}} If indention or length of the function name make the first form impractical, use this second form. {{{#!python def do_something_that_needs_a_lot_explaining( the_first_argument, the_second_argument, the_third_argument, the_fourth_argument, the fifth_argument): }}} It might be a good idea to leave a blank line after the parameter list when using this style. Remember, it's all about readability. === Multiline function calls === When your code ''calls'' a function with lots of arguments, it could very well exceed the 79 character maximum. In that case, you should wrap your function call to fit, like so: {{{#!python my_thing = some_object.do_something_to( the_first_argument, the_second_argument, the_third_argument, the_fourth_argument, the fifth_argument) }}} '''Do not''' indent your code like this: {{{#!python my_thing = some_object.do_something_to(the_first_argument, the_second_argument, the_third_argument, the_fourth_argument, the fifth_argument) }}} or like this: {{{#!python my_thing = some_object.do_something_to(the_first_argument, the_second_argument, the_third_argument, the_fourth_argument, the fifth_argument) }}} === Vim Configuration === To make wrapping and tabs fit the above standard, you can add the following to your {{{.vimrc}}}: {{{ autocmd BufNewFile,BufRead *.py set tw=78 ts=4 sts=4 sw=4 et }}} To make trailing whitespace visible: {{{ set list set listchars=tab:>.,trail:- }}} This will also make it obvious if you accidentally introduce a tab. To make long lines show up: {{{ match Error /\%>79v.\+/ }}} For an even more in-depth Vim configuration, have a look at UltimateVimPythonSetup for a complete vim file you can copy to your local setup. === Emacs Configuration === There are actually two Emacs Python modes. Emacs comes with `python.el` which (IMO) has some quirks and does not seem to be as popular among hardcore Python programmers. [[http://launchpad.net/python-mode|python-mode.el]] comes with XEmacs and is supported by a group of hardcore Python programmers. Even though it's an add-on, it works with Emacs just fine. |
|
Line 172: | Line 62: |
* Classes should be in {{{CamelCase}}} * Methods should be {{{initialCamelCase}}} * Functions should {{{use_underscores}}} * Non-method attributes and properties should {{{use_underscores}}} * Local variables should {{{use_underscores}}} * Modules should be in {{{lowercase}}} * Constants should be in {{{ALL_CAPS}}} * Interface class names should always begin with {{{I}}} * Single character names should be avoided for both variables and methods. Even list comprehensions and generator expressions should not use them. However, these rules may not apply when modifying non-Launchpad code -- e.g. Zope. In those cases, consistency with existing code should be a priority. When working on older Launchpad code that doesn't meet this standard, converting it is preferable but not required. As PEP-8 states, consistency is the top priority. === Shadowing Builtins === Take care not to use names that shadow builtins. This includes names such as {{{str}}}, {{{list}}} or {{{dict}}}. This can cause subtle bugs; for example: {{{#!python def func(str): ... # Convert number to a string s = str(number) # BOOM! }}} It is okay to shadow builtins that we don't use, such as `filter` and `reduce`. === Private Name Mangling === In general, don't mangle attribute names using two leading underscores, e.g. `__very_specific_attribute`: http://www.python.org/doc/2.4.4/ref/atom-identifiers.html Just use a single underscore to create a pseudo-private attribute and name it appropriately. ''BarryWarsaw says: double-underscore private names are really only there to assist in classes designed for inheritance. If class A wants to make sure some of its private attributes won't collide with subclass B's attributes, you can use double-underscores. This is pretty rare, and since we control all the code, is almost never appropriate for Launchpad.'' |
Consistency with existing code is the top priority. We follow PEP-8 with the following exceptions: * {{{CamelCase}}}: classes, interfaces (beginning with {{{I}}}) * {{{initialCamelCase}}}: methods * {{{lowercase_underscores}}}: functions, non-method attributes, properties, local variables * {{{ALL_CAPS}}}: constants |
Line 219: | Line 76: |
Since we control all the Launchpad code, it's almost always better to just rename `A._foo()` to `A.foo()`, making it public, and then it's fine to call it from outside class A. If you need to keep the old name for backward compatibility (because you don't want to change all call sites right now), create an alias and make sure you indicate that the old name is deprecated. |
|
Line 236: | Line 86: |
You should use ''fields'' to describe arguments, return values, and exceptions raised, as documented in [[http://epydoc.sourceforge.net/fields.html|epydoc]]. Avoid using synonym fields such as "returns" and "raises". | You should use field names as defined in the [[http://epydoc.sourceforge.net/fields.html|epydoc]] documentation but with reST syntax. |
Line 240: | Line 90: |
Here are some examples: {{{#!python def example1(a, b): """Perform some calculation. It is a **very** complicated calculation. """ }}} |
Here is comprehensive example. Parameter descriptions are a good idea but not mandatory. Describe in as much or as little detail as necessary. |
Line 267: | Line 109: |
{{{#!python def example3(): """Call `example2` with sensible arguments.""" }}} ''There is some controversy about whether interface methods should get a docstring or not. OT1H, we want everything that '''can''' have a docstring '''to''' have a docstring. OTOH, this messes up `pydoctor` which can extract the method's docstring from the interface if the implementation doesn't have a docstring. We have no resolution on this yet, so for now, include the docstrings on such methods.'' |
|
Line 279: | Line 114: |
# Copyright 2004-2007 Canonical Ltd. All rights reserved. | # Copyright 2009-2011 Canonical Ltd. All rights reserved. |
Line 291: | Line 126: |
with a list of public names in the module. See [#multiline the section on multiline braces] for more details. |
with a list of public names in the module. |
Line 300: | Line 134: |
often than in general Python code. Importing a module should not have side effects. This means that any code other than a function/class/constant declaration should be guarded by an {{{if __name__ == '__main__':}}} line. |
often than in general Python code. {{{__all__}}} should be formatted like imports. |
Line 311: | Line 143: |
* Database code cannot be imported directly | * View code cannot import code from {{{canonical.launchpad.database}}}. |
Line 332: | Line 164: |
Imports should not be circular. Bad: {{{#!python # foo.py import bar }}} {{{#!python # bar.py import foo }}} This causes weird bugs. Find a different way to structure your code. |
|
Line 384: | Line 202: |
We now discourage importing names from packages, where the package's `__init__.py` has sub-module `import-*` statements. We used to do this quite a bit for `canonical.launchpad.interfaces` and many other packages. This style is discouraged now because * `import-*`'s obscure the actual location of names, making finding the objects much more difficult * their use tends to encourage hugantically ginormous multiline import statements, increasing the likelihood of merge conflicts * you also have to maintain the `__init__.py` files * this style can lead to circular import problems Instead, we now recommend that you do not add `import-*`'s in a package's `__init__.py`, and instead, use the more fully qualified import statements in your code. E.g. instead of {{{#!python from canonical.launchpad.interfaces import ( CannotChangeSubscription, CannotSubscribe, CannotUnsubscribe, EmailAddressStatus, IEmailAddressSet, IHeldMessageDetails, ILaunchpadCelebrities, IMailingList, IMailingListSet, IMailingListSubscription, IMessageApproval, IMessageApprovalSet, IMessageSet, MailingListStatus, PostedMessageStatus) }}} Use {{{#!python from canonical.launchpad.interfaces.emailaddress import ( EmailAddressStatus, IEmailAddressSet) from canonical.launchpad.interfaces.launchpad import ILaunchpadCelebrities from canonical.launchpad.interfaces.mailinglist import ( CannotChangeSubscription, CannotSubscribe, CannotUnsubscribe, IHeldMessageDetails, IMailingList, IMailingListSet, IMailingListSubscription, IMessageApproval, IMessageApprovalSet, MailingListStatus) from canonical.launchpad.interfaces.message import IMessageSet }}} |
We encourage importing names from the location they are defined in. This seems to work better with large complex components. |
Line 467: | Line 250: |
== Attributes == Trivial attribute getter/setter functions are not necessary. Python takes a "We're all consenting adults" view on encapsulation, so if you want to access an attribute on an instance, just do it. Be careful when accessing attributes of attributes. E.g.: {{{#!python x = foo.bar.baz * 2 }}} If {{{foo.bar}}} is None, Bad Things will happen, so always check if you're not sure. This is sometimes referred to as the "two dots rule". If you need to dynamically access an attribute, use {{{getattr}}} rather than {{{eval}}}. It is clearer and safer. For example: {{{#!python callback = getattr(self, "handler_" + state) }}} |
|
Line 487: | Line 252: |
When you need to add a property, ensure that {{{__metaclass__ = type}}} is used as mentioned above. For a read-only property, use the following pattern: {{{#!python class SomeClass: @property def foo(self): # Do some processing. return bar }}} You should rarely need to add a property that has a getter and a setter, but on those occasions, this is how to do it. The getter is the same as for the simple case. The setter is called {{{_setfoo}}}. The name {{{_setfoo}}} starts with an underscore to show that it is not meant to be used except via the property. {{{#!python class SomeClass: def foo(self): """Docstrings are helpful.""" # Do some processing. return bar def _setfoo(self, value): # Do something with 'value'. foo = property(foo, _setfoo, doc=foo.__doc__) }}} Note the order: getter, setter, make them into a property. ## TODO: ## mutable default arguments ## no __del__ ## getattr rather than eval ## steal How should I format my docstrings? from HackingFAQ ## mention pychecker etc. ## mention use of RST in docstrings |
Properties are expected to be cheap operations. It is surprising if a property is not cheap operation. For expensive operations use a method, usually named {{{getFoo()}}}. Using {{{cachedproperty}}} provides a work-around but it should not be overused. |
Line 524: | Line 257: |
Launchpad style tests for boolean True only. False, None, and 0 are not the same, and tests that rely on them being the same are ambiguous. Tests of objects that may be None or 0 must be written as truth tests because either value will be interpreted as False by the test. Let's say you have a sequence (e.g. a list or tuple) and you want test whether it's empty or not. Standard Python convention is just to use Python's rules that empty sequences are false: {{{#!python if not mylist: # sequence mylist is empty blah() }}} However, Launchpad hackers consider it to be more explicit to test against the sequence's length: {{{#!python if len(mylist) == 0: # sequence mylist is empty blah() }}} If the value could be `None` though, please check explicitly against that using an identity check. In other words, don't do this: {{{#!python if not foo: }}} and '''definitely''' don't do this: {{{#!python if foo == None: }}}} do this instead: {{{#!python if foo is None: }}} Note though that `is` and `is not` comparisions should only be used for comparing singletons, which include built-ins like `None` but also singleton objects you create in your program: {{{#!python missing = object() thing = mydict.get('thing', missing) if thing is missing: # etc... }}} You wouldn't use `==` in that case, but similarly, if you're not comparing against singletons, you should not use `is`, but `==`: {{{#!python if thing == 'foo': }}} You might think that because of string interning, it would be safe to use `is` here, but remember that interning is an implementation detail and you should not count on any particular string being interned. Always use `==` for comparison against strings and numbers. Note too that because of the way we use SQLObject, there may be some cases where you have to use `==` in places you'd normally think to use `is'. == If statements == The most commonly used patterns like {{{#!python if something: do_something() }}} and {{{#!python if something: do_something() else: do_something_else() }}} are perfectly fine. However, if you do have some `elif` statements, we consider it a good practice to always include an `else` statement, even if it contains only a comment and a `pass` statement, or an `assert` statement with an appropriate failure message. {{{#!python if isinstance(fruit, apple): eat(fruit) elif isinstance(fruit, pineapple): eat(peel(fruit)) else: # We only eat apples and pineapples. pass }}} Similarly you may have empty elif blocks, like {{{#!python if 'foo' in request.form: foo() elif 'bar' in request.form: bar() elif 'goback' in request.form: # No need to do anything; we'll simply redirect the user. pass else: raise UnexpectedFormData() redirect() }}} This may be considered an example of the "Explicit is better than implicit." principle. === Negation === A simple `if ... else` statement already contains a negation of the condition, so it is a good idea to avoid negating the condition because the `not` or `!` can easily be overread. Try to do it this way. {{{#!python if counter.isFull(): chime_bells() else: tick() }}} Avoid this: {{{#!python if not counter.isFull(): tick() else: chime_bells() }}} '''But''' this is ''not'' a strict rule because there may be cases when the program flow is better to read with the negation first, like when checking an object for None before accessing its attributes. {{{#!python if froobob is not None: blachi = froobob.getIt() else: blachi = nonchi }}} Use your own judgement to achieve maximum readability. |
Remember that False, None, [], and 0 are not the same although they all evaluate to False in a boolean context. If this matters in your code, be sure to check explicitly for either of them. Also, checking the length may be an expensive operation. Casting to bool may avoid this if the object specializes by implementing __nonzero__. |
Line 680: | Line 272: |
== Use of open() == When opening a file do one of: 1. Use an encoding (via `codecs.open(...)` in Python 2, or `open(..., encoding="...")` in Python 3), or 2. Use `"b"` in the mode to signify reading/writing bytes. === Discussion of text and binary modes === Python 2 does implicit encoding and decoding between unicode and byte strings. This is convenient, but means we can get away with being vague when reading and writing. Python 3, however, will not let us be vague: {{{ $ python3 >>> open("foo", "w").write(b'bar') Traceback (most recent call last): File "<stdin>", line 1, in <module> TypeError: must be str, not bytes >>> open("foo", "wb").write('bar') Traceback (most recent call last): File "<stdin>", line 1, in <module> TypeError: 'str' does not support the buffer interface }}} Python 3's `open()` takes a new encoding parameter - much like `codecs.open()` in Python 2 - with the following behaviour: "In text mode, if encoding is not specified the encoding used is platform dependent." Equals "don't count on it". Getting into the habit of using binary mode now - or `codecs.open()` - ought to help us avoid this pitfall when porting to Python 3. Python 3's `open()` function also enables universal newlines in text mode by default, for '''writing''' too; Python 2 does not support universal newlines when writing. Using binary mode ought to help us avoid this pitfall too. |
|
Line 681: | Line 308: |
Use of the built-in `hasattr` function should be avoided since it swallows exceptions. Instead use: {{{ if getattr(obj, 'attrname', None) is not None: }}} However, if `None` is a valid value for the attribute, you have to do this instead: {{{ missing = object() if getattr(obj, 'attrname', missing) is not missing: }}} |
Use `safe_hasattr` from `lazr.restful.utils` instead of the built-in `hasattr` function because the latter swallows exceptions. |
Line 724: | Line 341: |
== Unpacking assignment == {{{ #!python val_1, val_2 = multival_func() }}} And for 1-tuples {{{ #!python assert (len(vals) == 1, "Expected 1 value, but received %s" % len(vals)) val_1 = vals[0] }}} |
|
Line 795: | Line 396: |
== Configuration hints == === Vim === To make wrapping and tabs fit the above standard, you can add the following to your {{{.vimrc}}}: {{{ autocmd BufNewFile,BufRead *.py set tw=78 ts=4 sts=4 sw=4 et }}} To make trailing whitespace visible: {{{ set list set listchars=tab:>.,trail:- }}} This will also make it obvious if you accidentally introduce a tab. To make long lines show up: {{{ match Error /\%>79v.\+/ }}} For an even more in-depth Vim configuration, have a look at UltimateVimPythonSetup for a complete vim file you can copy to your local setup. === Emacs === There are actually two Emacs Python modes. Emacs comes with `python.el` which (IMO) has some quirks and does not seem to be as popular among hardcore Python programmers. [[http://launchpad.net/python-mode|python-mode.el]] comes with XEmacs and is supported by a group of hardcore Python programmers. Even though it's an add-on, it works with Emacs just fine. |
Python Style Guide
This document describes expected practices when writing Python code. There are occasions when you can break these rules, but be prepared to justify doing so when your code gets reviewed.
Contents
- Python Style Guide
Existing Conventions
There are well-established conventions in the Python community, and in general we should follow these. General Python conventions, and required reading:
PEP 8: Style Guide for Python Code
PEP 257: Docstring Conventions
The Zen of Python: python -c "import this"
Note that our standards differ slightly from PEP-8 in some cases.
Coding standards other projects use:
Although Launchpad is still written in Python 2, there are several things you can do to improve compatibility with Python 3, making an eventual port easier. There are some good guidelines in the Ubuntu wiki about Python 3.
Related Documents on This Wiki
Whitespace and Wrapping
- Code should fit within 78 columns, so as to fit nicely in an 80 column terminal, even when quoted in an email.
- Indents should be 4 spaces.
No tabs. This is not negotiable.
Multiline braces
There are lots of cases where you might have a list, tuple or dictionary literal that spans multiple lines. In these cases, you should consider formatting these literals as follows. This format makes changes to the list clearer to read in a diff. Note the trailing comma on the last element.
Naming
Consistency with existing code is the top priority. We follow PEP-8 with the following exceptions:
CamelCase: classes, interfaces (beginning with I)
initialCamelCase: methods
lowercase_underscores: functions, non-method attributes, properties, local variables
ALL_CAPS: constants
Private names are private
You should never call a non-public attribute or method from another class. In other words, if class A has a method _foo(), don't call it from anywhere outside class A.
Docstrings
If you haven't already, read PEP 257
- In general, everything that can have a docstring should: modules, classes, methods, functions.
Docstrings should always be enclosed in triple double quotes: """Like this."""
When a class or a method implements an interface, the docstring should say """See `IFoo`."""
Docstrings should be valid reST (with all the painful indentation rules that implies) so that tools such as pydoctor can be used to automatically generate API documentation.
You should use field names as defined in the epydoc documentation but with reST syntax.
Using `name` outputs a link to the documentation of the named object, if pydoctor can figure out what it is. For an example of pydoctor's output, see http://starship.python.net/crew/mwh/hacks/example.html.
Here is comprehensive example. Parameter descriptions are a good idea but not mandatory. Describe in as much or as little detail as necessary.
1 def example2(a, b):
2 """Perform some calculation.
3
4 It is a **very** complicated calculation.
5
6 :param a: The number of gadget you think this
7 function should frobnozzle.
8 :type a: ``int``
9 :param b: The name of the thing.
10 :type b: ``str``
11 :return: The answer!
12 :rtype: ``str``.
13 :raise ZeroDivisionError: when ``a`` is 0.
14 """
Modules
Each module should look like this:
The file standard_template.py has most of this already, so save yourself time by copying that when starting a new module. The "..." should be filled in with a list of public names in the module.
Note that although PEP-8 says to "put any relevant __all__ specification after the imports", Launchpad code should have the __all__ before the imports. This makes it easy to see what a module contains and exports, and avoids the problem that differing amounts of imports among files means that the __all__ list is in a different place each time. Given that we have the Import Fascist utility (see Imports), we use __all__ more often than in general Python code. __all__ should be formatted like imports.
Imports
Restrictions
There are restrictions on which imports can happen in Launchpad. Namely:
View code cannot import code from canonical.launchpad.database.
import * cannot be used if the module being imported from does not have an __all__
Database code may not import zope.exceptions.NotFoundError -- it must instead use canonical.launchpad.interfaces.NotFoundError
These restrictions are enforced by the Import Fascist, which will cause your tests not to pass if you don't abide by the rules.
Imports should be fully qualified. Good:
Bad:
I.e. if foo.bar imports foo.baz, it should say import foo.baz, not import baz.
Multiline imports
Sometimes import lines must span multiple lines, either because the package path is very long or because there are multiple names inside the module that you want to import.
Never use backslashes in import statements! Use parenthesized imports:
Like other lists, imports should list one item per line. The exception is if only one symbol is being imported from a given module.
1 from canonical.widgets.itemswidgets import CheckBoxMatrixWidget
But if you import two or more, then each item needs to be on a line by itself. Note the trailing comma on the last import and that the closing paren is on a line by itself.
Also, 'make lint' is a very good tool for helping you maintain your imports.
Import scope
We encourage importing names from the location they are defined in. This seems to work better with large complex components.
Circular imports
With the increased use of native Storm APIs, you may encounter more circular import situations. For example, a MailingList method may need a reference to the EmailAddress class for a query, and vice versa. The classic way to solve this is to put one of the imports inside a method instead of at module global scope (a "nested import").
Short of adopting something like Zope's lazy imports (which has issues of its own), you can't avoid this, so here are some tips to make it less painful.
- Do the nested import in the least common case. For example, if 5 methods
in database/mailinglist.py need access to EmailAddress but only one method in database/emailaddress.py needs access to MailingList, put the import inside the emailaddres.py method, so you have fewer overall nested imports.
- Clearly comment that the nested import is for avoiding a circular import, using the example below.
- Put the nested import at the top of the method.
Circular imports and webservice exports
One of the largest sources of pain from circular imports is caused when you need to export an interface on the webservice. Generally, the only way around this is to specify generic types (like the plain old Interface) at declaration time and then later patch the webservice's data structures at the bottom of the interface file.
Fortunately there are some helper functions to make this less painful, in components/apihelpers.py. These are simple functions where you can some info about your exported class/method/parameters and they do the rest for you.
For example:
Properties
Properties are expected to be cheap operations. It is surprising if a property is not cheap operation. For expensive operations use a method, usually named getFoo(). Using cachedproperty provides a work-around but it should not be overused.
Truth conditionals
Remember that False, None, [], and 0 are not the same although they all evaluate to False in a boolean context. If this matters in your code, be sure to check explicitly for either of them.
Also, checking the length may be an expensive operation. Casting to bool may avoid this if the object specializes by implementing nonzero.
Chaining method calls
Since in some cases (e.g. class methods and other objects that rely on descriptor get() behaviour) it's not possible to use the old style of chaining method calls (SuperClass.method(self, ...)), we should always use the super() builtin when we want that.
The exception to this rule is when we have class hierarchies outside of our control that are known not to use super() and that we want to use for diamond-shaped inheritance.
Use of lambda, and operator.attrgetter
Prefer operator.attrgetter to lambda. Remember that giving functions names makes the code that calls, passes and returns them easier to debug.
Use of open()
When opening a file do one of:
Use an encoding (via codecs.open(...) in Python 2, or open(..., encoding="...") in Python 3), or
Use "b" in the mode to signify reading/writing bytes.
Discussion of text and binary modes
Python 2 does implicit encoding and decoding between unicode and byte strings. This is convenient, but means we can get away with being vague when reading and writing.
Python 3, however, will not let us be vague:
$ python3 >>> open("foo", "w").write(b'bar') Traceback (most recent call last): File "<stdin>", line 1, in <module> TypeError: must be str, not bytes >>> open("foo", "wb").write('bar') Traceback (most recent call last): File "<stdin>", line 1, in <module> TypeError: 'str' does not support the buffer interface
Python 3's open() takes a new encoding parameter - much like codecs.open() in Python 2 - with the following behaviour:
- "In text mode, if encoding is not specified the encoding used is platform dependent."
Equals "don't count on it". Getting into the habit of using binary mode now - or codecs.open() - ought to help us avoid this pitfall when porting to Python 3.
Python 3's open() function also enables universal newlines in text mode by default, for writing too; Python 2 does not support universal newlines when writing. Using binary mode ought to help us avoid this pitfall too.
Use of hasattr
Use safe_hasattr from lazr.restful.utils instead of the built-in hasattr function because the latter swallows exceptions.
Database related
Storm
We use two database ORM (object-relational mapper) APIs in Launchpad, the older and deprecated SQLObject API and the new and improved Storm API. All new code should use the Storm API, and you are encourages to convert existing code to Storm as part of your tech-debt payments.
Note:
The SQLObject and Storm ResultSet interfaces are not compatible, so e.g. if you need to UNION between these two, you will run into trouble. We are looking into ways to address this.
Using the native Storm API can be verbose and inconvenient for some folks. There is a (somewhat) experimental Sugar base class in lib/canonical/launchpad/database/stormsugar.py which provides many convenient APIs to make your use of Storm easier.
Field attributes
When you need to add ID attributes to your database class, use field_id as the attribute name instead of fieldID.
Multi-line SQL
SQL doesn't care about whitespace, so use triple quotes for large SQL queries or fragments, e.g.:
This also easy to cut-and-paste into psql for interactive testing, unlike if you use several lines of single quoted strings.
Creating temporary files
We should use the most convenient method of the tempfile module, never taint '/tmp/' or any other 'supposed to be there' path.
Despite of being developed and deployed on Ubuntu systems, turning it into restriction might not be a good idea.
When using tempfile.mkstemp remember it returns an open file-descriptor which has to be closed or bound to the open file, otherwise they will leak and eventually hit the default Linux limit (1024).
There are 2 good variations according to the scope of the temporary file.
Or:
Never use:
It's also important to mention that in testing context, specially if you are using the lp.testing.TestCase (or one of its specializations) you can simply create a brand new temporary directory (using mkdtemp). Create as many files you need within it and register a cleanup function to purge the temporary directory recursively.
Configuration hints
Vim
To make wrapping and tabs fit the above standard, you can add the following to your .vimrc:
autocmd BufNewFile,BufRead *.py set tw=78 ts=4 sts=4 sw=4 et
To make trailing whitespace visible:
set list set listchars=tab:>.,trail:-
This will also make it obvious if you accidentally introduce a tab.
To make long lines show up:
match Error /\%>79v.\+/
For an even more in-depth Vim configuration, have a look at UltimateVimPythonSetup for a complete vim file you can copy to your local setup.
Emacs
There are actually two Emacs Python modes. Emacs comes with python.el which (IMO) has some quirks and does not seem to be as popular among hardcore Python programmers. python-mode.el comes with XEmacs and is supported by a group of hardcore Python programmers. Even though it's an add-on, it works with Emacs just fine.