Adrian Holovaty wrote: > Let's go with the http package, with an __init__.py in it, simply > because it makes it more flexible to put stuff in there in the future.
This raises an issue of coding style: my feeling, though PEP 8 (the python style guide) doesn't rule on it, is that __init__.py is intended primarily for manipulating the package namespace. Currently template/__init__.py and meta/__init__.py (soon to be joined by http/__init__.py) are loaded with code. I wonder whether people would think it worthwhile to extract this code out into modules, importing just the names that we want accessible at a package level back into __init__.py? It's largely an issue of taste, but it would make it clear what you're getting when you import the package. Not urgent but worth ruling on at some stage. Kieran
