Potential incorrect sys.path munging inside tasks

Description

Problem:

• sys.path at fabfile module level seems to be fine
• However, inside fabfile tasks/functions, sometimes sys.path appears to lose the first element, possibly only when that element is the empty string (i.e. when your cwd is in sys.path)
• This does not appear reproducible all the time, but was noticed by an IRC user and confirmed by (IIRC) Morgan shortly thereafter.
• The only place in the code Fabric modifies or mentions sys.path is fabric.main.load_fabfile.

To do:

• Test load_fabfile (right now, seems best way is to use dependency injection so we don’t have to try mocking eg __import__ [which doesn’t appear to work anyway]) to try and nail down the edge case
• If bug is found, fix it!

---

Originally submitted by Jeff Forcier (bitprophet) on 2010-11-12 at 09:18pm EST

---

Closed as Worksforme on 2011-03-10 at 01:08pm EST

[anentropic]

ok found one:

from fabric.api import task
from fabric.contrib import django

django.settings_module('myapp.settings')
from django.conf import settings
_ = settings.INSTALLED_APPS

@task
def mytask():
    # can now use settings.WHATEVER here

[anentropic]

In the meantime is there a workaround to make fabric.contrib.django.settings_module() actually work as per the docs?