dimagi/rapidsms-logistics — pull request #5 by mlavin (2012-12-03 21:21:48+00:00)
Title: Remove Invalid/Unused Import

This removes a stray import which causes issues with running `syncdb` when the Python path does not have a top level `log` module. To reproduce this problem you can remove the `log.py` in https://github.com/dimagi/logistics/blob/master/logistics_project/log.py and run `syncdb` (or `test`) and you'll see a nice import error:
```
python manage.py syncdb
Traceback (most recent call last):
File "manage.py", line 27, in
execute_manager(settings)
File "/home/mlavin/.virtualenvs/logistics-ghana/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 438, in execute_manager
utility.execute()
File "/home/mlavin/.virtualenvs/logistics-ghana/local/lib/python2.7/site-packages/django/core/management/__init__.py", line 379, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "/home/mlavin/.virtualenvs/logistics-ghana/local/lib/python2.7/site-packages/django/core/management/base.py", line 191, in run_from_argv
self.execute(*args, **options.__dict__)
File "/home/mlavin/.virtualenvs/logistics-ghana/local/lib/python2.7/site-packages/django/core/management/base.py", line 220, in execute
output = self.handle(*args, **options)
File "/home/mlavin/.virtualenvs/logistics-ghana/local/lib/python2.7/site-packages/django/core/management/base.py", line 351, in handle
return self.handle_noargs(**options)
File "/home/mlavin/.virtualenvs/logistics-ghana/local/lib/python2.7/site-packages/south/management/commands/syncdb.py", line 51, in handle_noargs
import_module('.management', app_name)
File "/home/mlavin/.virtualenvs/logistics-ghana/local/lib/python2.7/site-packages/django/utils/importlib.py", line 35, in import_module
__import__(name)
File "../submodules/rapidsms-logistics/logistics/management/__init__.py", line 1, in
import log
ImportError: No module named log
```
It causes a related problem when running the test suite for email-reports: https://github.com/dimagi/email-reports/pull/2

This probably needs to make its way to all of the other deployment branches but I'm not sure of the standard operating procedure for that.