create_jobs is broken about django-command-extensions HOT 4 CLOSED

I believe I'm experiencing this problem as well:

$ python manage.py create_jobs core
Traceback (most recent call last):
  File "manage.py", line 11, in <module>
    execute_manager(settings)
  File "/Applications/Django/django-trunk/django/core/management/__init__.py", line
340, in execute_manager
    utility.execute()
  File "/Applications/Django/django-trunk/django/core/management/__init__.py", line
295, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/Applications/Django/django-trunk/django/core/management/base.py", line 77,
in run_from_argv
    self.execute(*args, **options.__dict__)
  File "/Applications/Django/django-trunk/django/core/management/base.py", line 96,
in execute
    output = self.handle(*args, **options)
  File "/Applications/Django/django-trunk/django/core/management/base.py", line 146,
in handle
    app_output = self.handle_app(app, **options)
  File
"/opt/local/lib/python2.5/site-packages/django_extensions/management/commands/cr
eate_jobs.py",
line 37, in handle_app
    paths = [p for p in paths if not app_dir.startswith(p)]
AttributeError: 'NoneType' object has no attribute 'startswith'

I think this part is over-engineered given that handle_app is already
application-intelligent. This patch uses a similar technique to getting the 
app_dir
as Django's template file loader, and makes the process a *lot* simpler. :)

It is over-engineered :) Thanks for the patch.

Applied the patch to svn.
If there any problems please reopen this ticket.