Today, it's not possible to add an (empty)
__init__.py file inside the versions directory since it is considered as a migration script and as it does not contain the proper revision and down_revision variables, alembic stops working.
However, allowing us to use a
__init__.py file inside this package would facilitates the packaging: setuptools and distribute do not package the folders not having a
__init__.py file automatically, so the migration scripts end up not packaged by default. We can still use the MANIFEST.in file to add them, but it's a little annoying since we may forget to do that.
This may have some side effects though: what if someone put some code in
__init__.py? Should the code be taken into account in all migration scripts?
May be related to issue #91, but we don't ask exactly the same thing.