Skip to content

Commit

Permalink
Explicitly import PynagError
Browse files Browse the repository at this point in the history
This is needed because there are still unresolved cross-imports
in pynag and explicitly importing PynagError fixes parts of the code
that Utils was import but at the same time those modules were doing:

'from pynag.Utils import PynagError'

This refactor, and a few other changes will make it possible for
us to get rid of those cross imports.
  • Loading branch information
Pall Sigurdsson committed Dec 7, 2014
1 parent 66b9878 commit b56ce93
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions pynag/Utils/__init__.py
Original file line number Diff line number Diff line change
Expand Up @@ -591,6 +591,7 @@ def run_command(command, raise_error_on_fail=False, shell=True, env=None):
from pynag.Utils import checkresult
from pynag.Utils import decorators
from pynag import errors
from pynag.errors import PynagError
from pynag.Utils import git
from pynag.Utils import metrics
from pynag.Utils import nsca
Expand Down

0 comments on commit b56ce93

Please sign in to comment.