There has been some concern about the use of __future__ imports in Twisted. After a lengthy discussion with moshez, marvin--, and phed, we came to the conclusion that it'd be best to put an explicit list of allowable __future__s into the coding standard, nested_scopes being the only one for now (since that's what we use). yay/nay, etc.