NameError: global name 'settings' is not defined

[mandx]

I'm getting the error NameError: global name 'settings' is not defined in ST3's console, and the exception is thrown at ~/Library/Application Support/Sublime Text 3/Installed Packages/GitGutter.sublime-package", line 73, in settings_loaded which I think is this line: git_gutter_events.py:L73. The plugin works, anyway.

Traceback (most recent call last):
  File "/Applications/Sublime Text.app/Contents/MacOS/sublime_plugin.py", line 255, in on_post_save
    callback.on_post_save(v)
  File "git_gutter_events in ~/Library/Application Support/Sublime Text 3/Installed Packages/GitGutter.sublime-package", line 29, in on_post_save
  File "git_gutter_events in ~/Library/Application Support/Sublime Text 3/Installed Packages/GitGutter.sublime-package", line 73, in settings_loaded
NameError: global name 'settings' is not defined

I'm using OSX 10.9 and ST3 build 3059.

[jisaacks]

Thanks, does this happen if you restart sublime? I have been noticing some weird things with sublime packages, after updating them, some attributes seem lost. A restart usually fixes it though. Just want to rule that out.

[mandx]

@jisaacks Yes you are right, the "problem" goes away if I simply quit and open Sublime again. Then I tried to reproduce the issue, but never happened again. Looking at the code, could be that plugin_loaded() is not always called, and therefore the settings global variable may not be set?

[jisaacks]

it is supposed to be called, but if it isn't getting called that would be a sublime bug. Another possibility is that it gets called, just too late, again in theory that shouldn't happen.

If the bug was reproducible we could figure out exactly what is happening.

[poswald]

FYI, I see this happen reproducibly in the ST3 console on startup if I pip install pylint into my system path (/usr/local/bin/pylint), and it goes away if I pip uninstall it.

[rchl]

Unlikely to still be a problem after 3 years and many changed. Closing.